From: Chris T. <chr...@gm...> - 2012-12-19 00:32:15
|
Hello, There's a bit of a discontinuity between the svn extension version and the use of 1.7.x for compatibility with latest eclipse. Why can't the svn extension be upgraded to current 1.7? I looked over the code recently and it appears to be possible though it is not code that I use or am familiar with. I guess moving the svn extension to git will solve a part of the problem but will the extension be compatible with an eXist that uses 1.7.x elsewhere? Chris On Dec 18, 2012, at 11:19 PM, Dmitriy Shabanov <sha...@gm...> wrote: > Yes, I plan to move svn extension to git and provide it with old svnkit jars. > > On Tue, Dec 18, 2012 at 8:52 PM, Joe Wicentowski <jo...@gm...> wrote: > FYI, the build process on trunk still fails whenever the build > properties are set to include.feature.svn = true, unless I copy the > old svnkit jars into lib/user. I'm concerned that new users who try > to use 2.0RC or 2.0-final will be frustrated when they try to enable > the SVN feature. Do you have an idea for how to solve this? I > proposed some ideas below. > > -- > Dmitriy Shabanov > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d_______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |