build problem
Hi All, I have problems building the Geotools 2.5.8 source. It requires Maven 2.1.0, I have 2.2.1. It is just out of the box without Oracle jars, which I have to add to it. I installed them in the local repository with commands like mvn install:install-file -Dfile=/home/balazs/georaster/product/11.2.0/dbhome_1/jdbc/lib/ojdbc6.jar -DgroupId=com.oracle -DartifactId=ojdbc6 -Dversion=11.2.0 -Dpackaging=jar and put fragments like dependency groupIdcom.oracle/groupId artifactIdojdbc6/artifactId version11.2.0/version typejar/type optionalfalse/optional /dependency into the pom.xml in geotools source root. However, Maven keeps complaining about missing classes. What can be wrong? Can I have Maven output somehow the javac and similar steps of the build to be able to repeat it by hand? thank you in advance, best regards: Balázs Bámer Telefon, mobil TV, SMS, internet egy havi díjért. MédiaMánia díjcsomagok most dupla benne foglalt forgalommal. T-Mobile - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: build problem
Hi, Maven should output the javac compilation error to you. If you didn't see it, it means Maven hasn't reached the point to compile it yet. Maybe you could send us the complete output you get from Maven to see why it doesn't work. It seems to me that you've installed the jar file correctly (maybe check if the file really is there, in ~/.m2/repository/com/oracle/ojdbc6/11.2.0/ ). Csaba On 03/02/2010 12:23 PM, Bámer Balázs wrote: Hi All, I have problems building the Geotools 2.5.8 source. It requires Maven 2.1.0, I have 2.2.1. It is just out of the box without Oracle jars, which I have to add to it. I installed them in the local repository with commands like mvn install:install-file -Dfile=/home/balazs/georaster/product/11.2.0/dbhome_1/jdbc/lib/ojdbc6.jar -DgroupId=com.oracle -DartifactId=ojdbc6 -Dversion=11.2.0 -Dpackaging=jar and put fragments like dependency groupIdcom.oracle/groupId artifactIdojdbc6/artifactId version11.2.0/version typejar/type optionalfalse/optional /dependency into the pom.xml in geotools source root. However, Maven keeps complaining about missing classes. What can be wrong? Can I have Maven output somehow the javac and similar steps of the build to be able to repeat it by hand? thank you in advance, best regards: Balázs Bámer Telefon, mobil TV, SMS, internet egy havi díjért. MédiaMánia díjcsomagok most dupla benne foglalt forgalommal. T-Mobile - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: build problem
/imagemosaic/jdbc/GeoRasterThread.java:[135,8] cannot find symbol symbol : class STRUCT location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[137,2] cannot find symbol symbol : class STRUCT location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[159,13] cannot find symbol symbol : class STRUCT location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[183,2] cannot find symbol symbol : class JGeoRaster location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[186,2] cannot find symbol symbol : class STRUCT location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[205,33] cannot find symbol symbol : class STRUCT location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[206,20] cannot find symbol symbol : class JGeoRaster location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[207,18] cannot find symbol symbol : class JGeoRaster location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[208,17] cannot find symbol symbol : variable JGeoRaster location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[213,33] cannot find symbol symbol : class STRUCT location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[214,20] cannot find symbol symbol : class JGeoRaster location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[219,18] cannot find symbol symbol : class JGeoRaster location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[235,3] cannot find symbol symbol : class JGeoRasterMeta location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread /usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[286,9] cannot find symbol symbol : class GeoRasterException location: class org.geotools.gce.imagemosaic.jdbc.GeoRasterThread [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 47 seconds [INFO] Finished at: Tue Mar 02 12:19:30 CET 2010 [INFO] Final Memory: 32M/254M [INFO] best regards: Balázs Bámer -- View this message in context: http://old.nabble.com/build-problem-tp27754729p27755262.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: build problem
On Ter, 02 Mar 2010, kolaloka wrote:
and this is the output:
bal...@black:/usr/local/src/geotools-2.5.8$ mvn compile
[snip]
[INFO] Building imagemosaic-jdbc module
[INFO]task-segment: [compile]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] snapshot org.h2database:h2:1.0-SNAPSHOT: checking for updates from
maven2-repository.dev.java.net
[INFO] snapshot org.h2database:h2:1.0-SNAPSHOT: checking for updates from
osgeo
[INFO] snapshot org.h2database:h2:1.0-SNAPSHOT: checking for updates from
opengeo
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 31 source files to
/usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[25,31]
package oracle.spatial.georaster does not exist
[and so on]
Seems like you are missing one or more dependencies in the pom for
this project, or their scopes are incorrect.
--
Walking on water wasn't built in a day.
-- Jack Kerouac
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: build problem
Well it can't find oracle.spatial.georaster and some other packages. But
looks like you can't build this project at all with your version of
Maven:
http://www.mail-archive.com/geotools-gt2-us...@lists.sourceforge.net/msg07357.html
Maybe try downgrading to version 2.0.9 or try with a newer version of
the Geotools source code.
Csaba
On 03/02/2010 01:27 PM, kolaloka wrote:
Hi Csaba,
This is what I find in the repository:
bal...@black:~/.m2/repository/com/oracle$ find
.
./sdoapi
./sdoapi/11.2.0
./sdoapi/11.2.0/sdoapi-11.2.0.jar
./sdoapi/maven-metadata-local.xml
./xdb
./xdb/11.2.0
./xdb/11.2.0/xdb-11.2.0.jar
./xdb/maven-metadata-local.xml
./sdotype
./sdotype/11.2.0
./sdotype/11.2.0/sdotype-11.2.0.jar
./sdotype/maven-metadata-local.xml
./xmlparserv2
./xmlparserv2/11.2.0
./xmlparserv2/11.2.0/xmlparserv2-11.2.0.jar
./xmlparserv2/maven-metadata-local.xml
./sdoutl
./sdoutl/11.2.0
./sdoutl/11.2.0/sdoutl-11.2.0.jar
./sdoutl/maven-metadata-local.xml
./sdooutl
./sdooutl/11.2.0
./georasterapi
./georasterapi/11.2.0
./georasterapi/11.2.0/georasterapi-11.2.0.jar
./georasterapi/maven-metadata-local.xml
./dummy_spatial
./dummy_spatial/8.1.8
./dummy_spatial/8.1.8/dummy_spatial-8.1.8.jar.sha1
./dummy_spatial/8.1.8/dummy_spatial-8.1.8.pom.sha1
./dummy_spatial/8.1.8/dummy_spatial-8.1.8.pom
./dummy_spatial/8.1.8/dummy_spatial-8.1.8.jar
./ojdbc6
./ojdbc6/11.2.0
./ojdbc6/11.2.0/ojdbc6-11.2.0.jar
./ojdbc6/maven-metadata-local.xml
and this is the output:
bal...@black:/usr/local/src/geotools-2.5.8$ mvn compile
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Geotools
[INFO] Build tools for Geotools 2
[INFO] Maven plugins for Geotools 2
...
[INFO]
[INFO] Building Geotools
[INFO]task-segment: [compile]
[INFO]
[INFO] No goals needed for project - skipping
[INFO]
[INFO] Building Build tools for Geotools 2
[INFO]task-segment: [compile]
[INFO]
[INFO] No goals needed for project - skipping
[INFO]
[INFO] Building Maven plugins for Geotools 2
[INFO]task-segment: [compile]
[INFO]
[INFO] No goals needed for project - skipping
[INFO]
[INFO] Building Geotools Archetype
[INFO]task-segment: [compile]
[INFO]
[INFO] [plugin:descriptor {execution: default-descriptor}]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO] Extractor for language: java found 0 mojo descriptors.
[INFO] Applying extractor for language: bsh
[INFO] Extractor for language: bsh found 0 mojo descriptors.
[WARNING]
[WARNING] ***
[WARNING] Deprecation Alert:
[WARNING] No mojo descriptors were found in this project which has a
packaging type of maven-plugin.
[WARNING] In future versions of the plugin tools, this will fail the build.
[WARNING] If this project is an archetype, change the packaging type from
maven-plugin to maven-archetype.
[WARNING]
many similar blocks follow
[INFO]
[INFO] Building imagemosaic-jdbc module
[INFO]task-segment: [compile]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] snapshot org.h2database:h2:1.0-SNAPSHOT: checking for updates from
maven2-repository.dev.java.net
[INFO] snapshot org.h2database:h2:1.0-SNAPSHOT: checking for updates from
osgeo
[INFO] snapshot org.h2database:h2:1.0-SNAPSHOT: checking for updates from
opengeo
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 31 source files to
/usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[25,31]
package oracle.spatial.georaster does not exist
/usr/local/src/geotools-2.5.8/modules/plugin/imagemosaic-jdbc/src/main/java/org/geotools/gce/imagemosaic/jdbc/GeoRasterThread.java:[26,31]
package oracle.spatial.georaster does not exist
Re: build problem
Hi Eduardo, Seems like you are missing one or more dependencies in the pom for this project, or their scopes are incorrect. What does this mean? Looking into the repository for an actual class bal...@black:~/.m2/repository/com/oracle$ (for i in `find . -type f|grep jar$`; do unzip -l $i; done) |grep STRUCT 5985 06-16-04 11:33 oracle/sql/STRUCT.class 2830 07-31-09 19:31 oracle/sql/JAVA_STRUCT.class 11087 07-31-09 19:31 oracle/sql/STRUCT.class seems to be there. Well, two of the STRUCT might be a problem if it once finds it... others are not duplicated: bal...@black:~/.m2/repository/com/oracle$ (for i in `find . -type f|grep jar$`; do unzip -l $i; done) |grep JGeoRaster 10378 08-01-09 10:53 oracle/spatial/georaster/JGeoRaster.class 27539 08-01-09 10:53 oracle/spatial/georaster/JGeoRasterMeta.class best regards: Balázs Bámer -- View this message in context: http://old.nabble.com/build-problem-tp27754729p27755478.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: build problem
On Ter, 02 Mar 2010, kolaloka wrote: Looking into the repository for an actual class bal...@black:~/.m2/repository/com/oracle$ (for i in `find . -type f|grep jar$`; do unzip -l $i; done) |grep STRUCT 5985 06-16-04 11:33 oracle/sql/STRUCT.class 2830 07-31-09 19:31 oracle/sql/JAVA_STRUCT.class 11087 07-31-09 19:31 oracle/sql/STRUCT.class seems to be there. Well, two of the STRUCT might be a problem if it once finds it... others are not duplicated: bal...@black:~/.m2/repository/com/oracle$ (for i in `find . -type f|grep jar$`; do unzip -l $i; done) |grep JGeoRaster 10378 08-01-09 10:53 oracle/spatial/georaster/JGeoRaster.class 27539 08-01-09 10:53 oracle/spatial/georaster/JGeoRasterMeta.class It's not enough to have the jar's in your repository, you must list them in the pom.xml file so they are used during compilation. -- We cannot do everything at once, but we can do something at once. -- Calvin Coolidge Eduardo M KALINOWSKI edua...@kalinowski.com.br - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: build problem
Hi Csaba, Maybe try downgrading to version 2.0.9 or try with a newer version of the Geotools source code. I've removed all the 2.2.1 Maven stuff including repository. Installed the Ubuntu package maven2 2.0.9 and installed all the Oracle libraries again. mvn compile ends up in the same errors. (there are more test errors above, but I don't think they are interesting). Best regards: Balázs Bámer -- View this message in context: http://old.nabble.com/build-problem-tp27754729p27756093.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: build problem
Hi Eduardo, It's not enough to have the jar's in your repository, you must list them in the pom.xml file so they are used during compilation. Here is my modification in the main pom.xml: bal...@black:/usr/local/src/geotools-2.5.8$ less pom.xml ... !-- mvn install:install-file -Dfile=/home/balazs/georaster/product/11.2.0/dbhome_1/jdbc/lib/ojdbc6.jar -DgroupId=com.oracle -DartifactId=ojdbc6 -Dversion=11.2.0 -Dpackaging=jar -- dependency groupIdcom.oracle/groupId artifactIdojdbc6/artifactId version11.2.0/version typejar/type optionalfalse/optional /dependency !-- mvn install:install-file -Dfile=/home/balazs/georaster/product/11.2.0/dbhome_1/lib/xmlparserv2.jar -DgroupId=com.oracle -DartifactId=xmlparserv2 -Dversion=11.2.0 -Dpackaging=jar -- dependency groupIdcom.oracle/groupId artifactIdxmlparserv2/artifactId version11.2.0/version typejar/type optionalfalse/optional /dependency !-- mvn install:install-file -Dfile=/home/balazs/georaster/product/11.2.0/dbhome_1/md/jlib/georasterapi.jar -DgroupId=com.oracle -DartifactId=georasterapi -Dversion=11.2.0 -Dpackaging=jar -- dependency groupIdcom.oracle/groupId artifactIdgeorasterapi/artifactId version11.2.0/version typejar/type optionalfalse/optional /dependency !-- mvn install:install-file -Dfile=/home/balazs/georaster/product/11.2.0/dbhome_1/md/jlib/sdoapi.jar -DgroupId=com.oracle -DartifactId=sdoapi -Dversion=11.2.0 -Dpackaging=jar -- dependency groupIdcom.oracle/groupId artifactIdsdoapi/artifactId version11.2.0/version typejar/type optionalfalse/optional /dependency !-- mvn install:install-file -Dfile=/home/balazs/georaster/product/11.2 .0/dbhome_1/md/jlib/sdoutl.jar -DgroupId=com.oracle -DartifactId=sdoutl -Dversio n=11.2.0 -Dpackaging=jar -- dependency groupIdcom.oracle/groupId artifactIdsdoutl/artifactId version11.2.0/version typejar/type optionalfalse/optional /dependency !-- mvn install:install-file -Dfile=/home/balazs/georaster/product/11.2.0/dbhome_1/rdbms/jlib/xdb.jar -DgroupId=com.oracle -DartifactId=xdb -Dversion=11.2.0 -Dpackaging=jar -- dependency groupIdcom.oracle/groupId artifactIdxdb/artifactId version11.2.0/version typejar/type optionalfalse/optional /dependency ... best regards: Balázs Bámer -- View this message in context: http://old.nabble.com/build-problem-tp27754729p27756402.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: build problem
Here is my modification in the main pom.xml: bal...@black:/usr/local/src/geotools-2.5.8$ less pom.xml Does this mean its working now, or still having problems? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: build problem
Hi all, I've found out that there are some fake jars or similars in this source to allow it build without Oracle jars. There is a switch to allow build with the real Oracle jar. I need other ones as well, and couldn't get around this mechanism, so decided to build the Geotools plugin I need by hand (javac). Best regards: Balázs Bámer -- View this message in context: http://old.nabble.com/build-problem-tp27754729p27759330.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Build problem using profiles
Hi, I have two profiles defined in pom.xml. Any ways I can build two wars of both profiles in on line of command? i.e. mvn install -P development,production and place them at different location? Thanks in advance, Vincent -- View this message in context: http://www.nabble.com/Build-problem-using-profiles-tp21483041p21483041.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Archiva Build Problem
) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocumentScannerImpl.java:1157) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1794) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) at javax.xml.parsers.SAXParser.parse(SAXParser.java:176) at net.sf.ehcache.config.ConfigurationFactory.parseConfiguration(ConfigurationFactory.java:145) ... 62 more Sep 19, 2008 10:45:01 AM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart Sep 19, 2008 10:45:01 AM org.apache.catalina.core.StandardContext start SEVERE: Context [] startup failed due to previous errors Sep 19, 2008 10:45:04 AM org.apache.coyote.http11.Http11Protocol start -- View this message in context: http://n2.nabble.com/Archiva-Build-Problem-tp1101374p1101374.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Archiva Build Problem
On Fri, Sep 19, 2008 at 9:34 AM, waaraa1331 [EMAIL PROTECTED] wrote: Here is my error message. Solaris 10 SPARC apache-tomcat-6.0.18 archiva 1.1.2 Archiva has separate mailing lists... you can find subscription info on this page: http://archiva.apache.org/mail-lists.html (I haven't tried it in Tomcat, but there is some info here: http://archiva.apache.org/docs/1.1.2/adminguide/webapp.html ) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Archiva Build Problem
You should really be able to parse that stack trace and find the error... Hint: look for the word initial cause. Wayne On Fri, Sep 19, 2008 at 9:40 AM, Wendy Smoak [EMAIL PROTECTED] wrote: On Fri, Sep 19, 2008 at 9:34 AM, waaraa1331 [EMAIL PROTECTED] wrote: Here is my error message. Solaris 10 SPARC apache-tomcat-6.0.18 archiva 1.1.2 Archiva has separate mailing lists... you can find subscription info on this page: http://archiva.apache.org/mail-lists.html (I haven't tried it in Tomcat, but there is some info here: http://archiva.apache.org/docs/1.1.2/adminguide/webapp.html ) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
m2eclipse's build problem - pmd:cpd doesn't have a default lifecycle phase
Hi, I am trying to do the mvn install from Eclipse. I use the Maven Eclipse Plugin. When I try to to run mvn with any goal i get this error: [INFO] task-segment: [process-resources] [INFO] [ERROR] Maven cannot calculate your build plan, given the following information: Tasks: - process-resources Current project: Group-Id: com.steria.sib-vis Artifact-Id: sib-vis-common Version: 2.x-SNAPSHOT From file: D:\workspace\SIB-VIS\apps\sib-vis\sib-vis-common\pom.xml Error message: Mojo descriptor: pmd:cpd doesn't have a default lifecycle phase. Please specify a phase/ for this goal in your POM. Root error message: Mojo descriptor: pmd:cpd doesn't have a default lifecycle phase. Please specify a phase/ for this goal in your POM. I don't get this error when launching Maven commands from the command prompt. -- View this message in context: http://www.nabble.com/m2eclipse%27s-build-problem---pmd%3Acpd-doesn%27t-have-a-default-lifecycle-phase-tp19329122p19329122.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: m2eclipse's build problem - pmd:cpd doesn't have a default lifecycle phase
By default m2eclipse is using Maven 2.1-SNAPSHOT, and it seem like you are hitting into backward incompatibilities with version you are using in the command line. To workaround that you can configure default Maven runtime to use the same version as you are using in the command line. See Window / Preferences / Maven / Installations. regards, Eugene komadich wrote: I am trying to do the mvn install from Eclipse. I use the Maven Eclipse Plugin. When I try to to run mvn with any goal i get this error: [INFO] task-segment: [process-resources] [INFO] [ERROR] Maven cannot calculate your build plan, given the following information: Tasks: - process-resources Current project: Group-Id: com.steria.sib-vis Artifact-Id: sib-vis-common Version: 2.x-SNAPSHOT From file: D:\workspace\SIB-VIS\apps\sib-vis\sib-vis-common\pom.xml Error message: Mojo descriptor: pmd:cpd doesn't have a default lifecycle phase. Please specify a phase/ for this goal in your POM. Root error message: Mojo descriptor: pmd:cpd doesn't have a default lifecycle phase. Please specify a phase/ for this goal in your POM. I don't get this error when launching Maven commands from the command prompt. -- View this message in context: http://www.nabble.com/m2eclipse%27s-build-problem---pmd%3Acpd-doesn%27t-have-a-default-lifecycle-phase-tp19329122p19335863.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eclipse build problem
Hi, I'm trying to build Eclipse build with maven. In my case there is a library bundle which is just a package of some jars used by other plugins. The problem is that other plugins being build by maven depend on some of those jars and unfortunately I get compilation errors for all of that cases. This leads me to conclusion that such a case is not supported by maven. Is it so? As a workaround I'm creating separate bundle for each jar in use which is not nice. Regards, Stoil
qpid-java-client build problem related to maven.
hi,everyone: I encountered a problem when i built qpid-java-client, the following is the detailed outpu,from that, I don't why it download packages from: http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-site-plugin/2.0-beta-5/maven-site-plugin-2.0-beta-5.pom actually,it doesn't exist at all. Could anybody give any ideas Thanks mvn -Dmaven.repo.local=/builddir/build/BUILD/qpid-java-client/.m2/repository-X -e - Dmaven.test.skip=true -Dspecs.dir=/usr/share/amqp -Pfastinstall /usr/lib/jvm/java Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/builddir/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/usr/share/maven2/conf/plugin-registry.xml' [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Qpid [INFO] Jython Launcher [INFO] Qpid Common Utilities [INFO] Qpid Client [INFO] Qpid Example [INFO] [INFO] Building Qpid [INFO]task-segment: [install] [INFO] [DEBUG] Trying repository apache.snapshots Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-site-plugin/2.0-beta-5/maven-site-plugin-2.0-beta-5.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Error transferring file org.apache.maven.plugins:maven-site-plugin:pom:2.0-beta-5 from the specified remote repositories: apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), Codehaus Snapshots (http://snapshots.repository.codehaus.org/), __jpp_repo__ (file:///usr/share/maven2/repository), central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), junit-toolkit.snapshots ( http://junit-toolkit.svn.sourceforge.net/svnroot/junit-toolkit/snapshots/) Caused by I/O exception: No route to host [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build project for plugin 'org.apache.maven.plugins:maven-site-plugin': Error getting POM for 'org.apache.maven.plugins:maven-site-plugin' from the repository: Error transferring file org.apache.maven.plugins:maven-site-plugin:pom:2.0-beta-5 from the specified remote repositories: apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), Codehaus Snapshots (http://snapshots.repository.codehaus.org/), __jpp_repo__ (file:///usr/share/maven2/repository), central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), junit-toolkit.snapshots ( http://junit-toolkit.svn.sourceforge.net/svnroot/junit-toolkit/snapshots/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin( DefaultLifecycleExecutor.java:1269) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor( DefaultLifecycleExecutor.java:1517) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging (DefaultLifecycleExecutor.java:1011) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings (DefaultLifecycleExecutor.java:975) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at java.lang.reflect.Method.invoke(libgcj.so.7rh) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build project for plugin 'org.apache.maven.plugins:maven-site-plugin': Error getting POM for 'org.apache.maven.plugins:maven-site-plugin' from the repository: Error transferring file org.apache.maven.plugins:maven-site-plugin:pom:2.0-beta-5 from the specified remote repositories: apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), Codehaus Snapshots (http://snapshots.repository.codehaus.org/), __jpp_repo__
Re: Maven Build Problem - XFire
:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[9,32] package org.codehaus.xfire.aegis does not exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[10,38] package org.codehaus.xfire.annotations does not
exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[11,45] package org.codehaus.xfire.annotations.jsr181
does
not
exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[12,33] package org.codehaus.xfire.client does not exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[13,32] package org.codehaus.xfire.jaxb2 does not exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[14,34] package org.codehaus.xfire.service does not
exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[15,34] package org.codehaus.xfire.service does not
exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[16,31] package org.codehaus.xfire.soap does not exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[17,36] package org.codehaus.xfire.transport does not
exist
then following messages:
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\model\AddressMode
l.java:[41,1] cannot find symbol
symbol: class XmlAccessorType
@XmlAccessorType(XmlAccessType.FIELD)
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\model\AddressMode
l.java:[42,1] cannot find symbol
symbol: class XmlType
@XmlType(name = AddressModel, propOrder = {
So some/all xfire dependencies missed?
best regards.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Maven-Build-Problem---XFire-tf4062190s177.html#a11554464
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Build Problem - XFire
Hi Markus, I use the following dependencies for my xfire client !-- xfire dependencies -- dependency groupIdorg.codehaus.xfire/groupId artifactIdxfire-aegis/artifactId version1.2.6/version /dependency dependency groupIdorg.codehaus.xfire/groupId artifactIdxfire-core/artifactId version1.2.6/version exclusions exclusion groupIdjavax.mail/groupId artifactIdmail/artifactId /exclusion exclusion groupIdorg.apache.ws.commons/groupId artifactIdXmlSchema/artifactId /exclusion /exclusions /dependency Cheers, Siegfried Goeschl MPF wrote: Hi! Now i added following dependencies: but some packages missed: javax.xml.bin.annotation does not exist org.codehaus.xfire.jaxb2 does not exist my webservice use XFire 1.2.6 If you wrong understood: the webservice work (i can combile it and make a war file), the problem ist the webapplication wich use this webservice :( best regards. Siegfried Goeschl wrote: Hi Markus, I'm not using the xfire-plugin but +) which XFire version are you using - starting with 1.2.3 it ships with a full pom declaring all dependencies +) when using older version you might check out http://xfire.codehaus.org/Dependency+Guide Cheers, Siegfried Goeschl MPF wrote: Hi! I have a webapplication (myFaces) which also use a webservice of mine - so i installed the Xfire plugin and created the code which the wsdl of the webservice. on localhost all work, but now i wanted to create a war file and got a build error. did i need xfire dependencies at my pom file? whom? following build errors i got: C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic eImplImpl.java:[4,17] package javax.jws does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic e.java:[4,17] package javax.jws does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic e.java:[5,17] package javax.jws does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic e.java:[6,17] package javax.jws does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic e.java:[7,17] package javax.jws does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic e.java:[8,22] package javax.jws.soap does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\AnyType2AnyTy peMap.java:[6,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\AnyType2AnyTy peMap.java:[7,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\AnyType2AnyTy peMap.java:[8,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\AnyType2AnyTy peMap.java:[9,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ressComplex.java:[4,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ressComplex.java:[5,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ressComplex.java:[6,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ressComplex.java:[7,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ressComplex.java:[8,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\FormatService ResponseModelResponse.java:[4,33] package javax.xml.bind.annotation does not exi st C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\FormatService ResponseModelResponse.java:[5,33] package javax.xml.bind.annotation does not exi st C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\FormatService ResponseModelResponse.java:[6,33] package javax.xml.bind.annotation does not exi st C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\FormatService ResponseModelResponse.java:[7,33] package javax.xml.bind.annotation does not exi st C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\FormatService ResponseModelResponse.java:[8,33] package javax.xml.bind.annotation does not exi st C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ress.java:[4,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ress.java:[5,33] package javax.xml.bind.annotation does not exist
Maven Build Problem - XFire
not exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[14,34] package org.codehaus.xfire.service does not exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[15,34] package org.codehaus.xfire.service does not exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[16,31] package org.codehaus.xfire.soap does not exist
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic
eImplClient.java:[17,36] package org.codehaus.xfire.transport does not exist
then following messages:
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\model\AddressMode
l.java:[41,1] cannot find symbol
symbol: class XmlAccessorType
@XmlAccessorType(XmlAccessType.FIELD)
C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\model\AddressMode
l.java:[42,1] cannot find symbol
symbol: class XmlType
@XmlType(name = AddressModel, propOrder = {
So some/all xfire dependencies missed?
best regards.
--
View this message in context:
http://www.nabble.com/Maven-Build-Problem---XFire-tf4062190s177.html#a11541186
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Build Problem - XFire
Hi Markus, I'm not using the xfire-plugin but +) which XFire version are you using - starting with 1.2.3 it ships with a full pom declaring all dependencies +) when using older version you might check out http://xfire.codehaus.org/Dependency+Guide Cheers, Siegfried Goeschl MPF wrote: Hi! I have a webapplication (myFaces) which also use a webservice of mine - so i installed the Xfire plugin and created the code which the wsdl of the webservice. on localhost all work, but now i wanted to create a war file and got a build error. did i need xfire dependencies at my pom file? whom? following build errors i got: C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic eImplImpl.java:[4,17] package javax.jws does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic e.java:[4,17] package javax.jws does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic e.java:[5,17] package javax.jws does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic e.java:[6,17] package javax.jws does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic e.java:[7,17] package javax.jws does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic e.java:[8,22] package javax.jws.soap does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\AnyType2AnyTy peMap.java:[6,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\AnyType2AnyTy peMap.java:[7,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\AnyType2AnyTy peMap.java:[8,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\AnyType2AnyTy peMap.java:[9,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ressComplex.java:[4,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ressComplex.java:[5,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ressComplex.java:[6,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ressComplex.java:[7,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ressComplex.java:[8,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\FormatService ResponseModelResponse.java:[4,33] package javax.xml.bind.annotation does not exi st C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\FormatService ResponseModelResponse.java:[5,33] package javax.xml.bind.annotation does not exi st C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\FormatService ResponseModelResponse.java:[6,33] package javax.xml.bind.annotation does not exi st C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\FormatService ResponseModelResponse.java:[7,33] package javax.xml.bind.annotation does not exi st C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\FormatService ResponseModelResponse.java:[8,33] package javax.xml.bind.annotation does not exi st C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ress.java:[4,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ress.java:[5,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ress.java:[6,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ress.java:[7,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GetGeocodeAdd ress.java:[8,33] package javax.xml.bind.annotation does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic eImplClient.java:[8,26] package org.codehaus.xfire does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic eImplClient.java:[9,32] package org.codehaus.xfire.aegis does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic eImplClient.java:[10,38] package org.codehaus.xfire.annotations does not exist C:\work\projects\BUERGE~2\src\main\java\at\pcd\wam\technologie\geo\GeocodeServic eImplClient.java:[11,45] package org.codehaus.xfire.annotations.jsr181 does not exist
Maven 1.0.2 build problem
We have a build that has been working for a couple years now, but when I tried this on Vista I ended up getting an error. Just wondering if anybody has seen this or had any ideas on what may be wrong. Error: It happens when trying to build a sub-project. We are using a jbrew pluggin, when it tries to build the jbrew target. I get a CreateProcess error=2 The system cannot find file specified. Which is maven.bat Now the maven home directory is in the path, but for some reason when it switches to the jbrew directory to run that build file it is not able to find it. -- View this message in context: http://www.nabble.com/Maven-1.0.2-build-problem-tf3778230s177.html#a10683841 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Open Im build problem
Dear, I m compiling Open IM with Maven 2.0.6 with the command mvn install but i m not able to compile OpenIm. Please help me in this regard. And following is the surefire Report. --- Test set: net.java.dev.openim.TestSimpleClient --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.13 sec FAILURE! testClient(net.java.dev.openim.TestSimpleClient) Time elapsed: 0.03 sec ERROR! java.lang.NoClassDefFoundError: org/codehaus/plexus/classworlds/realm/NoSuchRealmException at org.codehaus.plexus.PlexusTestCase.setUp(PlexusTestCase.java:102) at net.java.dev.openim.TestSimpleClient.setUp(TestSimpleClient.java:24) at junit.framework.TestCase.runBare(TestCase.java:125) Waiting for quick response. Regards, Numan Ilyas - Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
Re: Open Im build problem
2007/5/10, Numan Ilyas [EMAIL PROTECTED]: Dear, I m compiling Open IM with Maven 2.0.6 with the command mvn install but i m not able to compile OpenIm. Please help me in this regard. I think you should ask the Open IM team for that. Antonio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Open Im build problem
You can file an issue there: http://jira.codehaus.org/browse/OPENIM Emmanuel Numan Ilyas a écrit : Dear, I m compiling Open IM with Maven 2.0.6 with the command mvn install but i m not able to compile OpenIm. Please help me in this regard. And following is the surefire Report. --- Test set: net.java.dev.openim.TestSimpleClient --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.13 sec FAILURE! testClient(net.java.dev.openim.TestSimpleClient) Time elapsed: 0.03 sec ERROR! java.lang.NoClassDefFoundError: org/codehaus/plexus/classworlds/realm/NoSuchRealmException at org.codehaus.plexus.PlexusTestCase.setUp(PlexusTestCase.java:102) at net.java.dev.openim.TestSimpleClient.setUp(TestSimpleClient.java:24) at junit.framework.TestCase.runBare(TestCase.java:125) Waiting for quick response. Regards, Numan Ilyas - Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: excluding parent jar and Continuum build problem
Thanks Alexandre, Sorry for confusion. Actually, I have following parent POM dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopecompile/scope /dependency dependency groupIdj2ee/groupId artifactIdj2ee/artifactId version1.5/version scopecompile/scope /dependency dependency groupIdcom.honda/groupId artifactIdGALC_Core/artifactId version1.0/version scopecompile/scope /dependency Now, I would like to exclude GALC_Core dependency inside child POM. I think we can use dependencyManagement tag in parnet POM. Now I have problem that Continuum is not building all projects, when I try to build parent POM. Any suggestion would be appreciated. Thanks, Vijay From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: Fri 4/7/2006 7:40 AM To: Maven Users List Subject: Re: excluding parent jar You can't have a parent project which produce a jar file. A parent project should always have a pom packaging value. On 4/6/06, Vijay Shanker [EMAIL PROTECTED] wrote: Hi there, Could you please let me know how to exclude parent POM's jar in child POM? I have following pom.xml dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopecompile/scope /dependency dependency groupIdj2ee/groupId artifactIdj2ee/artifactId version1.5/version scopecompile/scope /dependency dependency groupIdcom.honda/groupId artifactIdGALC_Core/artifactId version1.0/version scopecompile/scope /dependency I would like to exclude GALC_Core in child POM. Thanking you in advance. Vijay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: excluding parent jar and Continuum build problem
I guess you are declaring your dependency in your parents to tell Maven which version it should use? If it's the case, you should should use the dependencyManagement section instead. On 4/7/06, Vijay Shanker [EMAIL PROTECTED] wrote: Thanks Alexandre, Sorry for confusion. Actually, I have following parent POM dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopecompile/scope /dependency dependency groupIdj2ee/groupId artifactIdj2ee/artifactId version1.5/version scopecompile/scope /dependency dependency groupIdcom.honda/groupId artifactIdGALC_Core/artifactId version1.0/version scopecompile/scope /dependency Now, I would like to exclude GALC_Core dependency inside child POM. I think we can use dependencyManagement tag in parnet POM. Now I have problem that Continuum is not building all projects, when I try to build parent POM. Any suggestion would be appreciated. Thanks, Vijay From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: Fri 4/7/2006 7:40 AM To: Maven Users List Subject: Re: excluding parent jar You can't have a parent project which produce a jar file. A parent project should always have a pom packaging value. On 4/6/06, Vijay Shanker [EMAIL PROTECTED] wrote: Hi there, Could you please let me know how to exclude parent POM's jar in child POM? I have following pom.xml dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopecompile/scope /dependency dependency groupIdj2ee/groupId artifactIdj2ee/artifactId version1.5/version scopecompile/scope /dependency dependency groupIdcom.honda/groupId artifactIdGALC_Core/artifactId version1.0/version scopecompile/scope /dependency I would like to exclude GALC_Core in child POM. Thanking you in advance. Vijay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Build problem
It looks like there is a problem checking out your sources. Please make sure that the SCM information in the project is correct and that you can use the same information to check out the project from the command line. -Original Message- From: Malcolm Wong Ho [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 01, 2005 07:01 To: continuum-users@maven.apache.org Subject: Build problem Continuum build failing, not sure what the cause is. Using Maven2 and Continuum1. Log :- jvm 1| 2005-11-01 09:00:00,013 [scheduler1_Worker-11] INFO SchedulesActivator - Executing build job (DEFAULT_SCHEDULE)... jvm 1| 2005-11-01 09:00:00,053 [scheduler1_Worker-11] INFO Continuum - Enqueuing 'Maven Quick Start Archetype' (Build definition id=10 . jvm 1| 2005-11-01 09:00:00,154 [Thread-1] INFO ContinuumScm - Checking out project: 'Maven Quick Start Archetype', id: '10' to 'C:\blackb ird\continuum-1.0\bin\win32\..\..\apps\continuum\working-directory\10'. jvm 1| 2005-11-01 09:00:00,234 [Thread-1] WARN ConfigurationService - Error reading build output for build '25'. jvm 1| java.io.FileNotFoundException: C:\blackbird\continuum-1.0\bin\win32\..\..\apps\continuum\build-output-d irectory\10\25.log.txt (The system cannot find the file specified) jvm 1| at java.io.FileInputStream.open(Native Method) jvm 1| at java.io.FileInputStream.init(FileInputStream.java:106) jvm 1| at org.codehaus.plexus.util.FileUtils.fileRead(FileUtils.java:269) jvm 1| at org.codehaus.plexus.util.FileUtils.fileRead(FileUtils.java:261) jvm 1| at org.apache.maven.continuum.configuration.DefaultConfigurationService.get BuildOutput(DefaultConfigurationService.java:167) jvm 1| at org.apache.maven.continuum.notification.DefaultContinuumNotificationDisp atcher.sendNotification(DefaultContinuumNotificationDispatcher.java:1 29) jvm 1| at org.apache.maven.continuum.notification.DefaultContinuumNotificationDisp atcher.buildComplete(DefaultContinuumNotificationDispatcher.java:96) jvm 1| at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:261) jvm 1| at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:53) jvm 1| at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) jvm 1| at java.lang.Thread.run(Thread.java:595) Malcolm Wong Ho An investment in knowledge always pays the best interest. -- Benjamin Franklin This e-mail is sent on the Terms and Conditions that can be accessed by Clicking on this link http://www.vodacom.net/legal/email.aspx
Re: Build problem
I already answer to your previous mail but it seems it never arrive on the list. This pb is fixed in svn, it's due to a pb in scm execution. Emmanuel Malcolm Wong Ho a écrit : Continuum build failing, not sure what the cause is. Using Maven2 and Continuum1. Log :- jvm 1| 2005-11-01 09:00:00,013 [scheduler1_Worker-11] INFO SchedulesActivator - Executing build job (DEFAULT_SCHEDULE)... jvm 1| 2005-11-01 09:00:00,053 [scheduler1_Worker-11] INFO Continuum - Enqueuing 'Maven Quick Start Archetype' (Build definition id=10 . jvm 1| 2005-11-01 09:00:00,154 [Thread-1] INFO ContinuumScm - Checking out project: 'Maven Quick Start Archetype', id: '10' to 'C:\blackb ird\continuum-1.0\bin\win32\..\..\apps\continuum\working-directory\10'. jvm 1| 2005-11-01 09:00:00,234 [Thread-1] WARN ConfigurationService - Error reading build output for build '25'. jvm 1| java.io.FileNotFoundException: C:\blackbird\continuum-1.0\bin\win32\..\..\apps\continuum\build-output-d irectory\10\25.log.txt (The system cannot find the file specified) jvm 1| at java.io.FileInputStream.open(Native Method) jvm 1| at java.io.FileInputStream.init(FileInputStream.java:106) jvm 1| at org.codehaus.plexus.util.FileUtils.fileRead(FileUtils.java:269) jvm 1| at org.codehaus.plexus.util.FileUtils.fileRead(FileUtils.java:261) jvm 1| at org.apache.maven.continuum.configuration.DefaultConfigurationService.get BuildOutput(DefaultConfigurationService.java:167) jvm 1| at org.apache.maven.continuum.notification.DefaultContinuumNotificationDisp atcher.sendNotification(DefaultContinuumNotificationDispatcher.java:1 29) jvm 1| at org.apache.maven.continuum.notification.DefaultContinuumNotificationDisp atcher.buildComplete(DefaultContinuumNotificationDispatcher.java:96) jvm 1| at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:261) jvm 1| at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:53) jvm 1| at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) jvm 1| at java.lang.Thread.run(Thread.java:595) Malcolm Wong Ho An investment in knowledge always pays the best interest. -- Benjamin Franklin “This e-mail is sent on the Terms and Conditions that can be accessed by Clicking on this link http://www.vodacom.net/legal/email.aspx
Another build problem
My next build problem, see below. It is looking for commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom And it is not there. [EMAIL PROTECTED] /home/lilyevsk/workspace/lex $ m2 install [INFO] [INFO] Building null [INFO] [INFO] [resources:resources] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2 [INFO] [ERROR] BUILD ERROR [INFO] [ERROR] Cause: org.apache.maven.plugin.PluginExecutionException: Unable to resolve required dependencies for goal at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:375) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeMojo(DefaultL ifecycleExecutor.java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executePhase(Default LifecycleExecutor.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136) at org.apache.maven.cli.MavenCli.main(MavenCli.java:233) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Error transitively resolving artifacts: at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:191) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependenci es(DefaultPluginManager.java:723) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:355) ... 14 more Caused by: org.apache.maven.artifact.resolver.TransitiveArtifactResolutionException : Error retrieving metadata [commons-logging:commons-lo gging:jar:1.0.4] : at org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau ltArtifactResolver.java:307) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:187) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file at org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour ce.java:89) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau ltArtifactResolver.java:303) ... 17 more Caused by: org.apache.maven.project.ProjectBuildingException: Unable to find artifact: commons-logging:commons-logging:pom:1.0.4 at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:167) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:149) at org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour ce.java:83) ... 18 more [INFO] [INFO] Total time: 1 seconds [INFO] Finished at: Mon Apr 11 12:04:37 EDT 2005 [INFO] Final Memory: 1M/63M [INFO] If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: Another build problem
It is probably because this file: http://www.ibiblio.org/maven/commons-logging/poms/commons-logging-1.0.4.pom was published with the wrong version, so the conversion tool was unable to convert. I have corrected it, and hopefully within 4 hours it will have propogated to ibiblio. You should report the problem to commons-dev@jakarta.apache.org - I will do this now. commons-logging-1.0.3 works... - Brett On Apr 12, 2005 2:14 AM, Ilyevsky, Leonid (Equity Trading) [EMAIL PROTECTED] wrote: My next build problem, see below. It is looking for commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom And it is not there. [EMAIL PROTECTED] /home/lilyevsk/workspace/lex $ m2 install [INFO] [INFO] Building null [INFO] [INFO] [resources:resources] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2 [INFO] [ERROR] BUILD ERROR [INFO] [ERROR] Cause: org.apache.maven.plugin.PluginExecutionException: Unable to resolve required dependencies for goal at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:375) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeMojo(DefaultL ifecycleExecutor.java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executePhase(Default LifecycleExecutor.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136) at org.apache.maven.cli.MavenCli.main(MavenCli.java:233) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Error transitively resolving artifacts: at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:191) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependenci es(DefaultPluginManager.java:723) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:355) ... 14 more Caused by: org.apache.maven.artifact.resolver.TransitiveArtifactResolutionException : Error retrieving metadata [commons-logging:commons-lo gging:jar:1.0.4] : at org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau ltArtifactResolver.java:307) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:187) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file at org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour ce.java:89) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau ltArtifactResolver.java:303) ... 17 more Caused by: org.apache.maven.project.ProjectBuildingException: Unable to find artifact: commons-logging:commons-logging:pom:1.0.4 at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:167) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:149) at org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour ce.java:83) ... 18 more [INFO] [INFO] Total time: 1 seconds [INFO] Finished at: Mon Apr 11 12:04:37 EDT 2005 [INFO] Final Memory: 1M/63M [INFO] If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here
Re: Build problem related to test distribution
On Mon, 15 Sep 2003, Gil César Faria wrote: Hello everybody! I have a basic project where I have some general utility classes used by all other maven projects. Inside this general project, i have some abstract test classes that should be used within all other test classes of all projects. All test classes, including those abstract classes are under test directory. When maven builds the distribution for this general project, it only includes the source classes, not the test classes. But when i try to build other projects that depends upon this general project, i cannot compile the tests because the abstract test classes cannot be found. I am not sure about the best solution for this problem and would like an advise from our more maven experienced coleagues: Can i generate more than one artifact (jar) for a single project ? some kind of source distribution and test distribution ... No http://wiki.codehaus.org/maven/WhyYouCantCreateMultipleArtifactsInOneProject Should i generate only a single jar with all source and test classes inside it ? Don't see why not. The test class isnt a class for testing the artifact, rather a part of you general stuff. Bear in mind that the testcase class will be included if you end up building war or uberjars. Should i create a new project to hold only the abstract test classes, and include it as a dependency for all other projects ? This is also a solution. Currently you can only state _dependencies_ for a project so it doesn't add much value, but with a later version you can state runtime/testtime dependencies and then it might be a good idea to have it as a separate project. Guess the rest of your questions are answered by now? :) Should i redefine dist:build to create a test distribution ? There is an automated way to tell maven that the test classes should be considered as a dependency ? There is another way to organize my project classes to solve this problem? Can I define source dependencies and test dependencies separatelly? Any other suggestions? Thanks in advance! Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Build problem related to test distribution
We also desire to make test utility classes (primarily Mock Objects) available for use in testing of dependent projects. The approach of creating XYZ.jar and XYZ-tests.jar artifacts from project XYZ seems to be the best approach to this. Subsequent projects could then prescribe XYX-tests.jar as a test-dependency in their project.xml if needed. I don't think this runs counter to any of the arguments presented on the WhyYouCantCreateMultipleArtifactsInOneProject wiki page. Packaging an additional jar from the test code need not impact any of the plugins (except for a new test:deploy goal), and the build settings need not change. There is no risk of recreating the multi-project plugin within a single project. Alternate suggestion #1 of distributing test code inside a production jar is not a realistic solution in many (most?) environments. Alternate suggestion #2 of creating a new XYZ-test-support project creates a circular dependency - I can't test XYZ without the support classes, and I can't build the support classes without XYZ. I am curious to learn if the concept of a XYX-tests.jar artifact has been discussed before, and if so, why it would be rejected. Thanks, Mark -Original Message- From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] Sent: September 16, 2003 3:35 AM To: Maven Users List Subject: Re: Build problem related to test distribution On Mon, 15 Sep 2003, Gil César Faria wrote: Hello everybody! I have a basic project where I have some general utility classes used by all other maven projects. Inside this general project, i have some abstract test classes that should be used within all other test classes of all projects. All test classes, including those abstract classes are under test directory. When maven builds the distribution for this general project, it only includes the source classes, not the test classes. But when i try to build other projects that depends upon this general project, i cannot compile the tests because the abstract test classes cannot be found. I am not sure about the best solution for this problem and would like an advise from our more maven experienced coleagues: Can i generate more than one artifact (jar) for a single project ? some kind of source distribution and test distribution ... No http://wiki.codehaus.org/maven/WhyYouCantCreateMultipleArtifactsInOneProject Should i generate only a single jar with all source and test classes inside it ? Don't see why not. The test class isnt a class for testing the artifact, rather a part of you general stuff. Bear in mind that the testcase class will be included if you end up building war or uberjars. Should i create a new project to hold only the abstract test classes, and include it as a dependency for all other projects ? This is also a solution. Currently you can only state _dependencies_ for a project so it doesn't add much value, but with a later version you can state runtime/testtime dependencies and then it might be a good idea to have it as a separate project. Guess the rest of your questions are answered by now? :) Should i redefine dist:build to create a test distribution ? There is an automated way to tell maven that the test classes should be considered as a dependency ? There is another way to organize my project classes to solve this problem? Can I define source dependencies and test dependencies separatelly? Any other suggestions? Thanks in advance! Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Build problem related to test distribution
On Tue, 16 Sep 2003, Mark Langley wrote: We also desire to make test utility classes (primarily Mock Objects) available for use in testing of dependent projects. The approach of creating XYZ.jar and XYZ-tests.jar artifacts from project XYZ seems to be the best approach to this. Subsequent projects could then prescribe XYX-tests.jar as a test-dependency in their project.xml if needed. I don't think this runs counter to any of the arguments presented on the WhyYouCantCreateMultipleArtifactsInOneProject wiki page. Packaging an additional jar from the test code need not impact any of the plugins (except for a new test:deploy goal), and the build settings need not change. There is no risk of recreating the multi-project plugin within a single project. Alternate suggestion #1 of distributing test code inside a production jar is not a realistic solution in many (most?) environments. Point taken :) Alternate suggestion #2 of creating a new XYZ-test-support project creates a circular dependency - I can't test XYZ without the support classes, and I can't build the support classes without XYZ. I don't follow you here, perhaps you should try to clearify with a example In your original mail you wanted to create a source distribution and a test distribution. What is a test distribution? The src/main/java directory is for the source files of a artifact and the src/test/java is a set of tests for testing the artifact. They are not supposed to be general classes for use outside of the artifact. If you have a set of general test cases/util objects they really belong in a separate project. I am curious to learn if the concept of a XYX-tests.jar artifact has been discussed before, and if so, why it would be rejected. Thanks, Mark -Original Message- From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] Sent: September 16, 2003 3:35 AM To: Maven Users List Subject: Re: Build problem related to test distribution On Mon, 15 Sep 2003, Gil César Faria wrote: Hello everybody! I have a basic project where I have some general utility classes used by all other maven projects. Inside this general project, i have some abstract test classes that should be used within all other test classes of all projects. All test classes, including those abstract classes are under test directory. When maven builds the distribution for this general project, it only includes the source classes, not the test classes. But when i try to build other projects that depends upon this general project, i cannot compile the tests because the abstract test classes cannot be found. I am not sure about the best solution for this problem and would like an advise from our more maven experienced coleagues: Can i generate more than one artifact (jar) for a single project ? some kind of source distribution and test distribution ... No http://wiki.codehaus.org/maven/WhyYouCantCreateMultipleArtifactsInOneProject Should i generate only a single jar with all source and test classes inside it ? Don't see why not. The test class isnt a class for testing the artifact, rather a part of you general stuff. Bear in mind that the testcase class will be included if you end up building war or uberjars. Should i create a new project to hold only the abstract test classes, and include it as a dependency for all other projects ? This is also a solution. Currently you can only state _dependencies_ for a project so it doesn't add much value, but with a later version you can state runtime/testtime dependencies and then it might be a good idea to have it as a separate project. Guess the rest of your questions are answered by now? :) Should i redefine dist:build to create a test distribution ? There is an automated way to tell maven that the test classes should be considered as a dependency ? There is another way to organize my project classes to solve this problem? Can I define source dependencies and test dependencies separatelly? Any other suggestions? Thanks in advance! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
