Menu
▾
▴
exist-development — eXist Developer's List
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(22) |
Nov
(85) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(47) |
Feb
(127) |
Mar
(268) |
Apr
(78) |
May
(47) |
Jun
(38) |
Jul
(131) |
Aug
(221) |
Sep
(187) |
Oct
(54) |
Nov
(111) |
Dec
(84) |
| 2011 |
Jan
(152) |
Feb
(106) |
Mar
(94) |
Apr
(90) |
May
(53) |
Jun
(20) |
Jul
(24) |
Aug
(37) |
Sep
(32) |
Oct
(70) |
Nov
(22) |
Dec
(15) |
| 2012 |
Jan
(33) |
Feb
(110) |
Mar
(24) |
Apr
(1) |
May
(11) |
Jun
(8) |
Jul
(12) |
Aug
(37) |
Sep
(39) |
Oct
(81) |
Nov
(38) |
Dec
(50) |
| 2013 |
Jan
(23) |
Feb
(53) |
Mar
(23) |
Apr
(5) |
May
(19) |
Jun
(16) |
Jul
(16) |
Aug
(9) |
Sep
(21) |
Oct
(1) |
Nov
(2) |
Dec
(8) |
| 2014 |
Jan
(16) |
Feb
(6) |
Mar
(27) |
Apr
(1) |
May
(10) |
Jun
(1) |
Jul
(4) |
Aug
(10) |
Sep
(19) |
Oct
(22) |
Nov
(4) |
Dec
(6) |
| 2015 |
Jan
(3) |
Feb
(6) |
Mar
(9) |
Apr
|
May
(11) |
Jun
(23) |
Jul
(14) |
Aug
(10) |
Sep
(10) |
Oct
(9) |
Nov
(18) |
Dec
(4) |
| 2016 |
Jan
(5) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(15) |
Jun
(2) |
Jul
(8) |
Aug
(2) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
(12) |
Mar
(22) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(7) |
Oct
(19) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Loren C. <lor...@gm...> - 2015-09-29 10:43:30
|
I updated the xmlcalabash pom entry to <dependency> <groupId>com.rackspace.xmlcalabash</groupId> <artifactId>xmlcalabash-saxon94</artifactId> <version>1.0.16</version> </dependency> and got the following while compiling [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 12.995 s [INFO] Finished at: 2015-09-29T06:41:00-04:00 [INFO] Final Memory: 9M/245M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project XMLCalabash: Could not resolve dependencies for project org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > On Sep 29, 2015, at 6:29 AM, Loren Cahlander <lor...@gm...> wrote: > > > I updated the pom.xml file from https://github.com/eXist-db/eXist-XMLCalabash <https://github.com/eXist-db/eXist-XMLCalabash> > > to > > project xmlns="http://maven.apache.org/POM/4.0.0 <http://maven.apache.org/POM/4.0.0>" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance <http://www.w3.org/2001/XMLSchema-instance>" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 <http://maven.apache.org/POM/4.0.0> http://maven.apache.org/xsd/maven-4.0.0.xsd <http://maven.apache.org/xsd/maven-4.0.0.xsd>"> > <modelVersion>4.0.0</modelVersion> > <groupId>org.exist-db</groupId> > <artifactId>XMLCalabash</artifactId> > <version>0.1.7-SNAPSHOT</version> > <url>http://www.exist-db.org</url> <http://www.exist-db.org</url>> > > <organization> > <name>eXist Solutions</name> > <url>http://www.existsolutions.com</url> <http://www.existsolutions.com</url>> > </organization> > > <dependencies> > <!-- eXistDB Library --> > <dependency> > <groupId>org.exist-db</groupId> > <artifactId>existdb-core</artifactId> > <version>3.0.RC1</version> > </dependency> > <dependency> > <groupId>com.xmlcalabash</groupId> > <artifactId>xmlcalabash-saxon94</artifactId> > <version>1.0.14-SNAPSHOT</version> > </dependency> > > <dependency> > <groupId>junit</groupId> > <artifactId>junit</artifactId> > <version>4.4</version> > <scope>test</scope> > </dependency> > </dependencies> > > <build> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-compiler-plugin</artifactId> > <version>2.3.2</version> > <configuration> > <source>1.7</source> > <target>1.7</target> > </configuration> > </plugin> > </plugins> > </build> > > <repositories> > <repository> > <id>eXistDB</id> > <url>https://raw.github.com/eXist-db/mvn-repo/master/</url> <https://raw.github.com/eXist-db/mvn-repo/master/%3C/url%3E> > </repository> > </repositories> > > </project> > > > > > when I ran ‘mvn -X compile’ I got the following errors > > > ldc:eXist-XMLCalabash lcahlander$ mvn -X compile > Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T07:57:37-04:00) > Maven home: /usr/local/Cellar/maven/3.3.3/libexec > Java version: 1.8.0_60, vendor: Oracle Corporation > Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.11.1", arch: "x86_64", family: "mac" > [DEBUG] Created new class realm maven.api > [DEBUG] Importing foreign packages into class realm maven.api > [DEBUG] Imported: javax.enterprise.inject.* < plexus.core > [DEBUG] Imported: javax.enterprise.util.* < plexus.core > [DEBUG] Imported: javax.inject.* < plexus.core > [DEBUG] Imported: org.apache.maven.* < plexus.core > [DEBUG] Imported: org.apache.maven.artifact < plexus.core > [DEBUG] Imported: org.apache.maven.classrealm < plexus.core > [DEBUG] Imported: org.apache.maven.cli < plexus.core > [DEBUG] Imported: org.apache.maven.configuration < plexus.core > [DEBUG] Imported: org.apache.maven.exception < plexus.core > [DEBUG] Imported: org.apache.maven.execution < plexus.core > [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core > [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core > [DEBUG] Imported: org.apache.maven.model < plexus.core > [DEBUG] Imported: org.apache.maven.monitor < plexus.core > [DEBUG] Imported: org.apache.maven.plugin < plexus.core > [DEBUG] Imported: org.apache.maven.profiles < plexus.core > [DEBUG] Imported: org.apache.maven.project < plexus.core > [DEBUG] Imported: org.apache.maven.reporting < plexus.core > [DEBUG] Imported: org.apache.maven.repository < plexus.core > [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core > [DEBUG] Imported: org.apache.maven.settings < plexus.core > [DEBUG] Imported: org.apache.maven.toolchain < plexus.core > [DEBUG] Imported: org.apache.maven.usability < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core > [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core > [DEBUG] Imported: org.codehaus.classworlds < plexus.core > [DEBUG] Imported: org.codehaus.plexus.* < plexus.core > [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core > [DEBUG] Imported: org.codehaus.plexus.component < plexus.core > [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core > [DEBUG] Imported: org.codehaus.plexus.container < plexus.core > [DEBUG] Imported: org.codehaus.plexus.context < plexus.core > [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core > [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core > [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core > [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core > [DEBUG] Imported: org.eclipse.aether.* < plexus.core > [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core > [DEBUG] Imported: org.eclipse.aether.collection < plexus.core > [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core > [DEBUG] Imported: org.eclipse.aether.graph < plexus.core > [DEBUG] Imported: org.eclipse.aether.impl < plexus.core > [DEBUG] Imported: org.eclipse.aether.installation < plexus.core > [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core > [DEBUG] Imported: org.eclipse.aether.metadata < plexus.core > [DEBUG] Imported: org.eclipse.aether.repository < plexus.core > [DEBUG] Imported: org.eclipse.aether.resolution < plexus.core > [DEBUG] Imported: org.eclipse.aether.spi < plexus.core > [DEBUG] Imported: org.eclipse.aether.transfer < plexus.core > [DEBUG] Imported: org.eclipse.aether.version < plexus.core > [DEBUG] Imported: org.slf4j.* < plexus.core > [DEBUG] Imported: org.slf4j.spi.* < plexus.core > [DEBUG] Populating class realm maven.api > [INFO] Error stacktraces are turned on. > [DEBUG] Reading global settings from /usr/local/Cellar/maven/3.3.3/libexec/conf/settings.xml > [DEBUG] Reading user settings from /Users/lcahlander/.m2/settings.xml > [DEBUG] Reading global toolchains from /usr/local/Cellar/maven/3.3.3/libexec/conf/toolchains.xml > [DEBUG] Reading user toolchains from /Users/lcahlander/.m2/toolchains.xml > [DEBUG] Using local repository at /Users/lcahlander/.m2/repository > [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for /Users/lcahlander/.m2/repository > [INFO] Scanning for projects... > [DEBUG] Extension realms for project org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT: (none) > [DEBUG] Looking up lifecyle mappings for packaging jar from ClassRealm[plexus.core, parent: null] > [DEBUG] === REACTOR BUILD PLAN ================================================ > [DEBUG] Project: org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT > [DEBUG] Tasks: [compile] > [DEBUG] Style: Regular > [DEBUG] ======================================================================= > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building XMLCalabash 0.1.7-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] > [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] > [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.pom <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.pom> > Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.pom <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.pom> (8 KB at 11.6 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.pom.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom> > Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom> (9 KB at 112.3 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-plugins/23/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/22/maven-parent-22.pom <https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/22/maven-parent-22.pom> > Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/22/maven-parent-22.pom <https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/22/maven-parent-22.pom> (30 KB at 279.3 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/maven-parent/22/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/maven-parent/22/maven-parent-22.pom.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom <https://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom> > Downloaded: https://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom <https://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom> (15 KB at 174.3 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/apache/11/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/apache/11/apache-11.pom.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar> > Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar> (29 KB at 294.2 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom> > Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom> (8 KB at 99.4 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom> > Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom> (13 KB at 169.3 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-plugins/18/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/16/maven-parent-16.pom <https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/16/maven-parent-16.pom> > Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/16/maven-parent-16.pom <https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/16/maven-parent-16.pom> (23 KB at 291.4 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/maven-parent/16/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/maven-parent/16/maven-parent-16.pom.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/apache/apache/7/apache-7.pom <https://repo.maven.apache.org/maven2/org/apache/apache/7/apache-7.pom> > Downloaded: https://repo.maven.apache.org/maven2/org/apache/apache/7/apache-7.pom <https://repo.maven.apache.org/maven2/org/apache/apache/7/apache-7.pom> (15 KB at 183.0 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/apache/7/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/apache/7/apache-7.pom.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.jar <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.jar> > Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.jar <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.jar> (29 KB at 379.9 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.jar.lastUpdated > [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] > [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] > [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] > [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] > [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] > [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] > [DEBUG] === PROJECT BUILD PLAN ================================================ > [DEBUG] Project: org.exist-db:XMLCalabash:0.1.7-SNAPSHOT > [DEBUG] Dependencies (collect): [] > [DEBUG] Dependencies (resolve): [compile] > [DEBUG] Repositories (dependencies): [eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/>, default, releases+snapshots), central (https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2>, default, releases)] > [DEBUG] Repositories (plugins) : [central (https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2>, default, releases)] > [DEBUG] ----------------------------------------------------------------------- > [DEBUG] Goal: org.apache.maven.plugins:maven-resources-plugin:2.6:resources (default-resources) > [DEBUG] Style: Regular > [DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?> > <configuration> > <buildFilters default-value="${project.build.filters}"/> > <encoding default-value="${project.build.sourceEncoding}">${encoding}</encoding> > <escapeString>${maven.resources.escapeString}</escapeString> > <escapeWindowsPaths default-value="true">${maven.resources.escapeWindowsPaths}</escapeWindowsPaths> > <includeEmptyDirs default-value="false">${maven.resources.includeEmptyDirs}</includeEmptyDirs> > <outputDirectory default-value="${project.build.outputDirectory}"/> > <overwrite default-value="false">${maven.resources.overwrite}</overwrite> > <project default-value="${project}"/> > <resources default-value="${project.resources}"/> > <session default-value="${session}"/> > <supportMultiLineFiltering default-value="false">${maven.resources.supportMultiLineFiltering}</supportMultiLineFiltering> > <useBuildFilters default-value="true"/> > <useDefaultDelimiters default-value="true"/> > </configuration> > [DEBUG] ----------------------------------------------------------------------- > [DEBUG] Goal: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) > [DEBUG] Style: Regular > [DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?> > <configuration> > <basedir default-value="${basedir}"/> > <buildDirectory default-value="${project.build.directory}"/> > <classpathElements default-value="${project.compileClasspathElements}"/> > <compileSourceRoots default-value="${project.compileSourceRoots}"/> > <compilerId default-value="javac">${maven.compiler.compilerId}</compilerId> > <compilerVersion>${maven.compiler.compilerVersion}</compilerVersion> > <debug default-value="true">${maven.compiler.debug}</debug> > <debuglevel>${maven.compiler.debuglevel}</debuglevel> > <encoding default-value="${project.build.sourceEncoding}">${encoding}</encoding> > <executable>${maven.compiler.executable}</executable> > <failOnError default-value="true">${maven.compiler.failOnError}</failOnError> > <fork default-value="false">${maven.compiler.fork}</fork> > <generatedSourcesDirectory default-value="${project.build.directory}/generated-sources/annotations"/> > <maxmem>${maven.compiler.maxmem}</maxmem> > <meminitial>${maven.compiler.meminitial}</meminitial> > <optimize default-value="false">${maven.compiler.optimize}</optimize> > <outputDirectory default-value="${project.build.outputDirectory}"/> > <outputFileName>${project.build.finalName}</outputFileName> > <projectArtifact default-value="${project.artifact}"/> > <session default-value="${session}"/> > <showDeprecation default-value="false">${maven.compiler.showDeprecation}</showDeprecation> > <showWarnings default-value="false">${maven.compiler.showWarnings}</showWarnings> > <source default-value="1.5">1.7</source> > <staleMillis default-value="0">${lastModGranularityMs}</staleMillis> > <target default-value="1.5">1.7</target> > <verbose default-value="false">${maven.compiler.verbose}</verbose> > </configuration> > [DEBUG] ======================================================================= > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> > Downloading: https://raw.github.com/eXist-db/mvn-repo/master/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.pom <https://raw.github.com/eXist-db/mvn-repo/master/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.pom> > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.pom.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.pom <https://repo.maven.apache.org/maven2/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.pom> > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.pom.lastUpdated > [WARNING] The POM for org.exist-db:existdb-core:jar:3.0.RC1 is missing, no dependency information available > [DEBUG] Could not find metadata com.xmlcalabash:xmlcalabash-saxon94:1.0.14-SNAPSHOT/maven-metadata.xml in local (/Users/lcahlander/.m2/repository) > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> > Downloading: https://raw.github.com/eXist-db/mvn-repo/master/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/maven-metadata.xml <https://raw.github.com/eXist-db/mvn-repo/master/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/maven-metadata.xml> > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/resolver-status.properties > [DEBUG] Could not find metadata com.xmlcalabash:xmlcalabash-saxon94:1.0.14-SNAPSHOT/maven-metadata.xml in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/>) > [DEBUG] Could not find metadata com.xmlcalabash:xmlcalabash-saxon94:1.0.14-SNAPSHOT/maven-metadata.xml in local (/Users/lcahlander/.m2/repository) > [DEBUG] Skipped remote request for com.xmlcalabash:xmlcalabash-saxon94:1.0.14-SNAPSHOT/maven-metadata.xml, already updated during this session. > [DEBUG] Failure to find com.xmlcalabash:xmlcalabash-saxon94:1.0.14-SNAPSHOT/maven-metadata.xml in https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> was cached in the local repository, resolution will not be reattempted until the update interval of eXistDB has elapsed or updates are forced > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> > Downloading: https://raw.github.com/eXist-db/mvn-repo/master/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/xmlcalabash-saxon94-1.0.14-SNAPSHOT.pom <https://raw.github.com/eXist-db/mvn-repo/master/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/xmlcalabash-saxon94-1.0.14-SNAPSHOT.pom> > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/xmlcalabash-saxon94-1.0.14-SNAPSHOT.pom.lastUpdated > [WARNING] The POM for com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT is missing, no dependency information available > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> > Downloading: https://raw.github.com/eXist-db/mvn-repo/master/junit/junit/4.4/junit-4.4.pom <https://raw.github.com/eXist-db/mvn-repo/master/junit/junit/4.4/junit-4.4.pom> > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/junit/junit/4.4/junit-4.4.pom.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/junit/junit/4.4/junit-4.4.pom <https://repo.maven.apache.org/maven2/junit/junit/4.4/junit-4.4.pom> > Downloaded: https://repo.maven.apache.org/maven2/junit/junit/4.4/junit-4.4.pom <https://repo.maven.apache.org/maven2/junit/junit/4.4/junit-4.4.pom> (2 KB at 8.8 KB/sec) > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/junit/junit/4.4/_remote.repositories > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/junit/junit/4.4/junit-4.4.pom.lastUpdated > [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=1, ConflictMarker.markTime=0, ConflictMarker.nodeCount=4, ConflictIdSorter.graphTime=1, ConflictIdSorter.topsortTime=0, ConflictIdSorter.conflictIdCount=3, ConflictIdSorter.conflictIdCycleCount=0, ConflictResolver.totalTime=3, ConflictResolver.conflictItemCount=3, DefaultDependencyCollector.collectTime=1826, DefaultDependencyCollector.transformTime=7} > [DEBUG] org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT > [DEBUG] org.exist-db:existdb-core:jar:3.0.RC1:compile > [DEBUG] com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT:compile > [DEBUG] junit:junit:jar:4.4:test > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/> > Downloading: https://raw.github.com/eXist-db/mvn-repo/master/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.jar <https://raw.github.com/eXist-db/mvn-repo/master/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.jar> > Downloading: https://raw.github.com/eXist-db/mvn-repo/master/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/xmlcalabash-saxon94-1.0.14-SNAPSHOT.jar <https://raw.github.com/eXist-db/mvn-repo/master/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/xmlcalabash-saxon94-1.0.14-SNAPSHOT.jar> > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.jar.lastUpdated > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/xmlcalabash-saxon94-1.0.14-SNAPSHOT.jar.lastUpdated > [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 <https://repo.maven.apache.org/maven2> > Downloading: https://repo.maven.apache.org/maven2/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.jar <https://repo.maven.apache.org/maven2/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.jar> > [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.jar.lastUpdated > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 4.035 s > [INFO] Finished at: 2015-09-29T06:15:10-04:00 > [INFO] Final Memory: 13M/309M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project XMLCalabash: Could not resolve dependencies for project org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT: The following artifacts could not be resolved: org.exist-db:existdb-core:jar:3.0.RC1, com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/>) -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project XMLCalabash: Could not resolve dependencies for project org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT: The following artifacts could not be resolved: org.exist-db:existdb-core:jar:3.0.RC1, com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/>) > at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:221) > at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127) > at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT: The following artifacts could not be resolved: org.exist-db:existdb-core:jar:3.0.RC1, com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/>) > at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:211) > at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195) > ... 23 more > Caused by: org.eclipse.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: org.exist-db:existdb-core:jar:3.0.RC1, com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/>) > at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384) > at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:205) > ... 24 more > Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: The following artifacts could not be resolved: org.exist-db:existdb-core:jar:3.0.RC1, com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/>) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) > at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) > at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367) > ... 25 more > Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/ <https://raw.github.com/eXist-db/mvn-repo/master/>) > at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:39) > at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355) > at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > [ERROR] > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException <http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException> > ldc:eXist-XMLCalabash lcahlander$ > |
|
From: Loren C. <lor...@gm...> - 2015-09-29 10:30:18
|
I updated the pom.xml file from https://github.com/eXist-db/eXist-XMLCalabash <https://github.com/eXist-db/eXist-XMLCalabash> to project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>org.exist-db</groupId> <artifactId>XMLCalabash</artifactId> <version>0.1.7-SNAPSHOT</version> <url>http://www.exist-db.org</url> <organization> <name>eXist Solutions</name> <url>http://www.existsolutions.com</url> </organization> <dependencies> <!-- eXistDB Library --> <dependency> <groupId>org.exist-db</groupId> <artifactId>existdb-core</artifactId> <version>3.0.RC1</version> </dependency> <dependency> <groupId>com.xmlcalabash</groupId> <artifactId>xmlcalabash-saxon94</artifactId> <version>1.0.14-SNAPSHOT</version> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.4</version> <scope>test</scope> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>2.3.2</version> <configuration> <source>1.7</source> <target>1.7</target> </configuration> </plugin> </plugins> </build> <repositories> <repository> <id>eXistDB</id> <url>https://raw.github.com/eXist-db/mvn-repo/master/</url> </repository> </repositories> </project> when I ran ‘mvn -X compile’ I got the following errors ldc:eXist-XMLCalabash lcahlander$ mvn -X compile Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T07:57:37-04:00) Maven home: /usr/local/Cellar/maven/3.3.3/libexec Java version: 1.8.0_60, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.11.1", arch: "x86_64", family: "mac" [DEBUG] Created new class realm maven.api [DEBUG] Importing foreign packages into class realm maven.api [DEBUG] Imported: javax.enterprise.inject.* < plexus.core [DEBUG] Imported: javax.enterprise.util.* < plexus.core [DEBUG] Imported: javax.inject.* < plexus.core [DEBUG] Imported: org.apache.maven.* < plexus.core [DEBUG] Imported: org.apache.maven.artifact < plexus.core [DEBUG] Imported: org.apache.maven.classrealm < plexus.core [DEBUG] Imported: org.apache.maven.cli < plexus.core [DEBUG] Imported: org.apache.maven.configuration < plexus.core [DEBUG] Imported: org.apache.maven.exception < plexus.core [DEBUG] Imported: org.apache.maven.execution < plexus.core [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core [DEBUG] Imported: org.apache.maven.model < plexus.core [DEBUG] Imported: org.apache.maven.monitor < plexus.core [DEBUG] Imported: org.apache.maven.plugin < plexus.core [DEBUG] Imported: org.apache.maven.profiles < plexus.core [DEBUG] Imported: org.apache.maven.project < plexus.core [DEBUG] Imported: org.apache.maven.reporting < plexus.core [DEBUG] Imported: org.apache.maven.repository < plexus.core [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core [DEBUG] Imported: org.apache.maven.settings < plexus.core [DEBUG] Imported: org.apache.maven.toolchain < plexus.core [DEBUG] Imported: org.apache.maven.usability < plexus.core [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core [DEBUG] Imported: org.codehaus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.* < plexus.core [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.component < plexus.core [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core [DEBUG] Imported: org.codehaus.plexus.container < plexus.core [DEBUG] Imported: org.codehaus.plexus.context < plexus.core [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core [DEBUG] Imported: org.eclipse.aether.* < plexus.core [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core [DEBUG] Imported: org.eclipse.aether.collection < plexus.core [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core [DEBUG] Imported: org.eclipse.aether.graph < plexus.core [DEBUG] Imported: org.eclipse.aether.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.installation < plexus.core [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.metadata < plexus.core [DEBUG] Imported: org.eclipse.aether.repository < plexus.core [DEBUG] Imported: org.eclipse.aether.resolution < plexus.core [DEBUG] Imported: org.eclipse.aether.spi < plexus.core [DEBUG] Imported: org.eclipse.aether.transfer < plexus.core [DEBUG] Imported: org.eclipse.aether.version < plexus.core [DEBUG] Imported: org.slf4j.* < plexus.core [DEBUG] Imported: org.slf4j.spi.* < plexus.core [DEBUG] Populating class realm maven.api [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from /usr/local/Cellar/maven/3.3.3/libexec/conf/settings.xml [DEBUG] Reading user settings from /Users/lcahlander/.m2/settings.xml [DEBUG] Reading global toolchains from /usr/local/Cellar/maven/3.3.3/libexec/conf/toolchains.xml [DEBUG] Reading user toolchains from /Users/lcahlander/.m2/toolchains.xml [DEBUG] Using local repository at /Users/lcahlander/.m2/repository [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for /Users/lcahlander/.m2/repository [INFO] Scanning for projects... [DEBUG] Extension realms for project org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT: (none) [DEBUG] Looking up lifecyle mappings for packaging jar from ClassRealm[plexus.core, parent: null] [DEBUG] === REACTOR BUILD PLAN ================================================ [DEBUG] Project: org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT [DEBUG] Tasks: [compile] [DEBUG] Style: Regular [DEBUG] ======================================================================= [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building XMLCalabash 0.1.7-SNAPSHOT [INFO] ------------------------------------------------------------------------ [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.pom (8 KB at 11.6 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.pom.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom (9 KB at 112.3 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-plugins/23/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/22/maven-parent-22.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/22/maven-parent-22.pom (30 KB at 279.3 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/maven-parent/22/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/maven-parent/22/maven-parent-22.pom.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/apache/11/apache-11.pom (15 KB at 174.3 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/apache/11/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/apache/11/apache-11.pom.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar (29 KB at 294.2 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.6/maven-resources-plugin-2.6.jar.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom (8 KB at 99.4 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom (13 KB at 169.3 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-plugins/18/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-plugins/18/maven-plugins-18.pom.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/16/maven-parent-16.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/16/maven-parent-16.pom (23 KB at 291.4 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/maven-parent/16/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/maven-parent/16/maven-parent-16.pom.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/apache/apache/7/apache-7.pom Downloaded: https://repo.maven.apache.org/maven2/org/apache/apache/7/apache-7.pom (15 KB at 183.0 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/apache/7/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/apache/7/apache-7.pom.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.jar Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.jar (29 KB at 379.9 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.jar.lastUpdated [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [DEBUG] === PROJECT BUILD PLAN ================================================ [DEBUG] Project: org.exist-db:XMLCalabash:0.1.7-SNAPSHOT [DEBUG] Dependencies (collect): [] [DEBUG] Dependencies (resolve): [compile] [DEBUG] Repositories (dependencies): [eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/, default, releases+snapshots), central (https://repo.maven.apache.org/maven2, default, releases)] [DEBUG] Repositories (plugins) : [central (https://repo.maven.apache.org/maven2, default, releases)] [DEBUG] ----------------------------------------------------------------------- [DEBUG] Goal: org.apache.maven.plugins:maven-resources-plugin:2.6:resources (default-resources) [DEBUG] Style: Regular [DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?> <configuration> <buildFilters default-value="${project.build.filters}"/> <encoding default-value="${project.build.sourceEncoding}">${encoding}</encoding> <escapeString>${maven.resources.escapeString}</escapeString> <escapeWindowsPaths default-value="true">${maven.resources.escapeWindowsPaths}</escapeWindowsPaths> <includeEmptyDirs default-value="false">${maven.resources.includeEmptyDirs}</includeEmptyDirs> <outputDirectory default-value="${project.build.outputDirectory}"/> <overwrite default-value="false">${maven.resources.overwrite}</overwrite> <project default-value="${project}"/> <resources default-value="${project.resources}"/> <session default-value="${session}"/> <supportMultiLineFiltering default-value="false">${maven.resources.supportMultiLineFiltering}</supportMultiLineFiltering> <useBuildFilters default-value="true"/> <useDefaultDelimiters default-value="true"/> </configuration> [DEBUG] ----------------------------------------------------------------------- [DEBUG] Goal: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) [DEBUG] Style: Regular [DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?> <configuration> <basedir default-value="${basedir}"/> <buildDirectory default-value="${project.build.directory}"/> <classpathElements default-value="${project.compileClasspathElements}"/> <compileSourceRoots default-value="${project.compileSourceRoots}"/> <compilerId default-value="javac">${maven.compiler.compilerId}</compilerId> <compilerVersion>${maven.compiler.compilerVersion}</compilerVersion> <debug default-value="true">${maven.compiler.debug}</debug> <debuglevel>${maven.compiler.debuglevel}</debuglevel> <encoding default-value="${project.build.sourceEncoding}">${encoding}</encoding> <executable>${maven.compiler.executable}</executable> <failOnError default-value="true">${maven.compiler.failOnError}</failOnError> <fork default-value="false">${maven.compiler.fork}</fork> <generatedSourcesDirectory default-value="${project.build.directory}/generated-sources/annotations"/> <maxmem>${maven.compiler.maxmem}</maxmem> <meminitial>${maven.compiler.meminitial}</meminitial> <optimize default-value="false">${maven.compiler.optimize}</optimize> <outputDirectory default-value="${project.build.outputDirectory}"/> <outputFileName>${project.build.finalName}</outputFileName> <projectArtifact default-value="${project.artifact}"/> <session default-value="${session}"/> <showDeprecation default-value="false">${maven.compiler.showDeprecation}</showDeprecation> <showWarnings default-value="false">${maven.compiler.showWarnings}</showWarnings> <source default-value="1.5">1.7</source> <staleMillis default-value="0">${lastModGranularityMs}</staleMillis> <target default-value="1.5">1.7</target> <verbose default-value="false">${maven.compiler.verbose}</verbose> </configuration> [DEBUG] ======================================================================= [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://raw.github.com/eXist-db/mvn-repo/master/ [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://raw.github.com/eXist-db/mvn-repo/master/ Downloading: https://raw.github.com/eXist-db/mvn-repo/master/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.pom [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.pom.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.pom [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.pom.lastUpdated [WARNING] The POM for org.exist-db:existdb-core:jar:3.0.RC1 is missing, no dependency information available [DEBUG] Could not find metadata com.xmlcalabash:xmlcalabash-saxon94:1.0.14-SNAPSHOT/maven-metadata.xml in local (/Users/lcahlander/.m2/repository) [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://raw.github.com/eXist-db/mvn-repo/master/ [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://raw.github.com/eXist-db/mvn-repo/master/ Downloading: https://raw.github.com/eXist-db/mvn-repo/master/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/maven-metadata.xml [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/resolver-status.properties [DEBUG] Could not find metadata com.xmlcalabash:xmlcalabash-saxon94:1.0.14-SNAPSHOT/maven-metadata.xml in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/) [DEBUG] Could not find metadata com.xmlcalabash:xmlcalabash-saxon94:1.0.14-SNAPSHOT/maven-metadata.xml in local (/Users/lcahlander/.m2/repository) [DEBUG] Skipped remote request for com.xmlcalabash:xmlcalabash-saxon94:1.0.14-SNAPSHOT/maven-metadata.xml, already updated during this session. [DEBUG] Failure to find com.xmlcalabash:xmlcalabash-saxon94:1.0.14-SNAPSHOT/maven-metadata.xml in https://raw.github.com/eXist-db/mvn-repo/master/ was cached in the local repository, resolution will not be reattempted until the update interval of eXistDB has elapsed or updates are forced [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://raw.github.com/eXist-db/mvn-repo/master/ [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://raw.github.com/eXist-db/mvn-repo/master/ Downloading: https://raw.github.com/eXist-db/mvn-repo/master/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/xmlcalabash-saxon94-1.0.14-SNAPSHOT.pom [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/xmlcalabash-saxon94-1.0.14-SNAPSHOT.pom.lastUpdated [WARNING] The POM for com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT is missing, no dependency information available [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://raw.github.com/eXist-db/mvn-repo/master/ [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://raw.github.com/eXist-db/mvn-repo/master/ Downloading: https://raw.github.com/eXist-db/mvn-repo/master/junit/junit/4.4/junit-4.4.pom [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/junit/junit/4.4/junit-4.4.pom.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/junit/junit/4.4/junit-4.4.pom Downloaded: https://repo.maven.apache.org/maven2/junit/junit/4.4/junit-4.4.pom (2 KB at 8.8 KB/sec) [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/junit/junit/4.4/_remote.repositories [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/junit/junit/4.4/junit-4.4.pom.lastUpdated [DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=1, ConflictMarker.markTime=0, ConflictMarker.nodeCount=4, ConflictIdSorter.graphTime=1, ConflictIdSorter.topsortTime=0, ConflictIdSorter.conflictIdCount=3, ConflictIdSorter.conflictIdCycleCount=0, ConflictResolver.totalTime=3, ConflictResolver.conflictItemCount=3, DefaultDependencyCollector.collectTime=1826, DefaultDependencyCollector.transformTime=7} [DEBUG] org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT [DEBUG] org.exist-db:existdb-core:jar:3.0.RC1:compile [DEBUG] com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT:compile [DEBUG] junit:junit:jar:4.4:test [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://raw.github.com/eXist-db/mvn-repo/master/ [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://raw.github.com/eXist-db/mvn-repo/master/ Downloading: https://raw.github.com/eXist-db/mvn-repo/master/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.jar Downloading: https://raw.github.com/eXist-db/mvn-repo/master/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/xmlcalabash-saxon94-1.0.14-SNAPSHOT.jar [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.jar.lastUpdated [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/com/xmlcalabash/xmlcalabash-saxon94/1.0.14-SNAPSHOT/xmlcalabash-saxon94-1.0.14-SNAPSHOT.jar.lastUpdated [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 Downloading: https://repo.maven.apache.org/maven2/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.jar [DEBUG] Writing tracking file /Users/lcahlander/.m2/repository/org/exist-db/existdb-core/3.0.RC1/existdb-core-3.0.RC1.jar.lastUpdated [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.035 s [INFO] Finished at: 2015-09-29T06:15:10-04:00 [INFO] Final Memory: 13M/309M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project XMLCalabash: Could not resolve dependencies for project org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT: The following artifacts could not be resolved: org.exist-db:existdb-core:jar:3.0.RC1, com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/) -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project XMLCalabash: Could not resolve dependencies for project org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT: The following artifacts could not be resolved: org.exist-db:existdb-core:jar:3.0.RC1, com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:221) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.exist-db:XMLCalabash:jar:0.1.7-SNAPSHOT: The following artifacts could not be resolved: org.exist-db:existdb-core:jar:3.0.RC1, com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/) at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:211) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195) ... 23 more Caused by: org.eclipse.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: org.exist-db:existdb-core:jar:3.0.RC1, com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384) at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:205) ... 24 more Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: The following artifacts could not be resolved: org.exist-db:existdb-core:jar:3.0.RC1, com.xmlcalabash:xmlcalabash-saxon94:jar:1.0.14-SNAPSHOT: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367) ... 25 more Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.exist-db:existdb-core:jar:3.0.RC1 in eXistDB (https://raw.github.com/eXist-db/mvn-repo/master/) at org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:39) at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355) at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException ldc:eXist-XMLCalabash lcahlander$ |
|
From: Joe W. <jo...@gm...> - 2015-08-29 13:33:39
|
Thanks very much, Adam, for this full and interesting explanation. I can now appreciate everyone's enthusiasm for this pull request!
Joe
Sent from my iPhone
On Aug 29, 2015, at 5:37 AM, Adam Retter <ad...@ex...> wrote:
>> Moving to nio.2 improves eXist's performance and scalability in that it
>> allows eXist (1) to handle many more simultaneous connections (both file
>> system but also network operations) and (2) to treat connections these as
>> non-blocking operations.
>>
>> Is that about right?
>
> Those can be advantages of NIO if you use async operations and
> channels, however we have not made any changes in this area. eXist
> already uses channels for its BTree files, for other files we would
> see little or no gain for switching. For network stuff, we rely on
> Jetty and unfortunately we are still using the Servlet API and our
> approach is blocking, ideally that should be replaced.
>
>
>> Also, the pull request mentioned several improvements that, and I have some
>> questions about each item (inline):
>>
>> 1. File moves are now atomic.
>>
>> Q: as opposed to ___?
>
> Previously file or directory moves would or could be non-atomic. For
> example when moving a file, the file would be copied first and then
> the original deleted as a separate operation. With a directory, this
> is amplified, e.g. a new directory entry is made, each file is copied
> and then the original deleted, and finally the original directory
> entry is removed.
>
> You can probably imagine that if an error occurs or the system is
> stopped or crashes during such an operation, then previously you would
> have an inconsistency and possible corruption as the operation was not
> atomic, e.g. perhaps some of the files were moved or part of the file
> was moved.
>
>
>> 2. File copying and data copying is now handled directly by the JVM/OS.
>>
>> Q: as opposed to being handled by eXist homegrown code?
>
> Exactly. Previously we would set up a buffer in memory, typically 4KB.
> We would then loop though the source file/stream copying 4KB (or less)
> at a time into the in-memory buffer, then copying that out of the
> in-memory buffer to the destination file. This was a non-optimized and
> inefficient operation for many reasons, including: 1) assuming a 4KB
> buffer which may be non-optimal, 2) having to make 2 copies of the
> data from source to dest, 3) not using faster DMA techniques already
> available in NIO.1 since Java 6, e.g. FileChannel.transferTo.
>
> We now simply call Files.copy, which passes control for the copy
> process to the JVM NIO.2, which should choose depending on the OS
> choose the most efficient mechanism (hopefully DMA) supported by the
> OS.
>
>
>> 3. FileLock flush synchronisation is now guaranteed by the OS.
>>
>> Q: whereas before eXist's approach to this didn't provide this guarantee?
>
> Previously we used a java.nio.RandomAccessFile to obtain a FileChannel
> and performed a number of operations and then manually called
> FileChannel#force, which effectively calls `fsync` on the underlying
> OS to ensure the data is flushed to disk. The two issues here were, 1)
> you have to remember to call `force` appropriately, hopefully we were
> indeed doing that. 2) we were performing several operations before
> calling `force`, again a system crash or unexpected error could cause
> the system to end up with an inconsistent file and then the lock file
> data would be corrupt.
>
>
>> 4. Along the way I also found many Input and Output streams that were not
>> closed or could be left open by an exception, these have been fixed.
>>
>> Q: sounds like these could've led to memory leaks or file corruption?
>
> It is unlikely that these would have led to memory leaks. Used enough
> they could lead to a leak of file descriptors, i.e. using up file
> handles from the underlying OS which has a finite limit on these.
> Potentially a FileOutputStream that is not closed could result in a
> corrupt file: if a number of writes were performed, and neither flush
> or close was called, and then the systems stops unexpectedly because
> of a crash or some sort of error, then you could have a file where not
> all of the data was persisted to disk.
>
> I recently spent quite some time identifying many of these unclosed
> streams in eXist when I introduced the use of try-with-resource and
> fixing them. I was actually surprised when I found even more during
> this piece of work, somehow these additional ones had escaped my
> notice in the past.
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
|
|
From: Adam R. <ad...@ex...> - 2015-08-29 09:37:59
|
> Moving to nio.2 improves eXist's performance and scalability in that it
> allows eXist (1) to handle many more simultaneous connections (both file
> system but also network operations) and (2) to treat connections these as
> non-blocking operations.
>
> Is that about right?
Those can be advantages of NIO if you use async operations and
channels, however we have not made any changes in this area. eXist
already uses channels for its BTree files, for other files we would
see little or no gain for switching. For network stuff, we rely on
Jetty and unfortunately we are still using the Servlet API and our
approach is blocking, ideally that should be replaced.
> Also, the pull request mentioned several improvements that, and I have some
> questions about each item (inline):
>
> 1. File moves are now atomic.
>
> Q: as opposed to ___?
Previously file or directory moves would or could be non-atomic. For
example when moving a file, the file would be copied first and then
the original deleted as a separate operation. With a directory, this
is amplified, e.g. a new directory entry is made, each file is copied
and then the original deleted, and finally the original directory
entry is removed.
You can probably imagine that if an error occurs or the system is
stopped or crashes during such an operation, then previously you would
have an inconsistency and possible corruption as the operation was not
atomic, e.g. perhaps some of the files were moved or part of the file
was moved.
> 2. File copying and data copying is now handled directly by the JVM/OS.
>
> Q: as opposed to being handled by eXist homegrown code?
Exactly. Previously we would set up a buffer in memory, typically 4KB.
We would then loop though the source file/stream copying 4KB (or less)
at a time into the in-memory buffer, then copying that out of the
in-memory buffer to the destination file. This was a non-optimized and
inefficient operation for many reasons, including: 1) assuming a 4KB
buffer which may be non-optimal, 2) having to make 2 copies of the
data from source to dest, 3) not using faster DMA techniques already
available in NIO.1 since Java 6, e.g. FileChannel.transferTo.
We now simply call Files.copy, which passes control for the copy
process to the JVM NIO.2, which should choose depending on the OS
choose the most efficient mechanism (hopefully DMA) supported by the
OS.
> 3. FileLock flush synchronisation is now guaranteed by the OS.
>
> Q: whereas before eXist's approach to this didn't provide this guarantee?
Previously we used a java.nio.RandomAccessFile to obtain a FileChannel
and performed a number of operations and then manually called
FileChannel#force, which effectively calls `fsync` on the underlying
OS to ensure the data is flushed to disk. The two issues here were, 1)
you have to remember to call `force` appropriately, hopefully we were
indeed doing that. 2) we were performing several operations before
calling `force`, again a system crash or unexpected error could cause
the system to end up with an inconsistent file and then the lock file
data would be corrupt.
> 4. Along the way I also found many Input and Output streams that were not
> closed or could be left open by an exception, these have been fixed.
>
> Q: sounds like these could've led to memory leaks or file corruption?
It is unlikely that these would have led to memory leaks. Used enough
they could lead to a leak of file descriptors, i.e. using up file
handles from the underlying OS which has a finite limit on these.
Potentially a FileOutputStream that is not closed could result in a
corrupt file: if a number of writes were performed, and neither flush
or close was called, and then the systems stops unexpectedly because
of a crash or some sort of error, then you could have a file where not
all of the data was persisted to disk.
I recently spent quite some time identifying many of these unclosed
streams in eXist when I introduced the use of try-with-resource and
fixing them. I was actually surprised when I found even more during
this piece of work, somehow these additional ones had escaped my
notice in the past.
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Joe W. <jo...@gm...> - 2015-08-28 16:58:27
|
Since I'm not familiar with nio.2, I looked around for a summary of its benefits over io, and the clearest one seemed to be this: http://tutorials.jenkov.com/java-nio/nio-vs-io.html. The issues discussed are mostly over my head, but let me try a summary: Moving to nio.2 improves eXist's performance and scalability in that it allows eXist (1) to handle many more simultaneous connections (both file system but also network operations) and (2) to treat connections these as non-blocking operations. Is that about right? Also, the pull request mentioned several improvements that, and I have some questions about each item (inline): 1. File moves are now atomic. Q: as opposed to ___? 2. File copying and data copying is now handled directly by the JVM/OS. Q: as opposed to being handled by eXist homegrown code? 3. FileLock flush synchronisation is now guaranteed by the OS. Q: whereas before eXist's approach to this didn't provide this guarantee? 4. Along the way I also found many Input and Output streams that were not closed or could be left open by an exception, these have been fixed. Q: sounds like these could've led to memory leaks or file corruption? Apologies for my java-ignorance - I'm just curious to understand the benefits of these changes. They sound great! Joe |
|
From: Dannes W. <da...@ex...> - 2015-08-28 11:06:55
|
thank you adam for your PR and your additional notes ! |
|
From: Adam R. <ad...@ex...> - 2015-08-28 09:19:20
|
Hey devs, We have now switched to using NIO.2 in a large proportion of the core code base. There may be a few places where java.io.File and friends are still in use, if you find these, feel free to clean them up. The commit is here - https://github.com/eXist-db/exist/commit/d06a425f6d3f9ad607bf93e05816e5e0e58b7b5e So I would ask that in future there are a few rules that should be followed to keep us clean with regards to NIO.2. 1. Always use java.nio.file.Path instead of java.io.File. 1.1 If you are working with a 3rd party library that demands a java.io.File, then call .toFile on the Path at the last possible moment, i.e. in the method call to that library. This will allow us to easily identify non NIO.2 code in future. 2. For constructing paths, use `Paths.get` for new paths, `Path.resolve` and `Path.resolveSibling` for child and sibling paths respectively, and Path.relativise for `relative` paths. 3. Use java.nio.file.Files for filesystem ops. Do not use Apache Commons IO. If you want "quiet" versions of the NIO.2 Files methods then see org.exist.util.FileUtils. 3.1 Pay attention to StandardCopyOptions; e.g. if you are doing a Files.move, you most likely want it to be MOVE_ATOMIC. 4. When you want to open a reader/writer or input/outputStream (buffered or un-buffered) on a file, use Files.newInputStream and friends instead of the java.io.FileInputStream and friends constructors. 4.1 ALWAYS do this inside a try-with-resources statement. 4.2 Pay attention to the StandardOpenOptions; e.g. if you want fsync then use SYNC. 4.3 You can often use FIles.newSeekableByteChannel instead of java.io.RandomAccessFile. See the history of org.exist.storage.FileLock for an example of this switch. 5. When you want to list files, consider whether Files.find might be more efficient than Files.list. Note that Files.find on a directory will include the directory itself, if you don't want that then add a .filter. Try and operate on the Stream as a Stream, rather than calling .collect. Remember, that the Stream can only be read once. 6. If you want the just name of the file (most likely only for serialization purposes) then call org.exist.util.FileUtils.fileName(path). 6.1 path.getFileName().endsWith(".ext") most likely does not do what you think it does! You probably wanted path.getFileName().toString().endsWith(".ext"), but instead please use the shortcut FileUtils.fileName(path).endsWith(".ext") Cheers Adam. -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Baumann, A. (LGL) <Axe...@lg...> - 2015-08-27 11:05:01
|
Hi Adam, sorry, but I’m not confident in using GitHub so I will send you my implementation of the history trigger. Greetings, Axel Von: Adam Retter [mailto:ad...@ex...] Gesendet: Donnerstag, 27. August 2015 11:56 An: Baumann, Axel (LGL) Cc: exi...@li... Betreff: Re: [Exist-development] document history trigger doesn't work Hi Axel, I haven't myself used the Document History trigger for sometime however I am surprised to learn that it doesn't work. I last used it in eXist 2.1 when I tested it for the eXist book. We would of course be happy to receive any tests, fixes or improvements. We are using GitHub for development, so please feel free to send us a Pull-request - https://www.github.com/exist-db/exist On 17 August 2015 at 09:05, Baumann, Axel (LGL) <Axe...@lg...<mailto:Axe...@lg...>> wrote: Hi, the implementation of the document history trigger in eXist-db 2.2 (LTS) doesn’t work. The trigger creates a collection instead of a document and saving the changed document leads to an exception. I‘ve implemented a document history trigger which works and fulfills our needs. Are there any plans on your site to clean up the document history trigger to make it work as expected or are you may be interested in my implementation of the document history trigger ? Greetings, Mit freundlichen Grüßen, Axel Baumann Es ist nichts scheißer als Platz Zwei (Erik Meijer) -- Axel Baumann Landesamt für Geoinformation und Landentwicklung Baden-Württemberg (LGL) Abteilung 3 - Geodatenzentrum (GDZ) Ref. 35 Stuttgarter Straße 161 70806 Kornwestheim Tel.: +49 7154 9598 - 748<tel:%2B49%207154%209598%20-%20748> Fax: +49 7154 9598<tel:%2B49%207154%209598> - 92 748 E-Mail: axe...@lg...<mailto:axe...@lg...> http://www.lgl-bw.de ------------------------------------------------------------------------------ _______________________________________________ Exist-development mailing list Exi...@li...<mailto:Exi...@li...> https://lists.sourceforge.net/lists/listinfo/exist-development -- Adam Retter eXist Developer { United Kingdom } ad...@ex...<mailto:ad...@ex...> irc://irc.freenode.net/existdb<http://irc.freenode.net/existdb> |
|
From: Adam R. <ad...@ex...> - 2015-08-27 09:55:55
|
Hi Axel, I haven't myself used the Document History trigger for sometime however I am surprised to learn that it doesn't work. I last used it in eXist 2.1 when I tested it for the eXist book. We would of course be happy to receive any tests, fixes or improvements. We are using GitHub for development, so please feel free to send us a Pull-request - https://www.github.com/exist-db/exist On 17 August 2015 at 09:05, Baumann, Axel (LGL) <Axe...@lg...> wrote: > Hi, > > > > the implementation of the document history trigger in eXist-db 2.2 (LTS) > doesn’t work. The trigger creates a collection instead of a document and > saving the changed document leads to an exception. I‘ve implemented a > document history trigger which works and fulfills our needs. Are there any > plans on your site to clean up the document history trigger to make it work > as expected or are you may be interested in my implementation of the > document history trigger ? > > > > Greetings, > > Mit freundlichen Grüßen, > > Axel Baumann > > > > Es ist nichts scheißer als Platz Zwei (Erik Meijer) > > -- > > Axel Baumann > > > > Landesamt für Geoinformation und Landentwicklung > > Baden-Württemberg (LGL) > > Abteilung 3 - Geodatenzentrum (GDZ) > > Ref. 35 > > Stuttgarter Straße 161 > > 70806 Kornwestheim > > > > Tel.: +49 7154 9598 - 748 > > Fax: +49 7154 9598 - 92 748 > > E-Mail: axe...@lg... > > http://www.lgl-bw.de > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
|
From: Adam R. <ad...@ex...> - 2015-08-27 08:47:33
|
Loren, Are you sure that Windows service manager will automatically restart a failed process? On 25 Aug 2015 23:22, "Loren Cahlander" <lor...@gm...> wrote: > > I have the need to have eXist exit its jvm with a code other than zero. > > I have a case where eXist is running on a windows server and it is > difficult to get admin access. Without admin access, the restart in the > services does not restart if the exit is 0. > > I run system:shutdown() and the eXist instance shuts down, but the windows > service does not restart it. > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > |
|
From: Loren C. <lor...@gm...> - 2015-08-25 22:22:12
|
I have the need to have eXist exit its jvm with a code other than zero. I have a case where eXist is running on a windows server and it is difficult to get admin access. Without admin access, the restart in the services does not restart if the exit is 0. I run system:shutdown() and the eXist instance shuts down, but the windows service does not restart it. |
|
From: Baumann, A. (LGL) <Axe...@lg...> - 2015-08-17 08:17:02
|
Hi, the implementation of the document history trigger in eXist-db 2.2 (LTS) doesn't work. The trigger creates a collection instead of a document and saving the changed document leads to an exception. I've implemented a document history trigger which works and fulfills our needs. Are there any plans on your site to clean up the document history trigger to make it work as expected or are you may be interested in my implementation of the document history trigger ? Greetings, Mit freundlichen Grüßen, Axel Baumann Es ist nichts scheißer als Platz Zwei (Erik Meijer) -- Axel Baumann Landesamt für Geoinformation und Landentwicklung Baden-Württemberg (LGL) Abteilung 3 - Geodatenzentrum (GDZ) Ref. 35 Stuttgarter Straße 161 70806 Kornwestheim Tel.: +49 7154 9598 - 748 Fax: +49 7154 9598 - 92 748 E-Mail: axe...@lg... http://www.lgl-bw.de |
|
From: Adam R. <ad...@ex...> - 2015-07-12 12:41:20
|
Any further thoughts on this please @dmitriy and @wolfgang?
On 25 October 2014 at 10:58, Dannes Wessels <da...@ex...> wrote:
> Hi Adam,
>
> On 24 Oct 2014, at 23:16 , Adam Retter <ad...@ex...> wrote:
>
> Am I being stupid?
>
>
> Nobody from the community ever claimed this, i hope :-P
>
> ...and if not, any objections to me removing the extraneous code?
>
>
> As you present it, it makes sense, but maybe @dmitriy or @wolf have a
> scenario where it might be relevant….
>
> regards
>
> Dannes
>
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Leif-Jöran O. <lj...@ex...> - 2015-07-08 09:12:51
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Den 2015-07-08 kl. 10:17, skrev Dmitriy Shabanov: > On Wed, Jul 8, 2015 at 10:58 AM, Leif-Jöran Olsson <lj...@ex... > <mailto:lj...@ex...>> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Den 2015-07-07 kl. 15:48, skrev Dmitriy Shabanov: > > Do you mean this > > one https://github.com/eXist-db/exist/tree/develop/extensions/sv n ? > > Yes, that is the one I referred to and started to maintain as stat ed. > > > I do not want to delete it, but move it to it own repo. > > OK. So I can continue maintain it if all license stuff are in orde r. > > > Good to know that you are using it. licenses should be ok. Thanks. > And if you > are interesting in that I may spend some time and update to latest svn , > but only if you are sure that you going to use ;-) I think the 1.8.8 version I updated to in February should be ok still, so no urgent need to update the library yet. Cheers, Leif-Jöran -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iD8DBQFVnOM7hcIn5aVXOPIRAuKCAJ96AKjP0GEB7DM2Rc4yu8FQGHU/+wCgrw/6 jW/mZ1pxSA/aY0DVQfUjS9U= =9NG9 -----END PGP SIGNATURE----- |
|
From: Dmitriy S. <sha...@gm...> - 2015-07-08 08:17:12
|
On Wed, Jul 8, 2015 at 10:58 AM, Leif-Jöran Olsson <lj...@ex...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Den 2015-07-07 kl. 15:48, skrev Dmitriy Shabanov: > > Do you mean this > > one https://github.com/eXist-db/exist/tree/develop/extensions/svn ? > > Yes, that is the one I referred to and started to maintain as stated. > > > I do not want to delete it, but move it to it own repo. > > OK. So I can continue maintain it if all license stuff are in order. > Good to know that you are using it. licenses should be ok. And if you are interesting in that I may spend some time and update to latest svn, but only if you are sure that you going to use ;-) |
|
From: Leif-Jöran O. <lj...@ex...> - 2015-07-08 07:58:39
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Den 2015-07-07 kl. 15:48, skrev Dmitriy Shabanov: > Do you mean this > one https://github.com/eXist-db/exist/tree/develop/extensions/svn ? Yes, that is the one I referred to and started to maintain as stated. > I do not want to delete it, but move it to it own repo. OK. So I can continue maintain it if all license stuff are in order. Leif-Jöran > On Tue, Jul 7, 2015 at 4:39 PM, Leif-Jöran Olsson <lj...@ex... > <mailto:lj...@ex...>> wrote: > > Hi, I already deleteted this thread once since I also was on trave l and > the freeze period was over, so over to the new subject. I use the svn > extension in a lot of projects and already updated it in February to > make it work with current java versions (7 and 8 released January and > onwards). I could make an xar of it but do not want it removed unt il > then atleast. > > > > -- > Dmitriy Shabanov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iD8DBQFVnNgjhcIn5aVXOPIRAhOAAJ0RU1MnY4qkHYpO31Lpy5U73QhvTgCeJRTK SihZH/MnibFrmHbVQcvDzZA= =4DNd -----END PGP SIGNATURE----- |
|
From: Dmitriy S. <sha...@gm...> - 2015-07-07 13:48:23
|
Do you mean this one https://github.com/eXist-db/exist/tree/develop/extensions/svn ? I do not want to delete it, but move it to it own repo. On Tue, Jul 7, 2015 at 4:39 PM, Leif-Jöran Olsson <lj...@ex...> wrote: > Hi, I already deleteted this thread once since I also was on travel and > the freeze period was over, so over to the new subject. I use the svn > extension in a lot of projects and already updated it in February to > make it work with current java versions (7 and 8 released January and > onwards). I could make an xar of it but do not want it removed until > then atleast. > -- Dmitriy Shabanov |
|
From: Leif-Jöran O. <lj...@ex...> - 2015-07-07 13:39:43
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I already deleteted this thread once since I also was on travel and the freeze period was over, so over to the new subject. I use the svn extension in a lot of projects and already updated it in February to make it work with current java versions (7 and 8 released January and onwards). I could make an xar of it but do not want it removed until then atleast. Leif-Jöran Den 2015-06-29 kl. 12:46, skrev Dmitriy Shabanov: > Hi Adam, > > I did create it, and maintain ... but it was not used much, so I'm not > going to continue it support. > > On Mon, Jun 29, 2015 at 1:05 PM, Adam Retter <ad...@ex... > <mailto:ad...@ex...>> wrote: > > Hi Dmitriy, > > I have no idea of the provenance of the svn extension? or if anyon e is > using it? or who created it? So I cannot really say what its fate > should be... > > On 29 June 2015 at 10:55, Dmitriy Shabanov <sha...@gm... > <mailto:sha...@gm...>> wrote: > > I mean https://github.com/eXist-db/exist/tree/develop/extensions /svn > > > > Well, history cleanup may not required, but move it to it own gi t > repo? > > > > On Mon, Jun 29, 2015 at 12:15 PM, Adam Retter <ad...@ex... > <mailto:ad...@ex...>> wrote: > >> > >> Hi Dmitriy what is "svn extension", regards the history from > >> Subversion we want to keep this. I went to great lengths to ens ure > >> that this was preserved when we migrated because it was felt by > >> several of the devs that keeping this was essential. > >> > >> On 28 June 2015 at 22:43, Dmitriy Shabanov <sha...@gm... > <mailto:sha...@gm...>> wrote: > >> > Hi, > >> > > >> > If that going on, maybe it's time to delete svn extension fro m > eXist > >> > code > >> > too (including history)? May goal to reduce size of eXist git repo. > >> > > >> > On Sun, Jun 28, 2015 at 10:05 PM, Adam Retter > <ad...@ex... <mailto:ad...@ex...>> wrote: > >> >> > >> >> I have repaired much of the commit history and for now my re paired > >> >> copy is available here - > >> >> https://github.com/adamretter/exist/commits/develop > >> >> > >> >> I am afraid that to proceed and finish the job though I have a > couple > >> >> of different approaches that I could take. This needs to be > discussed > >> >> with the rest of the core development team to get an agreeme nt. > >> >> However, the crux of the matter is that removing a file from our > >> >> repository history will cause problems with existing open > >> >> pull-requests and any other branch or cloned repo. > >> >> > >> >> There are a few ways we could proceed. When the other core > developers > >> >> appear again (tomorrow now I guess), then we will resolve th is > ASAP. > >> >> > >> >> For the moment, please consider the repo still frozen. Sorry > for the > >> >> delay, and thank you for your patience. > >> >> > >> >> I will issue another update tomorrow AM (UTC). > >> >> > >> >> Adam. > >> >> > >> >> On 27 June 2015 at 22:49, Adam Retter <ad...@ex... > <mailto:ad...@ex...>> wrote: > >> >> > Hi eXist developers, > >> >> > > >> >> > For the moment, we think we may have a problem with our > GitHub Git > >> >> > repository. Can I please ask people to avoid sending or > merging any > >> >> > pull-requests for the next 12 hours or so. > >> >> > > >> >> > Unfortunately I am traveling at the moment, but I will be > able to > >> >> > look > >> >> > at repairing the repository from about 12pm UTC tomorrow > (Sunday 27th > >> >> > June). It should only take me about 1 - 2 hours. I will se nd a > >> >> > further > >> >> > update after that time. > >> >> > > >> >> > Also for your own sanity, I would suggest not doing a pull > or fetch > >> >> > from the eXist GitHub repository at the moment. > >> >> > > >> >> > Thanks for your patience. Adam. > >> >> > > >> >> > -- > >> >> > Adam Retter > >> >> > > >> >> > eXist Developer > >> >> > { United Kingdom } > >> >> > ad...@ex... <mailto:ad...@ex...> > >> >> > irc://irc.freenode.net/existdb <http://irc.freenode.net/ex istdb> > >> >> > >> >> > >> >> > >> >> -- > >> >> Adam Retter > >> >> > >> >> eXist Developer > >> >> { United Kingdom } > >> >> ad...@ex... <mailto:ad...@ex...> > >> >> irc://irc.freenode.net/existdb <http://irc.freenode.net/exis tdb> > >> >> > >> >> > >> >> > >> >> > ------------------------------------------------------------------ - ------------ > >> >> Monitor 25 network devices or servers for free with OpManage r! > >> >> OpManager is web-based network management software that moni tors > >> >> network devices and physical & virtual servers, alerts via > email & sms > >> >> for fault. Monitor 25 devices for free with no restriction. > Download > >> >> now > >> >> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > >> >> _______________________________________________ > >> >> Exist-development mailing list > >> >> Exi...@li... > <mailto:Exi...@li...> > >> >> https://lists.sourceforge.net/lists/listinfo/exist-developme nt > >> > > >> > > >> > > >> > > >> > -- > >> > Dmitriy Shabanov > >> > >> > >> > >> -- > >> Adam Retter > >> > >> eXist Developer > >> { United Kingdom } > >> ad...@ex... <mailto:ad...@ex...> > >> irc://irc.freenode.net/existdb <http://irc.freenode.net/existdb > > > > > > > > > > > -- > > Dmitriy Shabanov > > > > -- > Adam Retter > > eXist Developer > { United Kingdom } > ad...@ex... <mailto:ad...@ex...> > irc://irc.freenode.net/existdb <http://irc.freenode.net/existdb> > > > > > -- > Dmitriy Shabanov > > > ---------------------------------------------------------------------- - -------- > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors > network devices and physical & virtual servers, alerts via email & sms > for fault. Monitor 25 devices for free with no restriction. Download n ow > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > > > > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iD8DBQFVm9aThcIn5aVXOPIRAjrYAJ9OfazazKKlq0AlTVeiPAC6kSws4ACgprfU IBea6HsCUu11cFrdpn624dw= =AlvL -----END PGP SIGNATURE----- |
|
From: Hungerburg <pc...@my...> - 2015-07-04 10:22:21
|
Am 2015-07-04 um 10:59 schrieb Dmitriy Shabanov:
> On Sat, Jul 4, 2015 at 11:28 AM, Hungerburg <pc...@my...
>
> > XmldbURI uri = XmldbURI.create("/db/xmldb:something #1.dita");
>
> Regarding RFC 3986, that looks to me like a *decoded* path component
> with two segments ("db", "xmldb:something ") and a fragment ("1.dita")
> too; if it should be a path only, the crosshatch would have to be remain
> quoted even after decoding.
>
> In case of RFC 3986 here is "/db/xmldb" scheme, "something " hier-part
> and "1.dita" fragment. https://www.ietf.org/rfc/rfc3986.txt section 3.
That is exactly why I think that its a pain to pass URIs around as
strings. When intelligent people cannot come to a conclusion, how should
a computer do?
BTW: A scheme must not have a slash, at least not on the WWW:
https://tools.ietf.org/html/rfc3986#section-3.1
> And that mean that most of dbs have illegal resource name.
>
> Encoding may help, but should XmldbURI follow RFC 3986?
You can treat it the same as any other URI then?
--
Peter
|
|
From: Dmitriy S. <sha...@gm...> - 2015-07-04 08:59:15
|
On Sat, Jul 4, 2015 at 11:28 AM, Hungerburg <pc...@my...> wrote:
> Am 2015-07-03 um 19:28 schrieb Dmitriy Shabanov:
> > We should agree on something here and now,
> > because, for example, oXygen can create document at eXist by webdav
> > interface (other protocols allow that too) and that document will not
> > allow to list collection or remove it.
> >
> > Here the trace of exception on document request:
> >
> > java.lang.IllegalArgumentException: Invalid URI: xmldb URI scheme has no
> > instance name: xmldb:exercise%20
> > at org.exist.xmldb.XmldbURI.create(XmldbURI.java:188)
> > at org.exist.xmldb.XmldbURI.lastSegment(XmldbURI.java:500)
> > at
> org.exist.storage.NativeBroker.getXMLResource(NativeBroker.java:2223)
>
> Out of my special interest in URL handling, I tried to manually trace
> how to get from XmldbURI.create to the exception, from String to URI to
> String and back again:
>
> XmldbURI.create(String)
> XmldbURI.xmldbUriFor(String)
> XmldbURI.xmldbUriFor(String, Bool)
> java.net.URI new(escaped String)
> XmldbURI.getXmldbURI(URI)
> FullXmldbURI new(URI)
> XmldbURI.xmldbURI(URI, Bool)
> xmldbURI.URI.toString().trim()
> xmldbURI.normalize()
> java.net.URI new(truncated String)
> FullXmldbURI.parseURI(URI, Bool)
>
> Probably, thats not really what happens, the class is hell: "… to keep
> memory usage low" it says ;)
>
> > XmldbURI uri = XmldbURI.create("/db/xmldb:something #1.dita");
>
> Regarding RFC 3986, that looks to me like a *decoded* path component
> with two segments ("db", "xmldb:something ") and a fragment ("1.dita")
> too; if it should be a path only, the crosshatch would have to be remain
> quoted even after decoding.
>
In case of RFC 3986 here is "/db/xmldb" scheme, "something " hier-part
and "1.dita"
fragment. https://www.ietf.org/rfc/rfc3986.txt section 3.
And that mean that most of dbs have illegal resource name.
Encoding may help, but should XmldbURI follow RFC 3986?
--
Dmitriy Shabanov
|
|
From: Hungerburg <pc...@my...> - 2015-07-04 08:28:53
|
Am 2015-07-03 um 19:28 schrieb Dmitriy Shabanov:
> We should agree on something here and now,
> because, for example, oXygen can create document at eXist by webdav
> interface (other protocols allow that too) and that document will not
> allow to list collection or remove it.
>
> Here the trace of exception on document request:
>
> java.lang.IllegalArgumentException: Invalid URI: xmldb URI scheme has no
> instance name: xmldb:exercise%20
> at org.exist.xmldb.XmldbURI.create(XmldbURI.java:188)
> at org.exist.xmldb.XmldbURI.lastSegment(XmldbURI.java:500)
> at org.exist.storage.NativeBroker.getXMLResource(NativeBroker.java:2223)
Out of my special interest in URL handling, I tried to manually trace
how to get from XmldbURI.create to the exception, from String to URI to
String and back again:
XmldbURI.create(String)
XmldbURI.xmldbUriFor(String)
XmldbURI.xmldbUriFor(String, Bool)
java.net.URI new(escaped String)
XmldbURI.getXmldbURI(URI)
FullXmldbURI new(URI)
XmldbURI.xmldbURI(URI, Bool)
xmldbURI.URI.toString().trim()
xmldbURI.normalize()
java.net.URI new(truncated String)
FullXmldbURI.parseURI(URI, Bool)
Probably, thats not really what happens, the class is hell: "… to keep
memory usage low" it says ;)
> XmldbURI uri = XmldbURI.create("/db/xmldb:something #1.dita");
Regarding RFC 3986, that looks to me like a *decoded* path component
with two segments ("db", "xmldb:something ") and a fragment ("1.dita")
too; if it should be a path only, the crosshatch would have to be remain
quoted even after decoding.
--
Peter
|
|
From: Dmitriy S. <sha...@gm...> - 2015-07-03 17:28:18
|
That's why I wrote this mail. We should agree on something here and now,
because, for example, oXygen can create document at eXist by webdav
interface (other protocols allow that too) and that document will not allow
to list collection or remove it.
Here the trace of exception on document request:
java.lang.IllegalArgumentException: Invalid URI: xmldb URI scheme has no
instance name: xmldb:exercise%20
at org.exist.xmldb.XmldbURI.create(XmldbURI.java:188)
at org.exist.xmldb.XmldbURI.lastSegment(XmldbURI.java:500)
at org.exist.storage.NativeBroker.getXMLResource(NativeBroker.java:2223)
Other requesta raise same exception. (@ XmldbURI.lastSegment method)
On Fri, Jul 3, 2015 at 7:04 PM, Adam Retter <ad...@ex...> wrote:
> Yes I realise it is the existing method. But, if there is no javadoc
> describing what it does, then your guess is as good as mine!
>
> On 3 July 2015 at 16:14, Dmitriy Shabanov <sha...@gm...> wrote:
> > That is existing method at current code of XmldbURI.
> >
> > Main question that I have: should exception be raised and if yes - where?
> >
> > On Fri, Jul 3, 2015 at 5:59 PM, Adam Retter <ad...@ex...> wrote:
> >>
> >> I have no idea?
> >>
> >> Certainly if you did new java.net.URI("/db/xmldb:something #1.dita")
> >> you will get a URISyntaxException due to the space.
> >>
> >> It depends what the contract of the `create` function is, is it meant
> >> to URI encode?
> >>
> >> On 3 July 2015 at 15:50, Dmitriy Shabanov <sha...@gm...> wrote:
> >> > Hi,
> >> >
> >> > Is this test correct?
> >> >
> >> > XmldbURI uri = XmldbURI.create("/db/xmldb:something #1.dita");
> >> >
> >> > assertEquals("xmldb:/db/xmldb:something%20#1.dita", uri.toString());
> >> > assertEquals("xmldb:something%20#1.dita",
> uri.lastSegment().toString());
> >
> >
> >
> > --
> > Dmitriy Shabanov
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>
--
Dmitriy Shabanov
|
|
From: Adam R. <ad...@ex...> - 2015-07-03 16:04:49
|
Yes I realise it is the existing method. But, if there is no javadoc
describing what it does, then your guess is as good as mine!
On 3 July 2015 at 16:14, Dmitriy Shabanov <sha...@gm...> wrote:
> That is existing method at current code of XmldbURI.
>
> Main question that I have: should exception be raised and if yes - where?
>
> On Fri, Jul 3, 2015 at 5:59 PM, Adam Retter <ad...@ex...> wrote:
>>
>> I have no idea?
>>
>> Certainly if you did new java.net.URI("/db/xmldb:something #1.dita")
>> you will get a URISyntaxException due to the space.
>>
>> It depends what the contract of the `create` function is, is it meant
>> to URI encode?
>>
>> On 3 July 2015 at 15:50, Dmitriy Shabanov <sha...@gm...> wrote:
>> > Hi,
>> >
>> > Is this test correct?
>> >
>> > XmldbURI uri = XmldbURI.create("/db/xmldb:something #1.dita");
>> >
>> > assertEquals("xmldb:/db/xmldb:something%20#1.dita", uri.toString());
>> > assertEquals("xmldb:something%20#1.dita", uri.lastSegment().toString());
>
>
>
> --
> Dmitriy Shabanov
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
|
From: Dmitriy S. <sha...@gm...> - 2015-07-03 15:14:51
|
That is existing method at current code of XmldbURI.
Main question that I have: should exception be raised and if yes - where?
On Fri, Jul 3, 2015 at 5:59 PM, Adam Retter <ad...@ex...> wrote:
> I have no idea?
>
> Certainly if you did new java.net.URI("/db/xmldb:something #1.dita")
> you will get a URISyntaxException due to the space.
>
> It depends what the contract of the `create` function is, is it meant
> to URI encode?
>
> On 3 July 2015 at 15:50, Dmitriy Shabanov <sha...@gm...> wrote:
> > Hi,
> >
> > Is this test correct?
> >
> > XmldbURI uri = XmldbURI.create("/db/xmldb:something #1.dita");
> >
> > assertEquals("xmldb:/db/xmldb:something%20#1.dita", uri.toString());
> > assertEquals("xmldb:something%20#1.dita", uri.lastSegment().toString());
>
--
Dmitriy Shabanov
|
|
From: Adam R. <ad...@ex...> - 2015-07-03 14:59:50
|
I have no idea?
Certainly if you did new java.net.URI("/db/xmldb:something #1.dita")
you will get a URISyntaxException due to the space.
It depends what the contract of the `create` function is, is it meant
to URI encode?
On 3 July 2015 at 15:50, Dmitriy Shabanov <sha...@gm...> wrote:
> Hi,
>
> Is this test correct?
>
> XmldbURI uri = XmldbURI.create("/db/xmldb:something #1.dita");
>
> assertEquals("xmldb:/db/xmldb:something%20#1.dita", uri.toString());
> assertEquals("xmldb:something%20#1.dita", uri.lastSegment().toString());
>
> --
> Dmitriy Shabanov
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
--
Adam Retter
eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb
|
64 messages has been excluded from this view by a project administrator.
