From: Dan M. <dan...@gm...> - 2011-05-16 14:57:06
|
Hi, Am I correct to assume that there is, as of yet, no documentation on Dmitriy's exist subversion extension and the demo server has, as of today no link? I would like to create a Wikibook article on the exact steps needed to get Dmitriy's SVN extension running in the current trunk. Would anyone be willing to review this article for correctness? Here is a first version: http://en.wikibooks.org/wiki/XQuery/Subversion I will be updating this throughout the day. Thanks! - Dan On Sun, May 15, 2011 at 9:51 PM, Dmitriy Shabanov <sha...@gm...>wrote: > For now eXist's svn ext is the copy of svn client (WS) (think you found > right version, new API was changed) . I did mail to svn ML and did ask for > some changers at svn client code to allow simple reuse it without copying. > > I'll check what happening on svn side. > > On Sun, May 15, 2011 at 9:23 PM, Stefan Majewski < > ste...@un...> wrote: > >> given the recent interest in versioning within eXist, I wondered what >> had happened to Dmitriy's exist extension. >> As far as I understood, it is designed for precisely the purpose of >> having versioned code within the database. >> >> >> On 04/07/10 20:18, Dmitriy Shabanov wrote: >> > I'm glad to write that SVN extension is working (at the trunk). >> > >> > Testers & front-end developers (xquery functions & management front-end) >> > are welcome. >> >> I assume nobody is actively waiting for any response to this >> announcement, anymore. Nevertheless, this has been on my todo-list for a >> very long time and recent interest in versioning bumped it a little >> further up. Thus, I tried to give it a try: >> >> The obvious first thing I tried was to compile the extension module by >> just enabling it in the build process. Fair enough, obviously the svnkit >> api found in tools/ant/lib (that's the one it uses, I assume?) does not >> match the extension's implementation, such that the extension does not >> compile and the compilation process dies with errors related to >> unresolved symbols. >> >> But, as the svnkit library is not in the exist-repository and fetched >> during the build process, I assumed that probably a bump of the version >> that exist downloads lead to conflicting apis between exist's extension >> and svnkit. >> >> I tried the older svnkit releases one after the other and found that the >> extension compiles when I use svnkit.jar and svnkit-cli.jar from the >> release svnkit-1.3.3-6648. I simply replaced the jars in tools/ant/lib. >> >> At this point I have a few questions: >> >> - is this the appropriate version of svnkit? >> - if nothing else depends on the latest release of svnkit, would it be a >> good idea to fetch this older release in the first place? >> - would it be preferable to upgrade to the latest svnkit api? As far as >> I see this would require rewrites in the svn extension at some points. >> >> right now I am running the test-suite, that takes a while. I'm curious >> how the svn extension does with this and will do some other work in the >> meantime. Then I'm going to try to use the xquery functions provided by >> the svn extension. If someone has any hints or experiences with this, >> I'd be glad for any pointer. From a quick search in the mailing-list, I >> haven't found much apart from Dmitriy's announcement. >> >> cheers, >> Stefan >> >> > > > -- > Dmitriy Shabanov > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > > -- Dan McCreary Semantic Solutions Architect office: (952) 931-9198 cell: (612) 986-1552 |