Can't build using maven 3
Monday, 8 November 2010 · 6 messages · last reply 10 Nov 2010
SS
Stefano Santoro8 Nov 2010 19:03 #
Hi,
I have checked out basex from subversion, and I could not compile it using maven 3, first it complains that the jar and compiler plugins do not have versions elements in the pom.xml. Second when I attempt a compilation I get the following errors:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project basex: Compilation failure: Compilation failure:
[ERROR]
/home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[17,47] package com.sun.org.apache.xml.internal.resolver does not exist [ERROR]
/home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[18,53] package com.sun.org.apache.xml.internal.resolver.tools does not exist [ERROR]
/home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[93,14] cannot find symbol
[ERROR] symbol : class CatalogManager
[ERROR] location: class org.basex.build.xml.SAXWrapper
[ERROR]
/home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[93,38] cannot find symbol
[ERROR] symbol : class CatalogManager
[ERROR] location: class org.basex.build.xml.SAXWrapper
[ERROR]
/home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[99,32] cannot find symbol
[ERROR] symbol : class CatalogResolver
[ERROR] location: class org.basex.build.xml.SAXWrapper
ssantoro@ssantoroubu:~/opt/basex/basex$ mvn -version
Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400)
Java version: 1.6.0_22
Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix"
ssantoro@ssantoroubu:~/opt/basex/basex$ java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
Ciao
Stefano
Ciao
Stefano
CG
Christian Grün8 Nov 2010 20:25 #
Dear Stefano,
looks as if the recently included CatalogResolver isn't supported by all systems, such as yours – which isn't too surprising, as the discussed code is placed in the com-branch of Java. We'll rewrite the existing implementation to include the resolver code in a dynamic fashion whenever possible, and use the default configuration otherwise. Which Linux distribution are you working with?
Grazie,
Christian
Quoted text · Stefano Santoro · 53 lines
On Mon, Nov 8, 2010 at 6:06 PM, Stefano Santoro <stefano at santoro.org> wrote: > Hi, > I have checked out basex from subversion, and I could not compile it using > maven 3, first it complains that the jar and compiler plugins do not have > versions elements in the pom.xml. Second when I attempt a compilation I get > the following errors: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile > (default-compile) on project basex: Compilation failure: Compilation > failure: > [ERROR] > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[17,47] > package com.sun.org.apache.xml.internal.resolver does not exist > [ERROR] > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[18,53] > package com.sun.org.apache.xml.internal.resolver.tools does not exist > [ERROR] > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[93,14] > cannot find symbol > [ERROR] symbol : class CatalogManager > [ERROR] location: class org.basex.build.xml.SAXWrapper > [ERROR] > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[93,38] > cannot find symbol > [ERROR] symbol : class CatalogManager > [ERROR] location: class org.basex.build.xml.SAXWrapper > [ERROR] > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[99,32] > cannot find symbol > [ERROR] symbol : class CatalogResolver > [ERROR] location: class org.basex.build.xml.SAXWrapper > ssantoro@ssantoroubu:~/opt/basex/basex$ mvn -version > Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400) > Java version: 1.6.0_22 > Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix" > ssantoro@ssantoroubu:~/opt/basex/basex$ java -version > java version "1.6.0_22" > Java(TM) SE Runtime Environment (build 1.6.0_22-b04) > Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode) > Ciao > Stefano > > Ciao > Stefano > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > >
CG
Quoted text · Stefano Santoro · 1 line
> 64 bits Ubuntu 10.10
So this must be related to the Sun JVM; it seems to work fine with Ubuntu 10.10. and OpenJDK. We'll fix it and give you a note.
Quoted text · Christian Grün · 81 lines
> On Mon, Nov 8, 2010 at 2:25 PM, Christian Grün <christian.gruen at gmail.com> > wrote: >> >> Dear Stefano, >> >> looks as if the recently included CatalogResolver isn't supported by >> all systems, such as yours – which isn't too surprising, as the >> discussed code is placed in the com-branch of Java. We'll rewrite the >> existing implementation to include the resolver code in a dynamic >> fashion whenever possible, and use the default configuration >> otherwise. Which Linux distribution are you working with? >> >> Grazie, >> Christian >> >> >> On Mon, Nov 8, 2010 at 6:06 PM, Stefano Santoro <stefano at santoro.org> >> wrote: >> > Hi, >> > I have checked out basex from subversion, and I could not compile it >> > using >> > maven 3, first it complains that the jar and compiler plugins do not >> > have >> > versions elements in the pom.xml. Second when I attempt a compilation I >> > get >> > the following errors: >> > [ERROR] Failed to execute goal >> > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile >> > (default-compile) on project basex: Compilation failure: Compilation >> > failure: >> > [ERROR] >> > >> > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[17,47] >> > package com.sun.org.apache.xml.internal.resolver does not exist >> > [ERROR] >> > >> > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[18,53] >> > package com.sun.org.apache.xml.internal.resolver.tools does not exist >> > [ERROR] >> > >> > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[93,14] >> > cannot find symbol >> > [ERROR] symbol : class CatalogManager >> > [ERROR] location: class org.basex.build.xml.SAXWrapper >> > [ERROR] >> > >> > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[93,38] >> > cannot find symbol >> > [ERROR] symbol : class CatalogManager >> > [ERROR] location: class org.basex.build.xml.SAXWrapper >> > [ERROR] >> > >> > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[99,32] >> > cannot find symbol >> > [ERROR] symbol : class CatalogResolver >> > [ERROR] location: class org.basex.build.xml.SAXWrapper >> > ssantoro@ssantoroubu:~/opt/basex/basex$ mvn -version >> > Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400) >> > Java version: 1.6.0_22 >> > Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre >> > Default locale: en_US, platform encoding: UTF-8 >> > OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: >> > "unix" >> > ssantoro@ssantoroubu:~/opt/basex/basex$ java -version >> > java version "1.6.0_22" >> > Java(TM) SE Runtime Environment (build 1.6.0_22-b04) >> > Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode) >> > Ciao >> > Stefano >> > >> > Ciao >> > Stefano >> > >> > _______________________________________________ >> > BaseX-Talk mailing list >> > BaseX-Talk at mailman.uni-konstanz.de >> > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> > >> > > >
SS
Hi Christian,
64 bits Ubuntu 10.10
Ciao
Stefano
On Mon, Nov 8, 2010 at 2:25 PM, Christian Grün <christian.gruen at gmail.com>wrote:
Quoted text · Christian Grün · 76 lines
> Dear Stefano, > > looks as if the recently included CatalogResolver isn't supported by > all systems, such as yours – which isn't too surprising, as the > discussed code is placed in the com-branch of Java. We'll rewrite the > existing implementation to include the resolver code in a dynamic > fashion whenever possible, and use the default configuration > otherwise. Which Linux distribution are you working with? > > Grazie, > Christian > > > On Mon, Nov 8, 2010 at 6:06 PM, Stefano Santoro <stefano at santoro.org> > wrote: > > Hi, > > I have checked out basex from subversion, and I could not compile it > using > > maven 3, first it complains that the jar and compiler plugins do not have > > versions elements in the pom.xml. Second when I attempt a compilation I > get > > the following errors: > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile > > (default-compile) on project basex: Compilation failure: Compilation > > failure: > > [ERROR] > > > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[17,47] > > package com.sun.org.apache.xml.internal.resolver does not exist > > [ERROR] > > > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[18,53] > > package com.sun.org.apache.xml.internal.resolver.tools does not exist > > [ERROR] > > > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[93,14] > > cannot find symbol > > [ERROR] symbol : class CatalogManager > > [ERROR] location: class org.basex.build.xml.SAXWrapper > > [ERROR] > > > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[93,38] > > cannot find symbol > > [ERROR] symbol : class CatalogManager > > [ERROR] location: class org.basex.build.xml.SAXWrapper > > [ERROR] > > > /home/ssantoro/opt/basex/basex/src/main/java/org/basex/build/xml/SAXWrapper.java:[99,32] > > cannot find symbol > > [ERROR] symbol : class CatalogResolver > > [ERROR] location: class org.basex.build.xml.SAXWrapper > > ssantoro@ssantoroubu:~/opt/basex/basex$ mvn -version > > Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400) > > Java version: 1.6.0_22 > > Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: > "unix" > > ssantoro@ssantoroubu:~/opt/basex/basex$ java -version > > java version "1.6.0_22" > > Java(TM) SE Runtime Environment (build 1.6.0_22-b04) > > Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode) > > Ciao > > Stefano > > > > Ciao > > Stefano > > > > _______________________________________________ > > BaseX-Talk mailing list > > BaseX-Talk at mailman.uni-konstanz.de > > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > > > > >
MS
Hi Stefano,
the issue concerning com.**.resolver should be fixed by now. Simply checkout the latest version in our repository. To get Entity resolving you have to add the apache-commons xml resolver to your classpath manually when launching BaseX. Please let me know if it works for you.
I am working on upgrading our pom to allow building without the version required warnings.
Kind regards
Michael
Quoted text · Christian Grün · 6 lines
Am 08.11.2010 um 20:35 schrieb Christian Grün: >> 64 bits Ubuntu 10.10 > > So this must be related to the Sun JVM; it seems to work fine with > Ubuntu 10.10. and OpenJDK. We'll fix it and give you a note. >
MS
Michael Seiferle10 Nov 2010 20:00 #
Hi Stefano,
(this time with cc to the list, as this might be of general interest :-)) sorry again for the inconvenience. We currently have no automatic deployment of the minor Version jars to our repository (we are about to change that soon, hopefully).
The recoomended and "clean" solution is installing the latest repository version of BaseX into your local subversion repository via:
Quoted text · Michael Seiferle · 3 lines
> $ cd basex > $ svn up > $ mvn -DskipTests=true install
This should avoid the errors below.
Let me know if this helps and feel free to ask more!
Kind regards
Michael
Quoted text · Michael Seiferle · 6 lines
Am 10.11.2010 um 19:41 schrieb Stefano Santoro: > [WARNING] The POM for org.basex:basex:jar:6.3.2 is missing, no dependency information available > Downloading: http://repository.codehaus.org/org/basex/basex/6.3.2/basex-6.3.2.jar > Downloading: http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex/6.3.2/basex-6.3.2.jar > Downloading: http://repo1.maven.org/maven2/org/basex/basex/6.3.2/basex-6.3.2.jar >
Written for BaseX 6. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery