From: Immanuel N. <imm...@gm...> - 2013-07-24 13:56:06
|
Hi, Apparently, I broke my existdb when I tried to activate the subversion module following the instructions at http://exist-db.org/exist/apps/doc/subversion-module.xml In section "Enableing the subversion module" the final sentence says: "Recompile the eXist system using the build script." I interpreted this as running $EXIST_HOME/build.sh. The build process unfortunately failed (I appended at the bottom a few details of the error message). Yet, I thought it might be a good occasion to replace my "old" eXist 2.0 by the new version 2.1 and try to activate the svn module in this new version with more fortune. However, I have a little problem (which was my fault - I have to admit): my last backup of my existdb is some days old (I know I should have made a backup before executing build.sh - on the other hand I thought enabling a module would not crash the whole system). Anyway, I still have access to $EXIST_HOME/webapp/WEB-INF/data/fs and I wonder whether this contains all my latest data which I could then somehow import into my new existdb 2.1? Thanks for help. Immanuel --- erroe message fragment from build process: prepare: [echo] ------------------------- [echo] eXist 2.0 build [echo] ------------------------- [echo] SVN revision 18252 [echo] [echo] Apache Ant(TM) version 1.8.2 compiled on December 20 2010 BUILD FAILED /usr/local/exist/build/scripts/build-impl.xml:413: The following error occurred while executing this line: /usr/local/exist/build/scripts/extensions-build.xml:31: The following error occurred while executing this line: /usr/local/exist/build/scripts/extensions-common.xml:137: The following error occurred while executing this line: /usr/local/exist/build/scripts/extensions-common.xml:199: The following error occurred while executing this line: /usr/local/exist/build/scripts/extensions-common.xml:152: The following error occurred while executing this line: /usr/local/exist/build/scripts/extensions-common.xml:163: Compile failed; see the compiler error output for details. |
From: Dannes W. <da...@ex...> - 2013-07-24 14:09:53
|
Hi, > erroe message fragment from build process: > > prepare: > [echo] ------------------------- > [echo] eXist 2.0 build > [echo] ------------------------- > [echo] SVN revision 18252 > [echo] > [echo] Apache Ant(TM) version 1.8.2 compiled on December 20 2010 > > > BUILD FAILED > /usr/local/exist/build/scripts/build-impl.xml:413: The following error > occurred while executing this line: > /usr/local/exist/build/scripts/extensions-build.xml:31: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:137: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:199: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:152: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:163: Compile failed; > see the compiler error output for details. > I think there must be a bit more logging visible..... please could you share? regards Dannes -- eXist-db Native XML Database - http://exist-db.org Join us on linked-in: http://www.linkedin.com/groups?gid=35624 |
From: Dmitriy S. <sha...@gm...> - 2013-07-24 19:47:45
|
you should use old version of svnkit.jar, it will not compile with new one because API changed. On Wed, Jul 24, 2013 at 6:55 PM, Immanuel Normann < imm...@gm...> wrote: > Apparently, I broke my existdb when I tried to activate the subversion > module following the instructions at > > http://exist-db.org/exist/apps/doc/subversion-module.xml > > In section "Enableing the subversion module" the final sentence says: > "Recompile the eXist system using the build script." > > I interpreted this as running $EXIST_HOME/build.sh. > > The build process unfortunately failed (I appended at the bottom a few > details of the error message). > > Yet, I thought it might be a good occasion to replace my "old" eXist 2.0 > by the new version 2.1 and try to activate the svn module in this new > version with more fortune. > > However, I have a little problem (which was my fault - I have to admit): > my last backup of my existdb is some days old (I know I should have made a > backup before executing build.sh - on the other hand I thought enabling a > module would not crash the whole system). Anyway, I still have access to > $EXIST_HOME/webapp/WEB-INF/data/fs and I wonder whether this contains all > my latest data which I could then somehow import into my new existdb 2.1? > > Thanks for help. > > Immanuel > > --- > > erroe message fragment from build process: > > prepare: > [echo] ------------------------- > [echo] eXist 2.0 build > [echo] ------------------------- > [echo] SVN revision 18252 > [echo] > [echo] Apache Ant(TM) version 1.8.2 compiled on December 20 2010 > > > BUILD FAILED > /usr/local/exist/build/scripts/build-impl.xml:413: The following error > occurred while executing this line: > /usr/local/exist/build/scripts/extensions-build.xml:31: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:137: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:199: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:152: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:163: Compile failed; > see the compiler error output for details. > -- Dmitriy Shabanov PS There is patched jgit for eXist. It's in better shape then svn one. |
From: Immanuel N. <imm...@gm...> - 2013-07-25 11:38:36
|
Dmitriy, I saw your presentation on eXgit at XML-Prague and I really would love to use git instead of svn. Yet, our XML-authors use oXygen that doesn't have a nice git client but a subversion client built-in (moreover I heard that oXygen argue that subversion is the more appropriate versioning system for XML-content, i.e. they are not planning to implement a git-client for oXygen). A subversion repository is therefore more convenient for our XML-authors and I need to access the same repository through existdb. Could you be more specific about what version of svnkit.jar works well with what version of existdb? (And possibly where I should get it from). Thanks Immanuel 2013/7/24 Dmitriy Shabanov <sha...@gm...> > you should use old version of svnkit.jar, it will not compile with new one > because API changed. > > On Wed, Jul 24, 2013 at 6:55 PM, Immanuel Normann < > imm...@gm...> wrote: > >> Apparently, I broke my existdb when I tried to activate the subversion >> module following the instructions at >> >> http://exist-db.org/exist/apps/doc/subversion-module.xml >> >> In section "Enableing the subversion module" the final sentence says: >> "Recompile the eXist system using the build script." >> >> I interpreted this as running $EXIST_HOME/build.sh. >> >> The build process unfortunately failed (I appended at the bottom a few >> details of the error message). >> >> Yet, I thought it might be a good occasion to replace my "old" eXist 2.0 >> by the new version 2.1 and try to activate the svn module in this new >> version with more fortune. >> >> However, I have a little problem (which was my fault - I have to admit): >> my last backup of my existdb is some days old (I know I should have made a >> backup before executing build.sh - on the other hand I thought enabling a >> module would not crash the whole system). Anyway, I still have access to >> $EXIST_HOME/webapp/WEB-INF/data/fs and I wonder whether this contains all >> my latest data which I could then somehow import into my new existdb 2.1? >> >> Thanks for help. >> >> Immanuel >> >> --- >> >> erroe message fragment from build process: >> >> prepare: >> [echo] ------------------------- >> [echo] eXist 2.0 build >> [echo] ------------------------- >> [echo] SVN revision 18252 >> [echo] >> [echo] Apache Ant(TM) version 1.8.2 compiled on December 20 2010 >> >> >> BUILD FAILED >> /usr/local/exist/build/scripts/build-impl.xml:413: The following error >> occurred while executing this line: >> /usr/local/exist/build/scripts/extensions-build.xml:31: The following >> error occurred while executing this line: >> /usr/local/exist/build/scripts/extensions-common.xml:137: The following >> error occurred while executing this line: >> /usr/local/exist/build/scripts/extensions-common.xml:199: The following >> error occurred while executing this line: >> /usr/local/exist/build/scripts/extensions-common.xml:152: The following >> error occurred while executing this line: >> /usr/local/exist/build/scripts/extensions-common.xml:163: Compile failed; >> see the compiler error output for details. >> > > -- > Dmitriy Shabanov > > PS There is patched jgit for eXist. It's in better shape then svn one. > |
From: Joe W. <jo...@gm...> - 2013-07-25 12:01:53
|
Sent from my iPhone On Thursday, July 25, 2013 at 7:38 AM, Immanuel Normann wrote: > Dmitriy, > I saw your presentation on eXgit at XML-Prague and I really would love to use git instead of svn. Yet, our XML-authors use oXygen that doesn't have a nice git client but a subversion client built-in (moreover I heard that oXygen argue that subversion is the more appropriate versioning system for XML-content, i.e. they are not planning to implement a git-client for oXygen). > A subversion repository is therefore more convenient for our XML-authors and I need to access the same repository through existdb. > > Could you be more specific about what version of svnkit.jar works well with what version of existdb? (And possibly where I should get it from). > > Thanks > > Immanuel > > > 2013/7/24 Dmitriy Shabanov <sha...@gm... (mailto:sha...@gm...)> > > you should use old version of svnkit.jar, it will not compile with new one because API changed. > > > > On Wed, Jul 24, 2013 at 6:55 PM, Immanuel Normann <imm...@gm... (mailto:imm...@gm...)> wrote: > > > Apparently, I broke my existdb when I tried to activate the subversion module following the instructions at > > > > > > http://exist-db.org/exist/apps/doc/subversion-module.xml > > > > > > In section "Enableing the subversion module" the final sentence says: "Recompile the eXist system using the build script." > > > > > > I interpreted this as running $EXIST_HOME/build.sh. > > > > > > The build process unfortunately failed (I appended at the bottom a few details of the error message). > > > > > > Yet, I thought it might be a good occasion to replace my "old" eXist 2.0 by the new version 2.1 and try to activate the svn module in this new version with more fortune. > > > > > > However, I have a little problem (which was my fault - I have to admit): my last backup of my existdb is some days old (I know I should have made a backup before executing build.sh - on the other hand I thought enabling a module would not crash the whole system). Anyway, I still have access to $EXIST_HOME/webapp/WEB-INF/data/fs and I wonder whether this contains all my latest data which I could then somehow import into my new existdb 2.1? > > > > > > Thanks for help. > > > > > > Immanuel > > > > > > --- > > > > > > erroe message fragment from build process: > > > > > > prepare: > > > [echo] ------------------------- > > > [echo] eXist 2.0 build > > > [echo] ------------------------- > > > [echo] SVN revision 18252 > > > [echo] > > > [echo] Apache Ant(TM) version 1.8.2 compiled on December 20 2010 > > > > > > > > > BUILD FAILED > > > /usr/local/exist/build/scripts/build-impl.xml:413: The following error occurred while executing this line: > > > /usr/local/exist/build/scripts/extensions-build.xml:31: The following error occurred while executing this line: > > > /usr/local/exist/build/scripts/extensions-common.xml:137: The following error occurred while executing this line: > > > /usr/local/exist/build/scripts/extensions-common.xml:199: The following error occurred while executing this line: > > > /usr/local/exist/build/scripts/extensions-common.xml:152: The following error occurred while executing this line: > > > /usr/local/exist/build/scripts/extensions-common.xml:163: Compile failed; see the compiler error output for details. > > -- > > Dmitriy Shabanov > > > > PS There is patched jgit for eXist. It's in better shape then svn one. > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > > |
From: Joe W. <jo...@gm...> - 2013-07-25 12:15:30
|
Sorry for that last empty message! My baby got ahold of my iPhone! As long as I'm writing another message, I'm curious to know more about the oXygen folks' rationale for saying svn is more appropriate for xml than git. I've been thinking of migrating my office to github, so if there are any downsides for xml heavy repos, I'd be interested to know. Sent from my iPhone On Thursday, July 25, 2013 at 8:01 AM, Joe Wicentowski wrote: > > > Sent from my iPhone > > > On Thursday, July 25, 2013 at 7:38 AM, Immanuel Normann wrote: > > > Dmitriy, > > I saw your presentation on eXgit at XML-Prague and I really would love to use git instead of svn. Yet, our XML-authors use oXygen that doesn't have a nice git client but a subversion client built-in (moreover I heard that oXygen argue that subversion is the more appropriate versioning system for XML-content, i.e. they are not planning to implement a git-client for oXygen). > > A subversion repository is therefore more convenient for our XML-authors and I need to access the same repository through existdb. > > > > Could you be more specific about what version of svnkit.jar works well with what version of existdb? (And possibly where I should get it from). > > > > Thanks > > > > Immanuel > > > > > > 2013/7/24 Dmitriy Shabanov <sha...@gm... (mailto:sha...@gm...)> > > > you should use old version of svnkit.jar, it will not compile with new one because API changed. > > > > > > On Wed, Jul 24, 2013 at 6:55 PM, Immanuel Normann <imm...@gm... (mailto:imm...@gm...)> wrote: > > > > Apparently, I broke my existdb when I tried to activate the subversion module following the instructions at > > > > > > > > http://exist-db.org/exist/apps/doc/subversion-module.xml > > > > > > > > In section "Enableing the subversion module" the final sentence says: "Recompile the eXist system using the build script." > > > > > > > > I interpreted this as running $EXIST_HOME/build.sh. > > > > > > > > The build process unfortunately failed (I appended at the bottom a few details of the error message). > > > > > > > > Yet, I thought it might be a good occasion to replace my "old" eXist 2.0 by the new version 2.1 and try to activate the svn module in this new version with more fortune. > > > > > > > > However, I have a little problem (which was my fault - I have to admit): my last backup of my existdb is some days old (I know I should have made a backup before executing build.sh - on the other hand I thought enabling a module would not crash the whole system). Anyway, I still have access to $EXIST_HOME/webapp/WEB-INF/data/fs and I wonder whether this contains all my latest data which I could then somehow import into my new existdb 2.1? > > > > > > > > Thanks for help. > > > > > > > > Immanuel > > > > > > > > --- > > > > > > > > erroe message fragment from build process: > > > > > > > > prepare: > > > > [echo] ------------------------- > > > > [echo] eXist 2.0 build > > > > [echo] ------------------------- > > > > [echo] SVN revision 18252 > > > > [echo] > > > > [echo] Apache Ant(TM) version 1.8.2 compiled on December 20 2010 > > > > > > > > > > > > BUILD FAILED > > > > /usr/local/exist/build/scripts/build-impl.xml:413: The following error occurred while executing this line: > > > > /usr/local/exist/build/scripts/extensions-build.xml:31: The following error occurred while executing this line: > > > > /usr/local/exist/build/scripts/extensions-common.xml:137: The following error occurred while executing this line: > > > > /usr/local/exist/build/scripts/extensions-common.xml:199: The following error occurred while executing this line: > > > > /usr/local/exist/build/scripts/extensions-common.xml:152: The following error occurred while executing this line: > > > > /usr/local/exist/build/scripts/extensions-common.xml:163: Compile failed; see the compiler error output for details. > > > -- > > > Dmitriy Shabanov > > > > > > PS There is patched jgit for eXist. It's in better shape then svn one. > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Exist-open mailing list > > Exi...@li... > > https://lists.sourceforge.net/lists/listinfo/exist-open > > > > > > > > |
From: Immanuel N. <imm...@gm...> - 2013-07-25 12:32:09
|
I got the statement "that subversion is the more appropriate versioning system for XML-content" from hearsay only. Regarding there (non-)plans to support git in oXygen I refer to http://www.oxygenxml.com/forum/topic9867.html 2013/7/25 Joe Wicentowski <jo...@gm...> > Sorry for that last empty message! My baby got ahold of my iPhone! > > As long as I'm writing another message, I'm curious to know more about the > oXygen folks' rationale for saying svn is more appropriate for xml than > git. I've been thinking of migrating my office to github, so if there are > any downsides for xml heavy repos, I'd be interested to know. > > Sent from my iPhone > > On Thursday, July 25, 2013 at 8:01 AM, Joe Wicentowski wrote: > > > > Sent from my iPhone > > On Thursday, July 25, 2013 at 7:38 AM, Immanuel Normann wrote: > > Dmitriy, > I saw your presentation on eXgit at XML-Prague and I really would love to > use git instead of svn. Yet, our XML-authors use oXygen that doesn't have a > nice git client but a subversion client built-in (moreover I heard that > oXygen argue that subversion is the more appropriate versioning system for > XML-content, i.e. they are not planning to implement a git-client for > oXygen). > A subversion repository is therefore more convenient for our XML-authors > and I need to access the same repository through existdb. > > Could you be more specific about what version of svnkit.jar works well > with what version of existdb? (And possibly where I should get it from). > > Thanks > > Immanuel > > > 2013/7/24 Dmitriy Shabanov <sha...@gm...> > > you should use old version of svnkit.jar, it will not compile with new one > because API changed. > > On Wed, Jul 24, 2013 at 6:55 PM, Immanuel Normann < > imm...@gm...> wrote: > > Apparently, I broke my existdb when I tried to activate the subversion > module following the instructions at > > http://exist-db.org/exist/apps/doc/subversion-module.xml > > In section "Enableing the subversion module" the final sentence says: > "Recompile the eXist system using the build script." > > I interpreted this as running $EXIST_HOME/build.sh. > > The build process unfortunately failed (I appended at the bottom a few > details of the error message). > > Yet, I thought it might be a good occasion to replace my "old" eXist 2.0 > by the new version 2.1 and try to activate the svn module in this new > version with more fortune. > > However, I have a little problem (which was my fault - I have to admit): > my last backup of my existdb is some days old (I know I should have made a > backup before executing build.sh - on the other hand I thought enabling a > module would not crash the whole system). Anyway, I still have access to > $EXIST_HOME/webapp/WEB-INF/data/fs and I wonder whether this contains all > my latest data which I could then somehow import into my new existdb 2.1? > > Thanks for help. > > Immanuel > > --- > > erroe message fragment from build process: > > prepare: > [echo] ------------------------- > [echo] eXist 2.0 build > [echo] ------------------------- > [echo] SVN revision 18252 > [echo] > [echo] Apache Ant(TM) version 1.8.2 compiled on December 20 2010 > > > BUILD FAILED > /usr/local/exist/build/scripts/build-impl.xml:413: The following error > occurred while executing this line: > /usr/local/exist/build/scripts/extensions-build.xml:31: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:137: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:199: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:152: The following > error occurred while executing this line: > /usr/local/exist/build/scripts/extensions-common.xml:163: Compile failed; > see the compiler error output for details. > > > -- > Dmitriy Shabanov > > PS There is patched jgit for eXist. It's in better shape then svn one. > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > > > > |
From: Dmitriy S. <sha...@gm...> - 2013-07-25 15:41:12
|
On Thu, Jul 25, 2013 at 4:38 PM, Immanuel Normann < imm...@gm...> wrote: > I saw your presentation on eXgit at XML-Prague and I really would love to > use git instead of svn. Yet, our XML-authors use oXygen that doesn't have a > nice git client but a subversion client built-in (moreover I heard that > oXygen argue that subversion is the more appropriate versioning system for > XML-content, i.e. they are not planning to implement a git-client for > oXygen). > A subversion repository is therefore more convenient for our XML-authors > and I need to access the same repository through existdb. > > Could you be more specific about what version of svnkit.jar works well > with what version of existdb? (And possibly where I should get it from). > If you have working copy with svn enabled, you may copy svnkit from there. The version that should be used here http://www.svnkit.com/org.tmatesoft.svn_1.3.3.standalone.zip(copy svnkit.jar & svnkit-cli.jar to lib/users) -- Dmitriy Shabanov |
From: Immanuel N. <imm...@gm...> - 2013-07-30 10:57:43
|
Now I have checked out the latest master version from https://github.com/eXist-db/exist.git and configured conf.xml to extensions/build.properties activate the svn module, copied svnkit.jar & svnkit-cli.jar to lib/users from http://www.svnkit.com/org.tmatesoft.svn_1.3.3.standalone.zip and tried to build exist with all that. I got this message eventually: BUILD FAILED /home/immanuel/vc/git/exist/build/scripts/subversion.xml:55: org.tmatesoft.svn.core.SVNException: svn: Path '.' ends in '.', which is unsupported for this operation at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probe(SVNWCAccess.java:806) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probeOpen(SVNWCAccess.java:290) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probeOpen(SVNWCAccess.java:286) at org.tmatesoft.svn.core.wc.SVNWCClient.crawlEntries(SVNWCClient.java:3291) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2496) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2863) at nl.ow.dilemma.ant.svn.SubversionInfoImpl.getRevision(SubversionInfoImpl.java:70) at nl.ow.dilemma.ant.svn.SubversionInfoTask.execute(SubversionInfoTask.java:74) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.Target.performTasks(Target.java:411) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) at org.apache.tools.ant.Project.executeTarget(Project.java:1368) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.Main.runBuild(Main.java:809) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) 2013/7/25 Dmitriy Shabanov <sha...@gm...> > On Thu, Jul 25, 2013 at 4:38 PM, Immanuel Normann < > imm...@gm...> wrote: > >> I saw your presentation on eXgit at XML-Prague and I really would love to >> use git instead of svn. Yet, our XML-authors use oXygen that doesn't have a >> nice git client but a subversion client built-in (moreover I heard that >> oXygen argue that subversion is the more appropriate versioning system for >> XML-content, i.e. they are not planning to implement a git-client for >> oXygen). >> A subversion repository is therefore more convenient for our XML-authors >> and I need to access the same repository through existdb. >> >> Could you be more specific about what version of svnkit.jar works well >> with what version of existdb? (And possibly where I should get it from). >> > > If you have working copy with svn enabled, you may copy svnkit from there. > The version that should be used here > http://www.svnkit.com/org.tmatesoft.svn_1.3.3.standalone.zip(copy svnkit.jar & svnkit-cli.jar to lib/users) > > -- > Dmitriy Shabanov > |
From: Dannes W. <di...@ex...> - 2013-07-30 11:15:11
Attachments:
smime.p7s
|
what command are trying to run? are you sure you are completely in sync with 'develop' or 'master' on github? looking at the trace: > nl.ow.dilemma.ant.svn.SubversionInfoImpl.getRevision(SubversionInfoImpl.java:70) > at nl.ow.dilemma.ant.svn.SubversionInfoTask.execute(SubversionInfoTask.java:74) you are trying to get a subversion from the git-repo.... LJO did remove it all recently regards Dannes On 30 Jul 2013, at 12:57 , Immanuel Normann <imm...@gm...> wrote: > Now I have checked out the latest master version from https://github.com/eXist-db/exist.git and configured conf.xml to extensions/build.properties activate the svn module, copied svnkit.jar & svnkit-cli.jar to lib/users from http://www.svnkit.com/org.tmatesoft.svn_1.3.3.standalone.zip and tried to build exist with all that. > I got this message eventually: > > BUILD FAILED > /home/immanuel/vc/git/exist/build/scripts/subversion.xml:55: org.tmatesoft.svn.core.SVNException: svn: Path '.' ends in '.', which is unsupported for this operation > at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) > at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) > at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probe(SVNWCAccess.java:806) > at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probeOpen(SVNWCAccess.java:290) > at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probeOpen(SVNWCAccess.java:286) > at org.tmatesoft.svn.core.wc.SVNWCClient.crawlEntries(SVNWCClient.java:3291) > at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2496) > at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2863) > at nl.ow.dilemma.ant.svn.SubversionInfoImpl.getRevision(SubversionInfoImpl.java:70) > at nl.ow.dilemma.ant.svn.SubversionInfoTask.execute(SubversionInfoTask.java:74) |
From: Immanuel N. <imm...@gm...> - 2013-07-30 14:44:09
|
2013/7/30 Dannes Wessels <di...@ex...> > what command are trying to run? > are you sure you are completely in sync with 'develop' or 'master' on > github? > I just followed the instructions from https://github.com/eXist-db/exist $ git clone gi...@gi...:eXist-db/exist.git $ cd exist $ git checkout master $ ./build.sh looking at the trace: > > > nl.ow.dilemma.ant.svn.SubversionInfoImpl.getRevision(SubversionInfoImpl.java:70) > at > nl.ow.dilemma.ant.svn.SubversionInfoTask.execute(SubversionInfoTask.java:74) > > > you are trying to get a subversion from the git-repo.... LJO did remove it > all recently > So what am I supposed to do to get the subversion module running again? Immanuel > > Dannes > > > > On 30 Jul 2013, at 12:57 , Immanuel Normann <imm...@gm...> > wrote: > > Now I have checked out the latest master version from > https://github.com/eXist-db/exist.git and configured conf.xml to > extensions/build.properties activate the svn module, copied svnkit.jar > & svnkit-cli.jar to lib/users from > http://www.svnkit.com/org.tmatesoft.svn_1.3.3.standalone.zip and tried to > build exist with all that. > I got this message eventually: > > BUILD FAILED > /home/immanuel/vc/git/exist/build/scripts/subversion.xml:55: > org.tmatesoft.svn.core.SVNException: svn: Path '.' ends in '.', which is > unsupported for this operation > at > org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) > at > org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) > at > org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probe(SVNWCAccess.java:806) > at > org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probeOpen(SVNWCAccess.java:290) > at > org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.probeOpen(SVNWCAccess.java:286) > at > org.tmatesoft.svn.core.wc.SVNWCClient.crawlEntries(SVNWCClient.java:3291) > at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2496) > at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2863) > at > nl.ow.dilemma.ant.svn.SubversionInfoImpl.getRevision(SubversionInfoImpl.java:70) > at > nl.ow.dilemma.ant.svn.SubversionInfoTask.execute(SubversionInfoTask.java:74) > > > |
From: Dannes W. <di...@ex...> - 2013-07-30 15:12:56
|
that question has been answered by Dmitriy in this mail thread already On 30 Jul 2013, at 16:44 , Immanuel Normann <imm...@gm...> wrote: > you are trying to get a subversion from the git-repo.... LJO did remove it all recently > > So what am I supposed to do to get the subversion module running again |
From: Immanuel N. <imm...@gm...> - 2013-07-30 19:29:15
|
it is true that Dmitriy answered my question in this mail thread already and it was a solution for the where I rebuilt the downloaded the stable existdb 2.1. But it wasn't a solution for the new case where I built the latest master release from github. My last mail in this thread makes the steps explicit including also Dmitriy's instructions: "copied svnkit.jar & svnkit-cli.jar to lib/users from http://www.svnkit.com/org.tmatesoft.svn_1.3.3.standalone.zip" Yet, the built failed as described above. I don't see what else I could have missed from Dmitriy's answer. My dilemma is that rebuilding the stable existdb 2.1 with the subversion module enabled works fine, but starting it throws error messages (see my post in the "error in startup of clean build of trunk" thread). To overcome the latter tried to build the master release from github with the subversion module enabled which unfortunately failed (as I described above in this thread). And for this case Dmitiy's answer was not a solution. regards Immanuel 2013/7/30 Dannes Wessels <di...@ex...> > that question has been answered by Dmitriy in this mail thread already > > On 30 Jul 2013, at 16:44 , Immanuel Normann <imm...@gm...> > wrote: > > you are trying to get a subversion from the git-repo.... LJO did remove it >> all recently >> > > So what am I supposed to do to get the subversion module running again > > > |
From: Dannes W. <di...@ex...> - 2013-07-30 20:37:58
|
Hi, On 30 Jul 2013, at 21:29 , Immanuel Normann <imm...@gm...> wrote: > Yet, the built failed as described above. I don't see what else I could have missed from Dmitriy's answer. the instructions should do; i'll check for you tomorrow; important questions: since you started two mail threads..... with traces .... do you think these are related? aren't we mixing things? regards Dannes |
From: Dannes W. <di...@ex...> - 2013-07-30 20:51:33
|
On 30 Jul 2013, at 21:29 , Immanuel Normann <imm...@gm...> wrote: > it is true that Dmitriy answered my question in this mail thread already and it was a solution for the where I rebuilt the downloaded the stable existdb 2.1. > But it wasn't a solution for the new case where I built the latest master release from github. My last mail in this thread makes the steps explicit including also Dmitriy's instructions: > "copied svnkit.jar & svnkit-cli.jar to lib/users from http://www.svnkit.com/org.tmatesoft.svn_1.3.3.standalone.zip" when I build exist-db with the SVN extension, thenonly think I have to do is to change the property "include.feature.svn" in extensions/build.properties change # SVN extension include.feature.svn = true running "./build.sh" [[not ant?]] yields into the following: all: [echo] ==================================================================== [echo] Extension 'svn' ('svn') [echo] ==================================================================== dist: [echo] Generating jar for 'svn' compile: [echo] Compiling 'svn' init: [echo] Initializing 'svn' download-3rd-party: [echo] Retrieving 3rd party jar files 'svn' [fetch] Getting: http://www.svnkit.com/org.tmatesoft.svn_1.3.3.standalone.zip [fetch] To: /var/folders/qc/zpzw4s_j3f1bsfl98nnlgxmm0000gn/T/FetchTask3229778457559567910tmp [fetch] .................................................... [fetch] .................................................... [fetch] .................................................... etc compile-src: [echo] Compiling sources 'svn' [mkdir] Created dir: /...../exist/extensions/svn/build/classes [javac] Compiling 187 source files to /......exist/extensions/svn/build/classes [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.6 [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 1 warning compile-test: [echo] Compiling tests 'svn' [mkdir] Created dir: /....../exist/extensions/svn/build/test/classes [javac] Compiling 8 source files to /....../exist/extensions/svn/build/test/classes [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.6 [javac] 1 warning [copy] Copying 16 files to /....../exist/extensions/svn/build/classes [jar] Building jar: /......../exist/lib/extensions/exist-svn.jar that's what it needs for me to get it built..... There is no manual download required. please check for any svn jar files on any location, and remove them find . -name "svn*jar" regards Dannes |
From: Immanuel N. <imm...@gm...> - 2013-07-30 20:53:55
|
Hi, in the other thread "error in startup of clean build of trunk" the subversion module isn't mentioned at all. It is is only related to this thread due to my (futile) attempt to overcome the subversion module issue by compiling the master release from github instead of the stable download. Since it turned out that this master release has also issues with the subversion module I thought this thread here is the right place to discuss it. Anyway, thanks for your help! regards 2013/7/30 Dannes Wessels <di...@ex...> > Hi, > > On 30 Jul 2013, at 21:29 , Immanuel Normann <imm...@gm...> > wrote: > > Yet, the built failed as described above. I don't see what else I could > have missed from Dmitriy's answer. > > > the instructions should do; i'll check for you tomorrow; > > important questions: since you started two mail threads..... with traces > .... do you think these are related? aren't we mixing things? > > regards > > Dannes > > |
From: Dannes W. <di...@ex...> - 2013-07-30 20:58:40
|
On 30 Jul 2013, at 22:53 , Immanuel Normann <imm...@gm...> wrote: > in the other thread "error in startup of clean build of trunk" the subversion module isn't mentioned at all. I know, but since this thread is getting long, I wanted to x-check > It is is only related to this thread due to my (futile) attempt to overcome the subversion module issue by compiling the master release from github instead of the stable download. > Since it turned out that this master release has also issues with the subversion module I thought this thread here is the right place to discuss it. sure; but as I copied in, the build on the github-branche is working just fine [for me], like it has been doing for a long time.... regards Dannes |
From: Immanuel N. <imm...@gm...> - 2013-07-31 08:21:02
|
Hi Dannes, The trouble I had was due to the two files svnkit.jar and svnkit-cli.jar which I copied into $EXIST_HOME/lib/user/ following Dmitiy's instructions. Now, I learned (after testing myself) that this worked only for the stable downloadable 2.1 version, but not for the master release from github. <di...@ex...> > > > when I build exist-db with the SVN extension, then only think I have to do > is to change the property "include.feature.svn" in > extensions/build.properties > > change > > # SVN extension > include.feature.svn = *true* > > that's what it needs for me to get it built..... There is no manual > download required. please check for any svn jar files on any location, and > remove them > > find . -name "svn*jar" > Eventually, after removing these two files my build works fine as well. Yet, there is a (hopefully) last question: how can I import the subversion module? When I type import module namespace subversion = " http://exist-db.org/xquery/versioning/svn"; it displays this: error found while loading module subversion: failed to load module: ' http://exist-db.org/xquery/versioning/svn' from: ' http://exist-db.org/xquery/versioning/svn', location: ' http://exist-db.org/xquery/versioning/svn'. Source not found. Following the documentation at http://exist-db.org/exist/apps/doc/subversion-module.xml I uncommented the following line in the conf.xml file: <module uri="http://exist-db.org/xquery/versioning/svn" class="org.exist.versioning.svn.xquery.SVNModule" /> But that didn't have any effect. |
From: Dmitriy S. <sha...@gm...> - 2013-07-31 08:39:16
|
On Wed, Jul 31, 2013 at 12:20 PM, Immanuel Normann < imm...@gm...> wrote: > Yet, there is a (hopefully) last question: how can I import the subversion > module? > When I type > > import module namespace subversion = " > http://exist-db.org/xquery/versioning/svn"; > > it displays this: > > error found while loading module subversion: failed to load module: ' > http://exist-db.org/xquery/versioning/svn' from: ' > http://exist-db.org/xquery/versioning/svn', location: ' > http://exist-db.org/xquery/versioning/svn'. Source not found. > > Following the documentation at > http://exist-db.org/exist/apps/doc/subversion-module.xml > I uncommented the following line in the conf.xml file: > <module uri="http://exist-db.org/xquery/versioning/svn" > class="org.exist.versioning.svn.xquery.SVNModule" /> > > But that didn't have any effect. > Did you restart eXist after that? -- Dmitriy Shabanov |
From: Dannes W. <da...@ex...> - 2013-07-31 11:18:12
|
HI, from your build log the svn module is not built at all.....: all: [echo] ==================================================================== [echo] Extension 'svn' ('svn') [echo] ==================================================================== did you enable the extension in extension/build.properties or better extension/local.build.properties ? greets Dannes |
From: Immanuel N. <imm...@gm...> - 2013-07-31 13:37:43
|
Of cause, I had set "include.feature.svn = true" in $EXIST_HOME/extensions/build.properties BUT not in $EXIST_HOME/extensions/local.build.properties In fact http://exist-db.org/exist/apps/doc/subversion-module.xml doesn't mention this local.build.properties, at all. It even doesn't exist by default - one has to create it first. Eventually I also found a sort of hidden hint in conf.xml: - the following steps might be required: - copy extensions/build.properties to extensions/local.build.properties - edit extensions/local.build.properties - build modules with "./build.sh extension-modules" with include.feature.svn = true in $EXIST_HOME/extensions/local.build.properties it finally worked! This bit of info should go into the documentation at http://exist-db.org/exist/apps/doc/subversion-module.xml in order to spare others this trouble. Anyway, thanks for helping me so patiently! Regards Immanuel 2013/7/31 Dannes Wessels <da...@ex...> > HI, > > from your build log the svn module is not built at all.....: > > > all: > [echo] > ==================================================================== > [echo] Extension 'svn' ('svn') > [echo] > ==================================================================== > > did you enable the extension in extension/build.properties or better > extension/local.build.properties ? > > greets > > Dannes > > |
From: Immanuel N. <imm...@gm...> - 2015-01-27 13:10:35
|
Hi, after one and half year I experience again the same issues with the subversion module. This time with exist 2.2 (project.built=20141120124006). Again I followed the instructions from http://exist-db.org/exist/apps/doc/subversion-module.xml in some variants. I say variants because still these instructions are not clear in detail. It says: In the $EXIST_HOME/extensions/build.properties file set the svn feature to > be true > > include.feature.svn = true > So I did this. But I also made a copy of build.properties to local.build.properties, because this is what you can read in the header of build.properties: "Don't directly modify this file. Instead, copy it to local.build.properties and edit that" - something similar can be read in conf.xml. Next I followed the unambigous instruction: Then uncomment the following line in the conf.xml file: > > <module uri="http://exist-db.org/xquery/versioning/svn" > class="org.exist.versioning.svn.xquery.SVNModule" /> > In fact this line was already uncommented in the exist 2.2 built. Next I sopped the server. Finally the instruction says: Recompile the eXist system using the build script. > Again this is a rather unspecific instruction. I tried two variants (from the exist home directory): ./build.sh ./build.sh extension-modules Then I started the server. In the end it doesn't seem to work: when I try to import the module with import module namespace subversion = " > http://exist-db.org/xquery/versioning/svn"; > I get the error message: "failed to load module" How can I check whether the build process produced anything svn related? The build protocol says this: git.details: > > dist: > > all: > [echo] > ==================================================================== > [echo] Extension 'svn' ('svn') > [echo] > ==================================================================== > > git.details: > > dist: > I figured out that the build process finally creates a lib/extensions/exist-modules.jar. However, inside this jar there is no svn-module listet. Appearently, something is wrong with the build process as far as the svn module is concerned. Any help would be greatly appreciated! Regards Immanuel 2013-07-31 15:37 GMT+02:00 Immanuel Normann <imm...@gm...>: > Of cause, I had set "include.feature.svn = true" > in $EXIST_HOME/extensions/build.properties > > BUT not in $EXIST_HOME/extensions/local.build.properties > > In fact http://exist-db.org/exist/apps/doc/subversion-module.xml > doesn't mention this local.build.properties, at all. It even doesn't exist > by default - one has to create it first. > > Eventually I also found a sort of hidden hint in conf.xml: > > - the following steps might be required: > - copy extensions/build.properties to > extensions/local.build.properties > - edit extensions/local.build.properties > - build modules with "./build.sh extension-modules" > > with include.feature.svn = true > in $EXIST_HOME/extensions/local.build.properties > it finally worked! > > This bit of info should go into the documentation at > http://exist-db.org/exist/apps/doc/subversion-module.xml in order to > spare others this trouble. > > Anyway, thanks for helping me so patiently! > > Regards > Immanuel > > > 2013/7/31 Dannes Wessels <da...@ex...> > >> HI, >> >> from your build log the svn module is not built at all.....: >> >> >> all: >> [echo] >> ==================================================================== >> [echo] Extension 'svn' ('svn') >> [echo] >> ==================================================================== >> >> did you enable the extension in extension/build.properties or better >> extension/local.build.properties ? >> >> greets >> >> Dannes >> >> > |
From: Adam R. <ad...@ex...> - 2015-01-27 14:16:42
|
Is there any whitespace around the 'true' in your build.local.properties file? This has tripped many up in the past On 27 Jan 2015 13:11, "Immanuel Normann" <imm...@gm...> wrote: > Hi, > > after one and half year I experience again the same issues with the > subversion module. This time with exist 2.2 (project.built=20141120124006). > > Again I followed the instructions from > http://exist-db.org/exist/apps/doc/subversion-module.xml in some > variants. I say variants because still these instructions are not clear in > detail. > It says: > > In the $EXIST_HOME/extensions/build.properties file set the svn feature to >> be true >> >> include.feature.svn = true >> > > So I did this. But I also made a copy of build.properties to > local.build.properties, because this is what you can read in the header of > build.properties: "Don't directly modify this file. Instead, copy it to > local.build.properties and edit that" - something similar can be read in > conf.xml. > > Next I followed the unambigous instruction: > > Then uncomment the following line in the conf.xml file: >> >> <module uri="http://exist-db.org/xquery/versioning/svn" >> class="org.exist.versioning.svn.xquery.SVNModule" /> >> > > In fact this line was already uncommented in the exist 2.2 built. > > Next I sopped the server. > > Finally the instruction says: > > Recompile the eXist system using the build script. >> > > Again this is a rather unspecific instruction. I tried two variants (from > the exist home directory): > > ./build.sh > ./build.sh extension-modules > > Then I started the server. > > In the end it doesn't seem to work: when I try to import the module with > > import module namespace subversion = " >> http://exist-db.org/xquery/versioning/svn"; >> > > I get the error message: "failed to load module" > > How can I check whether the build process produced anything svn related? > > The build protocol says this: > > git.details: >> >> dist: >> >> all: >> [echo] >> ==================================================================== >> [echo] Extension 'svn' ('svn') >> [echo] >> ==================================================================== >> >> git.details: >> >> dist: >> > > I figured out that the build process finally creates a > lib/extensions/exist-modules.jar. > However, inside this jar there is no svn-module listet. > > Appearently, something is wrong with the build process as far as the svn > module is concerned. > Any help would be greatly appreciated! > > Regards > Immanuel > > > > > > 2013-07-31 15:37 GMT+02:00 Immanuel Normann <imm...@gm...>: > >> Of cause, I had set "include.feature.svn = true" >> in $EXIST_HOME/extensions/build.properties >> >> BUT not in $EXIST_HOME/extensions/local.build.properties >> >> In fact http://exist-db.org/exist/apps/doc/subversion-module.xml >> doesn't mention this local.build.properties, at all. It even doesn't >> exist by default - one has to create it first. >> >> Eventually I also found a sort of hidden hint in conf.xml: >> >> - the following steps might be required: >> - copy extensions/build.properties to >> extensions/local.build.properties >> - edit extensions/local.build.properties >> - build modules with "./build.sh extension-modules" >> >> with include.feature.svn = true >> in $EXIST_HOME/extensions/local.build.properties >> it finally worked! >> >> This bit of info should go into the documentation at >> http://exist-db.org/exist/apps/doc/subversion-module.xml in order to >> spare others this trouble. >> >> Anyway, thanks for helping me so patiently! >> >> Regards >> Immanuel >> >> >> 2013/7/31 Dannes Wessels <da...@ex...> >> >>> HI, >>> >>> from your build log the svn module is not built at all.....: >>> >>> >>> all: >>> [echo] >>> ==================================================================== >>> [echo] Extension 'svn' ('svn') >>> [echo] >>> ==================================================================== >>> >>> did you enable the extension in extension/build.properties or better >>> extension/local.build.properties ? >>> >>> greets >>> >>> Dannes >>> >>> >> > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > > |
From: Immanuel N. <imm...@gm...> - 2015-01-28 09:37:24
|
Yeah, you hit the point! There was a blank after "true". May be it would be a good idea to trim the property-values during the build process. I mean a value with whitespace at the end shouldn't be a permissable value anyway (unless you want to attrack whitespace coding to existdb - s. http://en.wikipedia.org/wiki/Whitespace_%28programming_language%29) Anyway, thanks for the valuable hint! Regards Immanuel 2015-01-27 15:16 GMT+01:00 Adam Retter <ad...@ex...>: > Is there any whitespace around the 'true' in your build.local.properties > file? This has tripped many up in the past > On 27 Jan 2015 13:11, "Immanuel Normann" <imm...@gm...> > wrote: > >> Hi, >> >> after one and half year I experience again the same issues with the >> subversion module. This time with exist 2.2 (project.built=20141120124006). >> >> Again I followed the instructions from >> http://exist-db.org/exist/apps/doc/subversion-module.xml in some >> variants. I say variants because still these instructions are not clear in >> detail. >> It says: >> >> In the $EXIST_HOME/extensions/build.properties file set the svn feature >>> to be true >>> >>> include.feature.svn = true >>> >> >> So I did this. But I also made a copy of build.properties to >> local.build.properties, because this is what you can read in the header of >> build.properties: "Don't directly modify this file. Instead, copy it to >> local.build.properties and edit that" - something similar can be read in >> conf.xml. >> >> Next I followed the unambigous instruction: >> >> Then uncomment the following line in the conf.xml file: >>> >>> <module uri="http://exist-db.org/xquery/versioning/svn" >>> class="org.exist.versioning.svn.xquery.SVNModule" /> >>> >> >> In fact this line was already uncommented in the exist 2.2 built. >> >> Next I sopped the server. >> >> Finally the instruction says: >> >> Recompile the eXist system using the build script. >>> >> >> Again this is a rather unspecific instruction. I tried two variants (from >> the exist home directory): >> >> ./build.sh >> ./build.sh extension-modules >> >> Then I started the server. >> >> In the end it doesn't seem to work: when I try to import the module with >> >> import module namespace subversion = " >>> http://exist-db.org/xquery/versioning/svn"; >>> >> >> I get the error message: "failed to load module" >> >> How can I check whether the build process produced anything svn related? >> >> The build protocol says this: >> >> git.details: >>> >>> dist: >>> >>> all: >>> [echo] >>> ==================================================================== >>> [echo] Extension 'svn' ('svn') >>> [echo] >>> ==================================================================== >>> >>> git.details: >>> >>> dist: >>> >> >> I figured out that the build process finally creates a >> lib/extensions/exist-modules.jar. >> However, inside this jar there is no svn-module listet. >> >> Appearently, something is wrong with the build process as far as the svn >> module is concerned. >> Any help would be greatly appreciated! >> >> Regards >> Immanuel >> >> >> >> >> >> 2013-07-31 15:37 GMT+02:00 Immanuel Normann <imm...@gm...>: >> >>> Of cause, I had set "include.feature.svn = true" >>> in $EXIST_HOME/extensions/build.properties >>> >>> BUT not in $EXIST_HOME/extensions/local.build.properties >>> >>> In fact http://exist-db.org/exist/apps/doc/subversion-module.xml >>> doesn't mention this local.build.properties, at all. It even doesn't >>> exist by default - one has to create it first. >>> >>> Eventually I also found a sort of hidden hint in conf.xml: >>> >>> - the following steps might be required: >>> - copy extensions/build.properties to >>> extensions/local.build.properties >>> - edit extensions/local.build.properties >>> - build modules with "./build.sh extension-modules" >>> >>> with include.feature.svn = true >>> in $EXIST_HOME/extensions/local.build.properties >>> it finally worked! >>> >>> This bit of info should go into the documentation at >>> http://exist-db.org/exist/apps/doc/subversion-module.xml in order to >>> spare others this trouble. >>> >>> Anyway, thanks for helping me so patiently! >>> >>> Regards >>> Immanuel >>> >>> >>> 2013/7/31 Dannes Wessels <da...@ex...> >>> >>>> HI, >>>> >>>> from your build log the svn module is not built at all.....: >>>> >>>> >>>> all: >>>> [echo] >>>> ==================================================================== >>>> [echo] Extension 'svn' ('svn') >>>> [echo] >>>> ==================================================================== >>>> >>>> did you enable the extension in extension/build.properties or better >>>> extension/local.build.properties ? >>>> >>>> greets >>>> >>>> Dannes >>>> >>>> >>> >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming. The Go Parallel Website, >> sponsored by Intel and developed in partnership with Slashdot Media, is >> your >> hub for all things parallel software development, from weekly thought >> leadership blogs to news, videos, case studies, tutorials and more. Take a >> look and join the conversation now. http://goparallel.sourceforge.net/ >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> >> |