Re: newby: disk space consumption
Hi Wayne, Thanks again for the feedback. I've looked through the poms and don't see any suspicious 'module' entries. I am using Hudson to run the Maven build. Do you know if this might cause the problem? Wessie! Wayne Fay wrote: There is no particular reason why these files should land in this directory using standard Maven configuration, so you must have something custom in your build that is causing it to occur. Try scanning the pom.xml files for modules. Obviously you can ignore the projectmodules node. Alternatively, you can try examining the build output which may provide some clues: mvn clean package | grep modules Wayne On 8/21/08, wessie [EMAIL PROTECTED] wrote: Hi Alex-450, Thanks for the quick response! I've tried changing the maven goals to clean package. The problem is that after each build it still archives the built ear and war files into the 'PROJECTX'/modules/ directory every single time the project is built. Is it possible to get around this archiving? Thanks again Wessie! Alex-450 wrote: Hi Wessie, why not simply upload the ear file to a location outside the cvs which is accessible via web (or via scp)? By the way, I was glad when we switched from CVS to SVN. I'm not an expert, but I have the impression that SVN is much more stable. Nevertheless I wouldn't put constantly changing binary files under a version control system. Cheers Alex wessie wrote: Hi all, I've been given the task of maintaining an exisiting Hudson/Maven setup. I think i've got an 'ok' understanding of whats going on but i'm still learning daily. The problem I have is this. I have a multi-module build that checksout a project from a cvs repository, builds the source, packages it into an ear file and then checks the ear back into the same cvs repository (just a slightly different location). The project is run with clean install goals. All of the above works fine BUT the ear file (and it's inner war file) gets copied into the 'PROJECTX'/modules/ directory every single time the project is built. The result is frequent calls from maintenance teams at really crappy hours. Writing a script the /modules/ directory periodically is a solution but i'd prefer to fix the problem and not one of its symptoms. I'd be happy to provide any poms if anyone is willing to help. Wessie! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/newby%3A-disk-space-consumption-tp19086120p19102282.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/newby%3A-disk-space-consumption-tp19086120p19138912.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: Get Maven internal build statistics
Le dimanche 24 août 2008 à 10:53 +0200, Andreas Gies a écrit : Hi there, if you run your maven build through the Hudson ci server, Hudson will display that information for your in the module build statistc. HTH Andreas Thx Andreas That's sounds great cos' I 'am already using Hudson for my CI! But I did not found the build statistics plugin for hudson : I look in my local admin web page (https://myhudsonserver/hudson/pluginManager/available), and in the Hudson Wiki plugin list pages : http://hudson.gotdns.com/wiki/display/HUDSON/Plugins and in the download section of hudson.dev.java.net https://hudson.dev.java.net/servlets/ProjectDocumentList?folderID=5818expandFolder=5818folderID=2761 But I did not found that plugin. Could you point me an url? -- Julien Graglia - NetCeler - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
repo1 is down
Hi, http://repo1.maven.org/maven2 seems to be down or very very slow. Does someone experience the same issue ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JavaDoc-Report crashes with TestNG
Hello, I have configured the maven-javadoc-plugin in the reporting section. Unfortunately when generating the report, the plugin crashes. The exceptions look like it has problems with the @Test annotation of TestNG. Any ideas or solutions what happens? Greets Wolfgang Roessler -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19139379.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]
AW: repo1 is down
Hi, I am having the same problems: 25.08.08 09:27:39 CEST: Unable to update index for central http://repo1.maven.org/maven2/ Cheers Stefan -Ursprüngliche Nachricht- Von: Bouiaw [mailto:[EMAIL PROTECTED] Gesendet: Montag, 25. August 2008 09:51 An: users@maven.apache.org Betreff: repo1 is down Hi, http://repo1.maven.org/maven2 seems to be down or very very slow. Does someone experience the same issue ? - 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]
How do I override a plugin dependency?
Hi all, I have a need to override a specific dependency used by the maven-torque-plugin, and I am struggling to convince maven v2.0.9 to do this. The symptoms are that the original jar is being used, instead of the overridden jar, which is effectively ignored. To test this, I have deleted the original jar completely from my local maven repository, and what I expect to happen is that maven should not try to download this dependency again, because it has been overridden. In practise, maven downloads the original jar, and ignores the overridden jar. Is there anything obvious that I have missed in this process? My plugin definition looks like this: plugin groupIdorg.apache.torque/groupId artifactIdtorque-maven-plugin/artifactId version3.3/version dependencies dependency groupIdorg.apache.derby/groupId artifactIdderby/artifactId version10.4.1.3/version /dependency dependency groupIdorg.apache.torque/groupId artifactIdtorque-templates/artifactId version3.3.1/version /dependency /dependencies /plugin Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: repo1 is down
Looks to be an issue here too. I've sent in a support request. 2008/8/25 Glase, Stefan [EMAIL PROTECTED]: Hi, I am having the same problems: 25.08.08 09:27:39 CEST: Unable to update index for central http://repo1.maven.org/maven2/ Cheers Stefan -Ursprüngliche Nachricht- Von: Bouiaw [mailto:[EMAIL PROTECTED] Gesendet: Montag, 25. August 2008 09:51 An: users@maven.apache.org Betreff: repo1 is down Hi, http://repo1.maven.org/maven2 seems to be down or very very slow. Does someone experience the same issue ? - 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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JavaDoc-Report crashes with TestNG
Do you need to configure it to use Java's 1.5 source level? - Brett 2008/8/25 WolfgangRoessler [EMAIL PROTECTED]: Hello, I have configured the maven-javadoc-plugin in the reporting section. Unfortunately when generating the report, the plugin crashes. The exceptions look like it has problems with the @Test annotation of TestNG. Any ideas or solutions what happens? Greets Wolfgang Roessler -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19139379.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven2 usage
Hi, I have a Parent Project, and it has a child Project. The Parent is of type 'pom' and it aggregates the child. In order to run mvn install, I need to be either inside the parent or the child projects. Is it possible to selectively execute child goals/phases, from the parent directory ? Regards, Saket CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS***
Re: JavaDoc-Report crashes with TestNG
I set the javadocVersion, but the plugin still crashes. - Wolfgang Brett Porter wrote: Do you need to configure it to use Java's 1.5 source level? - Brett 2008/8/25 WolfgangRoessler [EMAIL PROTECTED]: Hello, I have configured the maven-javadoc-plugin in the reporting section. Unfortunately when generating the report, the plugin crashes. The exceptions look like it has problems with the @Test annotation of TestNG. Any ideas or solutions what happens? Greets Wolfgang Roessler -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19139379.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19140451.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: repo1 is down
The problem should be fixed. Cheers The Maven team On Mon, Aug 25, 2008 at 9:59 AM, Brett Porter [EMAIL PROTECTED]wrote: Looks to be an issue here too. I've sent in a support request. 2008/8/25 Glase, Stefan [EMAIL PROTECTED]: Hi, I am having the same problems: 25.08.08 09:27:39 CEST: Unable to update index for central http://repo1.maven.org/maven2/ Cheers Stefan -Ursprüngliche Nachricht- Von: Bouiaw [mailto:[EMAIL PROTECTED] Gesendet: Montag, 25. August 2008 09:51 An: users@maven.apache.org Betreff: repo1 is down Hi, http://repo1.maven.org/maven2 seems to be down or very very slow. Does someone experience the same issue ? - 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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-wsdl2code-plugin' does not exist or no valid version could be found
Hello Guys, I m using maven 2.0.9. Have completed the proxy settings in setting.xml. This is my pom: project modelVersion4.0.0/modelVersion groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version2/version build plugins plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.4/version executions execution goals goalwsdl2code/goal /goals configuration packageNamecom.mblox.soap.paymentapi/packageName wsdlFilepayment.wsdl/wsdlFile /configuration /execution /executions /plugin /plugins /build /project And getting the above exception. Please help me to remove the exception and generate JAVA code out of a wsdl. Thanks, Asif DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-wsdl2code-plugin' does not exist or no valid version could be found
Probably nothing wrong with the project POM, but what did you specify in your settings.xml? Did you specify a mirror section? I encountered this once too, and I got it resolved by specifying repositories and pluginRepositries in an always active profile. Here is the profile snippet from my settings.xml: !-- Enabled profile containing the Telenet repository. The repository settings are -- !-- required so the lookup of the parent POM succeeds. Otherwise we have a chicken -- !-- and egg problem, since the repositories are define in there globally.-- profile idbootstrap-repositories/id activation activeByDefaulttrue/activeByDefault /activation repositories repository idnexus/id nameInternal Proxy Repository/name releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicywarn/checksumPolicy /snapshots urlhttp://nexusa1:8082/nexus/content/groups/public/url layoutdefault/layout /repository /repositories pluginRepositories pluginRepository idnexus/id nameInternal Proxy Repository/name releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicywarn/checksumPolicy /snapshots urlhttp://nexusa1:8082/nexus/content/groups/public/url layoutdefault/layout /pluginRepository /pluginRepositories /profile Hope this helps. Ringo * Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes éventuelles peuvent contenir des informations confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce message est adressé exclusivement à son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complète sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez reçu ce message par erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
artifact built from maven-nuxeo-plugin being installed before execution of following plugins
Hi,
I need to build resources artifacts (I use maven-assembly-plugin) and
use them (with our maven-nuxeo-plugin) from the same pom.xml
The built resources artifacts do not need to be in the project
dependency but have to be installed before the execution of the second
plugin.
Is it possible to make artifacts built from maven-assembly-plugin being
installed before the execution of the following maven-nuxeo-plugin ?
I have this error when running mvn install:
[INFO]
[INFO] Building Nuxeo EP EAR
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/Users/julien/Documents/workspace/nuxeo/nuxeo-platform/nuxeo-platform-ear/target
...
[INFO] [assembly:attached {execution: make-resources}]
[INFO] Reading assembly descriptor: src/main/assemble/resources/mono.xml
...
[INFO] Building zip:
/Users/julien/Documents/workspace/nuxeo/nuxeo-platform/nuxeo-platform-ear/target/nuxeo-platform-ear-5.1.6-SNAPSHOT-resources-mono.zip
...
[INFO] [nuxeo:assembly {execution: assemble-ear}]
[INFO] Loading assembly descriptor:
/Users/julien/Documents/workspace/nuxeo/nuxeo-platform/nuxeo-platform-ear/src/main/assemble/nuxeo.xml
...
org.apache.maven.plugin.MojoExecutionException: Unable to find artifact.
...
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.nuxeo.ecm.platform
-DartifactId=nuxeo-platform-ear -Dversion=5.1.6-SNAPSHOT
-Dclassifier=resources-mono -Dpackaging=zip -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.nuxeo.ecm.platform
-DartifactId=nuxeo-platform-ear -Dversion=5.1.6-SNAPSHOT
-Dclassifier=resources-mono -Dpackaging=zip -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to run assembly
Here's an extract of my pom.xml:
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptorsrc/main/assemble/resources/mono.xml/descriptor
...
/descriptors
/configuration
executions
execution
idmake-resources/id
phasepackage/phase
goals
goalattached/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-nuxeo-plugin/artifactId
extensionstrue/extensions
executions
execution
idassemble-ear/id
phasepackage/phase
goals
goalassembly/goal
/goals
configuration
...
/configuration
/execution
/executions
/plugin
Thanks,
--
Julien CARSIQUE, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[EMAIL PROTECTED] | Tel: +33 1 40 33 79 87
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: repo1 is down
repo1 respond, but it is very very slow : 30 seconds by request ! On Mon, Aug 25, 2008 at 11:35 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote: The problem should be fixed. Cheers The Maven team On Mon, Aug 25, 2008 at 9:59 AM, Brett Porter [EMAIL PROTECTED]wrote: Looks to be an issue here too. I've sent in a support request. 2008/8/25 Glase, Stefan [EMAIL PROTECTED]: Hi, I am having the same problems: 25.08.08 09:27:39 CEST: Unable to update index for central http://repo1.maven.org/maven2/ Cheers Stefan -Ursprüngliche Nachricht- Von: Bouiaw [mailto:[EMAIL PROTECTED] Gesendet: Montag, 25. August 2008 09:51 An: users@maven.apache.org Betreff: repo1 is down Hi, http://repo1.maven.org/maven2 seems to be down or very very slow. Does someone experience the same issue ? - 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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SCM dependencies?
Hi, I have a general question about maven. I've used maven in the past at a company where I used to work. The way we used it was I think pretty typical, we had a few libraries the project depended on, and we generated a few reports, etc. In my current company, we use a custom (internal) tool, which has, I think, a lot in common with maven, the problem being of course that it is *not* maven :) Ie, there is no documentation, no maintenance, etc. There are also a few problems with it, that's why I was wondering if we could entirely replace this tool with maven, and I have a few questions I hope you guys can help me with. The main difference I see is that our custom tool handles scm dependencies. What I mean by that is that we have our project which is split in several modules and they all have their own life on subversion, and we say for example that the project is on svn://svn/project1/trunk and it depends on svn://svn/module1/trunk and on svn://svn/module2/branches/v2. Then when we bootstrap the project, the tool will checkout these two modules, and generate an eclipse workspace, with one project by module, and the team plugin setup as needed for the project and its dependencies. So a developer can work on the project itself, but if he finds a problem on a dependency he can also work on it! He has the sources and can commit, etc. When I used to work with maven, we only had jar dependencies, ie, the project depended on built versions of some module (external or internal), which is a bit different. So my question is, is this kind of scm dependency possible with maven? Thank you very much. BoD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-wsdl2code-plugin' does not exist or no valid version could be found
you need to add an entry to specify the libraries used for your plugin. For example: pluginRepositories pluginRepository idgwt-maven/id urlhttp://gwt-maven.googlecode.com/svn/trunk/mavenrepo/url /pluginRepository /pluginRepositories You need to change this example probably to point to an repo which contains the libraries you need -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 25 August 2008 11:33 To: mailto:users@maven.apache.org Subject: org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-wsdl2code-plugin' does not exist or no valid version could be found Hello Guys, I m using maven 2.0.9. Have completed the proxy settings in setting.xml. This is my pom: project modelVersion4.0.0/modelVersion groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version2/version build plugins plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.4/version executions execution goals goalwsdl2code/goal /goals configuration packageNamecom.mblox.soap.paymentapi/packageName wsdlFilepayment.wsdl/wsdlFile /configuration /execution /executions /plugin /plugins /build /project And getting the above exception. Please help me to remove the exception and generate JAVA code out of a wsdl. Thanks, Asif DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. - 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]
maven-assembly-plugin / artifact built from maven-assembly-plugin being installed before execution of following plugins in same pom.xml
Changed subject (maven-assembly-plugin)
Julien CARSIQUE a écrit :
Hi,
I need to build resources artifacts (I use maven-assembly-plugin) and
use them (with our maven-nuxeo-plugin) from the same pom.xml
The built resources artifacts do not need to be in the project
dependency but have to be installed before the execution of the second
plugin.
Is it possible to make artifacts built from maven-assembly-plugin
being installed before the execution of the following
maven-nuxeo-plugin ?
I have this error when running mvn install:
[INFO]
[INFO] Building Nuxeo EP EAR
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/Users/julien/Documents/workspace/nuxeo/nuxeo-platform/nuxeo-platform-ear/target
...
[INFO] [assembly:attached {execution: make-resources}]
[INFO] Reading assembly descriptor: src/main/assemble/resources/mono.xml
...
[INFO] Building zip:
/Users/julien/Documents/workspace/nuxeo/nuxeo-platform/nuxeo-platform-ear/target/nuxeo-platform-ear-5.1.6-SNAPSHOT-resources-mono.zip
...
[INFO] [nuxeo:assembly {execution: assemble-ear}]
[INFO] Loading assembly descriptor:
/Users/julien/Documents/workspace/nuxeo/nuxeo-platform/nuxeo-platform-ear/src/main/assemble/nuxeo.xml
...
org.apache.maven.plugin.MojoExecutionException: Unable to find artifact.
...
Caused by:
org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable
to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.nuxeo.ecm.platform
-DartifactId=nuxeo-platform-ear -Dversion=5.1.6-SNAPSHOT
-Dclassifier=resources-mono -Dpackaging=zip -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.nuxeo.ecm.platform
-DartifactId=nuxeo-platform-ear -Dversion=5.1.6-SNAPSHOT
-Dclassifier=resources-mono -Dpackaging=zip -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]
...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to run assembly
Here's an extract of my pom.xml:
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptorsrc/main/assemble/resources/mono.xml/descriptor
...
/descriptors
/configuration
executions
execution
idmake-resources/id
phasepackage/phase
goals
goalattached/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-nuxeo-plugin/artifactId
extensionstrue/extensions
executions
execution
idassemble-ear/id
phasepackage/phase
goals
goalassembly/goal
/goals
configuration
...
/configuration
/execution
/executions
/plugin
Thanks,
-
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]
how to manage two different projects with similar project structures
Hi, I have created two different projects, say A B. Both contain a module, say M. When i run, /mvn install /in both the projects, M gets installed in my local repository at two different locations, but with the same name, say M-1.0.0.jar. Now, if I add the modules M as dependencies to my 3rd application, say D, in the final war of D, only one M is there. Is there a way to change the name of M-1.0.0.jar of A to A-M-1.0.0.jar or some similar name, without explicitly renaming the folder name of module M to A-M and B-M. Regards, Shakun - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dependency issue
Hi, I am using two dependencies, both are dependent upon apache-comons-collections, but of different versions. So, my final jar / war contains two versions of commons-collections, is there a way to stop this. Regards, Shakun - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release fails during SVN commit
Some of my users are having the same problem. I think it has to do with the svn 1.5 client. Liz Sommers [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: repo1 is down
repo1 works again quickly, thanks a lot. On Mon, Aug 25, 2008 at 11:53 AM, Bouiaw [EMAIL PROTECTED] wrote: repo1 respond, but it is very very slow : 30 seconds by request ! On Mon, Aug 25, 2008 at 11:35 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote: The problem should be fixed. Cheers The Maven team On Mon, Aug 25, 2008 at 9:59 AM, Brett Porter [EMAIL PROTECTED]wrote: Looks to be an issue here too. I've sent in a support request. 2008/8/25 Glase, Stefan [EMAIL PROTECTED]: Hi, I am having the same problems: 25.08.08 09:27:39 CEST: Unable to update index for central http://repo1.maven.org/maven2/ Cheers Stefan -Ursprüngliche Nachricht- Von: Bouiaw [mailto:[EMAIL PROTECTED] Gesendet: Montag, 25. August 2008 09:51 An: users@maven.apache.org Betreff: repo1 is down Hi, http://repo1.maven.org/maven2 seems to be down or very very slow. Does someone experience the same issue ? - 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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC10
Using RC10, the following fails, which was working with 2.0.9: (seems like it doesn't like enums?!) mvn clean tomcat:deploy -o [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'tomcat'. [INFO] [INFO] Building webclient [INFO]task-segment: [clean, tomcat:deploy] [INFO] [INFO] [clean:clean] [INFO] Deleting directory target [INFO] Preparing tomcat:deploy [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 57 source files to target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure MyClass.java:[22,1] annotations are not supported in -source 1.3 (try -source 1.5 to enable annotations) @SuppressWarnings(nls) *MyEnum.java:[17,7] 'class' or 'interface' expected* [...other, similar errors...] [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:338) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682) ... 20 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Mon Aug 25 13:32:46 CEST 2008 [INFO] Final Memory: 11M/20M [INFO] -
AW: Release fails during SVN commit
Hi Andreas, I am not sure but maybe this would be worth a try. In my projects I always refer to the trunk folder in the SCM configuration and point to the tags or releases folder in the tagBase property of the maven-release-plugin. So your configuration would look like this in your pom.xml: scm connectionscm:svn:http://xxx/svndir/project/trunk/connection developerConnectionscm:svn:http://xxx /svndir/project/trunk/develope rConnection urlhttp://xxx /svndir/project//url /scm ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId configuration tagBasehttp://XXX.XXX.XXX.XXX/svndir/project/tags/tagBase autoVersionSubmodulestrue/autoVersionSubmodules preparationGoalsclean install/preparationGoals /configuration /plugin My idea behind this is, that it might be a problem to point to a tag-directory within the scm connection. I my understanding those folders should be on the same level. Hope to help Stefan -Ursprüngliche Nachricht- Von: Andreas Heinecke [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 21. August 2008 10:04 An: users@maven.apache.org Betreff: Release fails during SVN commit Hi there, I encountered a strange problem. Since a few weeks I'm not able to perform a release with Maven. The release process fails during executing the release:prepare goal at the same position, always. The point at which the release fails is when Maven tries to commit the release POM's to SVN. This commit fails with the error message that the file which is about to be committed already exists at the position in SVN. But it isn't there. Strange, uh? I actually checked the tagbase configuration of the plugin and tried to alter it, but the effect remains. I don't know what I can try to fix this issue. The last thing altered at the configuration is a switch of the SVN server. We had to switch to a newer SVN version 1.5.0. We also switched to the new 1.5.0 SVN client as we know that there are problems with newer server software and older client software. Please find parts of my pom.xml configuration attached below. Any pointers are welcome. Regards, Andreas. My SCM configuration: scm connectionscm:svn:http://xxx.xxx.xxx.xxx/svndir/project/connection developerConnectionscm:svn:http://xxx.xxx.xxx.xxx/svndir/project/develope rConnection urlhttp://xxx.xxx.xxx.xxx/svndir/project/url /scm My release plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId configuration tagBasehttp://XXX.XXX.XXX.XXX/svndir/project/tags/tagBase autoVersionSubmodulestrue/autoVersionSubmodules preparationGoalsclean install/preparationGoals /configuration /plugin - 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:org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-wsdl2code-plugin' does not exist or no valid version could be found
I was asked to run and paste the mvn -X wsdl2code:wsdl2code output. Here is the same: C:\Paymentmvn -X wsdl2code:wsdl2code + Error stacktraces are turned on. Maven version: 2.0.9 Java version: 1.6.0_07 OS name: windows xp version: 5.1 arch: x86 Family: windows [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\asif_garhi\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\apache-maven-2.0.9\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'wsdl2code'. [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [DEBUG] Loading plugin prefixes from group: org.codehaus.mojo [DEBUG] Retrieving parent-POM: org.apache.axis2:axis2-parent::1.4 for project: null:axis2-wsdl2code-maven-plugin:maven-plugin:null from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: org.apache.axis2:axis2-parent:pom:1.4 from the repository. [DEBUG] Adding managed dependencies for unknown:axis2-wsdl2code-maven-plugin [DEBUG] com.sun.xml.fastinfoset:FastInfoset:jar:1.1.8 [DEBUG] org.apache.tomcat:tribes:jar:6.0.14 [DEBUG] org.apache.tomcat:juli:jar:6.0.14 [DEBUG] xml-apis:xml-apis:jar:1.3.04 [DEBUG] xml-resolver:xml-resolver:jar:1.2 [DEBUG] xalan:xalan:jar:2.7.0 [DEBUG] com.sun.xml.bind:jaxb-impl:jar:2.1.6 [DEBUG] com.sun.xml.bind:jaxb-xjc:jar:2.1.6 [DEBUG] javax.xml.bind:jaxb-api:jar:2.1 [DEBUG] org.springframework:spring-core:jar:2.5.1 [DEBUG] org.springframework:spring-beans:jar:2.5.1 [DEBUG] org.springframework:spring-context:jar:2.5.1 [DEBUG] org.springframework:spring-web:jar:2.5.1 [DEBUG] javax.servlet:servlet-api:jar:2.3 [DEBUG] org.codehaus.jettison:jettison:jar:1.0-RC2 [DEBUG] org.jibx:jibx-bind:jar:1.1.5 [DEBUG] org.jibx:jibx-run:jar:1.1.5 [DEBUG] org.apache.ant:ant-launcher:jar:1.7.0 [DEBUG] org.apache.ws.commons.axiom:axiom-api:jar:1.2.7 [DEBUG] org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7 [DEBUG] org.apache.ws.commons.axiom:axiom-dom:jar:1.2.7 [DEBUG] org.apache.ws.commons.schema:XmlSchema:jar:1.4.2 [DEBUG] org.apache.neethi:neethi:jar:2.0.4 [DEBUG] org.apache.ant:ant:jar:1.7.0 [DEBUG] org.apache.bcel:bcel:jar:5.2 [DEBUG] commons-logging:commons-logging:jar:1.1.1 [DEBUG] commons-codec:commons-codec:jar:1.3 [DEBUG] org.codehaus.woodstox:wstx-asl:jar:3.2.4 [DEBUG] org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1 [DEBUG] org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0.1 [DEBUG] org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.2 [DEBUG] org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1 [DEBUG] org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar:1.1 [DEBUG] jaxen:jaxen:jar:1.1.1 [DEBUG] annogen:annogen:jar:0.1.0 [DEBUG] commons-httpclient:commons-httpclient:jar:3.1 [DEBUG] commons-io:commons-io:jar:1.4 [DEBUG] org.apache.httpcomponents:httpcore:jar:4.0-beta1 [DEBUG] org.apache.httpcomponents:httpcore-nio:jar:4.0-beta1 [DEBUG] org.apache.httpcomponents:httpcore-niossl:jar:4.0-beta1 [DEBUG] commons-fileupload:commons-fileupload:jar:1.2 [DEBUG] wsdl4j:wsdl4j:jar:1.6.2 [DEBUG] backport-util-concurrent:backport-util-concurrent:jar:3.1 [DEBUG] org.apache.woden:woden-api:jar:1.0M8 [DEBUG] org.apache.woden:woden-impl-dom:jar:1.0M8 [DEBUG] xmlunit:xmlunit:jar:1.1:test [DEBUG] junit:junit:jar:4.4:test [DEBUG] org.apache.xmlbeans:xmlbeans:jar:2.3.0 [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.7 [DEBUG] org.apache.maven:maven-project:jar:2.0.7 [DEBUG] org.apache.maven:maven-artifact:jar:2.0.8 [DEBUG] org.apache.maven:maven-archiver:jar:2.2 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.9 [DEBUG] org.apache.maven.shared:maven-plugin-testing-harness:jar:1.1:test [DEBUG] log4j:log4j:jar:1.2.15 [DEBUG] org.eclipse.core:org.eclipse.core.jobs:jar:3.2.0 [DEBUG] org.eclipse.core:org.eclipse.core.resources:jar:3.2.0 [DEBUG] org.eclipse.core:org.eclipse.core.runtime:jar:3.2.0 [DEBUG] org.eclipse.equinox:org.eclipse.equinox.common:jar:3.2.0 [DEBUG] org.eclipse.jface:org.eclipse.jface:jar:3.2.0 [DEBUG] org.eclipse.osgi:org.eclipse.osgi:jar:3.2.0 [DEBUG] org.eclipse.swt:org.eclipse.swt:jar:3.2.0 [DEBUG] org.eclipse.swt:org.eclipse.swt.win32.win32.x86:jar:3.2.0 [DEBUG] org.eclipse.ui:org.eclipse.ui.ide:jar:3.2.0 [DEBUG] com.intellij:openapi:jar:5.0 [DEBUG] com.intellij:extensions:jar:5.0 [DEBUG] rhino:js:jar:1.6R7 [DEBUG] bsf:bsf:jar:2.4.0 [DEBUG] org.apache.activemq:apache-activemq:jar:5.0.0 [DEBUG] jalopy:jalopy:jar:1.5rc3 [DEBUG] xerces:xercesImpl:jar:2.8.1 [DEBUG] org.igniterealtime:smack:jar:3.0.4:provided [DEBUG] commons-lang:commons-lang:jar:2.3:provided [DEBUG] maven-wsdl2code-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine
Re: SCM dependencies?
On Mon, Aug 25, 2008 at 6:13 AM, BoD [EMAIL PROTECTED] wrote: The main difference I see is that our custom tool handles scm dependencies. What I mean by that is that we have our project which is split in several modules and they all have their own life on subversion, and we say for example that the project is on svn://svn/project1/trunk and it depends on svn://svn/module1/trunk and on svn://svn/module2/branches/v2. Then when we bootstrap the project, the tool will checkout these two modules, and generate an eclipse workspace, with one project by module, and the team plugin setup as needed for the project and its dependencies. So a developer can work on the project itself, but if he finds a problem on a dependency he can also work on it! He has the sources and can commit, etc. When I used to work with maven, we only had jar dependencies, ie, the project depended on built versions of some module (external or internal), which is a bit different. So my question is, is this kind of scm dependency possible with maven? It's a bit of both. If you have a set of related projects that tend to have the same lifecycle, it's not uncommon to put them in a multi-module project. If you go that route, then it's very easy to check out the multi-module project, have Maven build an eclipse workspace, and use them such that a change in one module is automatically reflected in the other modules within eclipse (project dependencies instead of JAR dependencies). If, on the other hand, these are projects that aren't very tightly coupled, then you'd usually stick to JAR-style dependencies, although there may still be another way of making what you want happen. It sounds like the former case is closer to what you need, though. - Geoffrey -- Geoffrey Wiseman
Re: SCM dependencies?
Thank you very much for your answer. Ok let's say I'd like to try the first way (multi-module project, project dependencies). Where should I start, to make a pom from an existing project? (Do you know of a simple example, or a tutorial somewhere for that particular case?) Thanks! BoD Geoffrey Wiseman wrote: On Mon, Aug 25, 2008 at 6:13 AM, BoD [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: The main difference I see is that our custom tool handles scm dependencies. What I mean by that is that we have our project which is split in several modules and they all have their own life on subversion, and we say for example that the project is on svn://svn/project1/trunk and it depends on svn://svn/module1/trunk and on svn://svn/module2/branches/v2. Then when we bootstrap the project, the tool will checkout these two modules, and generate an eclipse workspace, with one project by module, and the team plugin setup as needed for the project and its dependencies. So a developer can work on the project itself, but if he finds a problem on a dependency he can also work on it! He has the sources and can commit, etc. When I used to work with maven, we only had jar dependencies, ie, the project depended on built versions of some module (external or internal), which is a bit different. So my question is, is this kind of scm dependency possible with maven? It's a bit of both. If you have a set of related projects that tend to have the same lifecycle, it's not uncommon to put them in a multi-module project. If you go that route, then it's very easy to check out the multi-module project, have Maven build an eclipse workspace, and use them such that a change in one module is automatically reflected in the other modules within eclipse (project dependencies instead of JAR dependencies). If, on the other hand, these are projects that aren't very tightly coupled, then you'd usually stick to JAR-style dependencies, although there may still be another way of making what you want happen. It sounds like the former case is closer to what you need, though. - Geoffrey -- Geoffrey Wiseman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Taglist and Dashboard
Hello, I want to include the report of taglist-maven-plugin into my maven-dashboard report. I found out, that currently the taglist-plugin does not support xml-output and therefore cannot be aggregated by the dashboard-plugin. I know there is a patch for this available. When will this patch be incorporated and a new snapshot-release be available? Greets Wolfgang -- View this message in context: http://www.nabble.com/Taglist-and-Dashboard-tp19143343p19143343.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: [PLEASE TEST] Maven 2.0.10-RC10
Hi Peter, It seems that you don't have the maven-compiler-plugin configured correctly. You must set the source as 1.5 to use Enums. See [1] for more information. [1]http://maven.apache.org/general.html#Compiling-J2SE-5 Cheers, Henrique Peter Horlock wrote: Using RC10, the following fails, which was working with 2.0.9: (seems like it doesn't like enums?!) mvn clean tomcat:deploy -o [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'tomcat'. [INFO] [INFO] Building webclient [INFO]task-segment: [clean, tomcat:deploy] [INFO] [INFO] [clean:clean] [INFO] Deleting directory target [INFO] Preparing tomcat:deploy [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 57 source files to target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure MyClass.java:[22,1] annotations are not supported in -source 1.3 (try -source 1.5 to enable annotations) @SuppressWarnings(nls) *MyEnum.java:[17,7] 'class' or 'interface' expected* [...other, similar errors...] [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:338) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682) ... 20 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Mon Aug 25 13:32:46 CEST 2008 [INFO] Final Memory: 11M/20M [INFO] - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: SCM dependencies?
Hi, the free book Maven - The definitive Guide published by Sonatype has a nice chapter on this topic: http://www.sonatype.com/book/reference/multimodule.html Hope to help, Stefan -Ursprüngliche Nachricht- Von: BoD [mailto:[EMAIL PROTECTED] Gesendet: Montag, 25. August 2008 14:51 An: Maven Users List Betreff: Re: SCM dependencies? Thank you very much for your answer. Ok let's say I'd like to try the first way (multi-module project, project dependencies). Where should I start, to make a pom from an existing project? (Do you know of a simple example, or a tutorial somewhere for that particular case?) Thanks! BoD Geoffrey Wiseman wrote: On Mon, Aug 25, 2008 at 6:13 AM, BoD [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: The main difference I see is that our custom tool handles scm dependencies. What I mean by that is that we have our project which is split in several modules and they all have their own life on subversion, and we say for example that the project is on svn://svn/project1/trunk and it depends on svn://svn/module1/trunk and on svn://svn/module2/branches/v2. Then when we bootstrap the project, the tool will checkout these two modules, and generate an eclipse workspace, with one project by module, and the team plugin setup as needed for the project and its dependencies. So a developer can work on the project itself, but if he finds a problem on a dependency he can also work on it! He has the sources and can commit, etc. When I used to work with maven, we only had jar dependencies, ie, the project depended on built versions of some module (external or internal), which is a bit different. So my question is, is this kind of scm dependency possible with maven? It's a bit of both. If you have a set of related projects that tend to have the same lifecycle, it's not uncommon to put them in a multi-module project. If you go that route, then it's very easy to check out the multi-module project, have Maven build an eclipse workspace, and use them such that a change in one module is automatically reflected in the other modules within eclipse (project dependencies instead of JAR dependencies). If, on the other hand, these are projects that aren't very tightly coupled, then you'd usually stick to JAR-style dependencies, although there may still be another way of making what you want happen. It sounds like the former case is closer to what you need, though. - Geoffrey -- Geoffrey Wiseman - 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: org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-wsdl2code-plugin' does not exist or no valid version could be found
Asif, I was asked to run and paste the mvn -X wsdl2code:wsdl2code output. Here is the same: Thanks for the requested output. I think I found what is wrong in your setup. 1) Your POM (first mail): project modelVersion4.0.0/modelVersion groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version2/version build plugins plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.4/version executions execution goals goalwsdl2code/goal /goals configuration packageNamecom.mblox.soap.paymentapi/packageName wsdlFilepayment.wsdl/wsdlFile /configuration /execution /executions /plugin /plugins /build /project What is your intent? Is this really the axis2-wsdl2code-maven-plugin you are developping or do you just want to use the plugin in your project? You are using the same groupId and artifactId for your module and together with it, you list it as a build plugin. If you just want to use the plugin, please change the groupId and artifactId of your own POM to something else. The section of the build plugin seems OK. 2) Now you still got an error. This is because you specified too much on your command line. If the plugin is correctly implemented, you just have to invoke mvn deploy and the appropriate actions will be executed automatically. So why did you get the error? You specified wsdl2code:wsdl2code on the command line. Maven2 will try to resolve the goal prefix wsdl2code to a plugin. I don't know the exact implementation of this resolving mechanism, but one thing it at least tries is to pre- and postfix your wsdl2code with some default parts. In the end you get maven-wsdl2code-plugin and this plugin gets resolved in the org.apache.maven.plugins and org.codehaus.plugins groupIds. In neither of these groupIds does this plugin exist. So fix the project information of your own pom and just run mvn install or mvn deploy and you should be fine. Ringo * Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes éventuelles peuvent contenir des informations confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce message est adressé exclusivement à son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complète sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez reçu ce message par erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu. * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reworking Build Reactor Order
How do I move it to the bottom of the reactor? I've tried changing dependencies but each time I try to make it dependent on the last thing in the reactor, I get a cyclic dependency error. -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Saturday, August 23, 2008 1:19 AM To: Maven Users List Subject: RE: Reworking Build Reactor Order You can influence it by moving it to the bottom of the modules list in the reactor. If that doesn't do it, then insert a dependency on the others so that it builds last. -Original Message- From: Arthur Gawronski [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 2:50 PM To: users@maven.apache.org Subject: Reworking Build Reactor Order Currently, I have Core Project 1 +SubProject 1-1 +SubProject 1-2 +SubProject 1-3 +CoreProject 1pom - pom.xml Core Project 2 +SubProject 2-1 +SubProject 2-2 +SubProject 2-3 +CoreProject2pom - pom.xml I have no flexibility as to the locations of the folders. The pom in CoreProject2pom references all subprojects as modules. When doing a clean install, the reactor list is built similarly to the following: SubProject1-3 SubProject1-1 SubProject1-2 coreProject2pom SubProject2-2 SubProject2-3 SubProject2-1 The problem is that coreProject2pom creates my distributable. It tries to move copy and create an assembly of SubProject2 jars that haven't packaged yet. How do I change a dependency or include a script in order to force the coreProject2pom to be built last in my reactor? Thanks - 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: SCM dependencies?
On Mon, Aug 25, 2008 at 9:16 AM, Glase, Stefan [EMAIL PROTECTED] wrote: Hi, the free book Maven - The definitive Guide published by Sonatype has a nice chapter on this topic: http://www.sonatype.com/book/reference/multimodule.html Hope to help, Stefan Yes, that's what I would recommend as well, reasonable starting point. I would have included it in the first email, but was running low on time. ;) - Geoffrey -- Geoffrey Wiseman
Re: SCM dependencies?
Thanks a lot! :) BoD Geoffrey Wiseman wrote: On Mon, Aug 25, 2008 at 9:16 AM, Glase, Stefan [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, the free book Maven - The definitive Guide published by Sonatype has a nice chapter on this topic: http://www.sonatype.com/book/reference/multimodule.html Hope to help, Stefan Yes, that's what I would recommend as well, reasonable starting point. I would have included it in the first email, but was running low on time. ;) - Geoffrey -- Geoffrey Wiseman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Taglist and Dashboard
On Mon, Aug 25, 2008 at 5:54 AM, WolfgangRoessler [EMAIL PROTECTED] wrote: I want to include the report of taglist-maven-plugin into my maven-dashboard report. I found out, that currently the taglist-plugin does not support xml-output and therefore cannot be aggregated by the dashboard-plugin. I know there is a patch for this available. When will this patch be incorporated and a new snapshot-release be available? The best place to ask about patches and snapshots is on the development list for the plugin. Both the Taglist and Dashboard plugins are at Codehaus, you can find subscription info here: http://mojo.codehaus.org/taglist-maven-plugin/mail-lists.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Dependency issue
Shakun, try using dependency exclusions ... /exclusions /dependency on one of them. mvn dependency:tree will give you details of all dependencies for your project. From: Shakun Gupta [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 6:30 AM To: Maven Users List Subject: Dependency issue Hi, I am using two dependencies, both are dependent upon apache-comons-collections, but of different versions. So, my final jar / war contains two versions of commons-collections, is there a way to stop this. Regards, Shakun - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: how to manage two different projects with similar project structures
An artifact is uniquely identified by its groupId, artifactId, version and classifier. In your case I hope your groupId, artifactId is different because your 'M' module really(i deduce) is a different module for 'A' 'B' projects. If your M module is a shared module then I suggest that either 'A' or 'B' refer to the other 'M' rather than installing it's own 'M'. You might also want to move out M module in its own project and have both A and B refer to it. You'll have to take into account the lifecycles of your projects and decide what makes the most sense to do. -GJ From: Shakun Gupta [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 6:28 AM To: Maven Users List Subject: how to manage two different projects with similar project structures Hi, I have created two different projects, say A B. Both contain a module, say M. When i run, /mvn install /in both the projects, M gets installed in my local repository at two different locations, but with the same name, say M-1.0.0.jar. Now, if I add the modules M as dependencies to my 3rd application, say D, in the final war of D, only one M is there. Is there a way to change the name of M-1.0.0.jar of A to A-M-1.0.0.jar or some similar name, without explicitly renaming the folder name of module M to A-M and B-M. Regards, Shakun - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: repo1 is down
temporarily switch to another repo ? From: Bouiaw [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 5:53 AM To: Maven Users List Subject: Re: repo1 is down repo1 respond, but it is very very slow : 30 seconds by request ! On Mon, Aug 25, 2008 at 11:35 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote: The problem should be fixed. Cheers The Maven team On Mon, Aug 25, 2008 at 9:59 AM, Brett Porter [EMAIL PROTECTED]wrote: Looks to be an issue here too. I've sent in a support request. 2008/8/25 Glase, Stefan [EMAIL PROTECTED]: Hi, I am having the same problems: 25.08.08 09:27:39 CEST: Unable to update index for central http://repo1.maven.org/maven2/ Cheers Stefan -Ursprüngliche Nachricht- Von: Bouiaw [mailto:[EMAIL PROTECTED] Gesendet: Montag, 25. August 2008 09:51 An: users@maven.apache.org Betreff: repo1 is down Hi, http://repo1.maven.org/maven2 seems to be down or very very slow. Does someone experience the same issue ? - 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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: repo1 is down
Some mirrors are listed here : http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-Listofavailablemaven2mirrors . On Mon, Aug 25, 2008 at 4:29 PM, Jeudy, Guillaume [EMAIL PROTECTED]wrote: temporarily switch to another repo ? From: Bouiaw [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 5:53 AM To: Maven Users List Subject: Re: repo1 is down repo1 respond, but it is very very slow : 30 seconds by request ! On Mon, Aug 25, 2008 at 11:35 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote: The problem should be fixed. Cheers The Maven team On Mon, Aug 25, 2008 at 9:59 AM, Brett Porter [EMAIL PROTECTED] wrote: Looks to be an issue here too. I've sent in a support request. 2008/8/25 Glase, Stefan [EMAIL PROTECTED]: Hi, I am having the same problems: 25.08.08 09:27:39 CEST: Unable to update index for central http://repo1.maven.org/maven2/ Cheers Stefan -Ursprüngliche Nachricht- Von: Bouiaw [mailto:[EMAIL PROTECTED] Gesendet: Montag, 25. August 2008 09:51 An: users@maven.apache.org Betreff: repo1 is down Hi, http://repo1.maven.org/maven2 seems to be down or very very slow. Does someone experience the same issue ? - 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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Re: repo1 is down
On Mon, Aug 25, 2008 at 10:29 AM, Jeudy, Guillaume [EMAIL PROTECTED]wrote: temporarily switch to another repo ? From: Bouiaw [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 5:53 AM To: Maven Users List Subject: Re: repo1 is down repo1 respond, but it is very very slow : 30 seconds by request ! This is one of the many reasons I'd recommend that any remotely serious maven user consider using a mirror/proxy arrangement like Nexus or Artifactory. - Geoffrey -- Geoffrey Wiseman
Re: repo1 is down
Yes it's always one reason of this good practice, but it's not why we don't have to fix it. Contegix is checking if we have another problem ... Arnaud On Mon, Aug 25, 2008 at 4:39 PM, Geoffrey Wiseman [EMAIL PROTECTED] wrote: On Mon, Aug 25, 2008 at 10:29 AM, Jeudy, Guillaume [EMAIL PROTECTED] wrote: temporarily switch to another repo ? From: Bouiaw [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 5:53 AM To: Maven Users List Subject: Re: repo1 is down repo1 respond, but it is very very slow : 30 seconds by request ! This is one of the many reasons I'd recommend that any remotely serious maven user consider using a mirror/proxy arrangement like Nexus or Artifactory. - Geoffrey -- Geoffrey Wiseman -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Change order of plugins in the same phase
Hi all,
my problem is the following: I want to execute a plugin (the
exec-maven-plugin ) in the deploy phase. But this should be done before
the maven-deploy-plugin execution. I also know that, as from maven 2.0.5,
the order of the plugin-definition in the pom determine the order in which
they will be executed. But somehow it seems that this does not work for
the 'default'-phase-plugins. Or is it just some kind of incomplete
configuration? See below for my test-pom and test result.
Any help is welcome.
Thanks
Klaus
Test:
I tested it, not with the deploy phase but with the compile. So the
build-plugins-section of my pom was change like the following..
...
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
executions
execution
idRunFileThatStartsProductBuilding/id
phasecompile/phase
goals
goalexec/goal
/goals
/execution
/executions
configuration
executablecmd/executable´
workingDirectory${basedir}/workingDirectory
arguments
argument/c/argument
argumentdir/argument
/arguments
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
/plugin
...
But the result was the following..
[INFO] [clean:clean]
[INFO] Deleting directory c:\heuk\workspaces\mavenProjectBuilding\target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 1 source file to
c:\heuk\workspaces\mavenProjectBuilding\target\classes
[INFO] [exec:exec {execution: RunAntFileThatStartsProductBuildingZip}]
[INFO] Volume in Laufwerk C: hat keine Bezeichnung.
[INFO] Volumeseriennummer: 382D-8F67
[INFO]
[INFO] Verzeichnis von c:\heuk\workspaces\mavenProjectBuilding
[INFO]
[INFO] 25.08.2008 15:45DIR .
[INFO] 25.08.2008 15:45DIR ..
[INFO] 25.08.2008 15:45 4.071 pom.xml
[INFO] 25.08.2008 08:35DIR src
[INFO] 25.08.2008 15:45DIR target
[INFO]1 Datei(en) 4.071 Bytes
[INFO]4 Verzeichnis(se), 3.988.070.400 Bytes frei
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Mon Aug 25 15:45:53 CEST 2008
[INFO] Final Memory: 7M/14M
[INFO]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
when maven2 downloads dependencies
Hi, My local repo is populated to build my project, I'm not using any SNAPSHOT versions as dependencies. Can someone tell me why maven stubbornly does a remote lookup to repo1 wasting valuable time ? (it does not download anything I just get log entries like): Downloading: http://repo1.maven.org/maven2/com/sun/facelets/jsf-facelets/1.1.14/ jsf-facelets-1.1.14.pom Thanks, -Guillaume This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: when maven2 downloads dependencies
This pom isn't in your local repository so maven try to download it, but it doesn' exist on repo1 too so it will try for each build. Emmanuel On Mon, Aug 25, 2008 at 4:58 PM, Jeudy, Guillaume [EMAIL PROTECTED]wrote: Hi, My local repo is populated to build my project, I'm not using any SNAPSHOT versions as dependencies. Can someone tell me why maven stubbornly does a remote lookup to repo1 wasting valuable time ? (it does not download anything I just get log entries like): Downloading: http://repo1.maven.org/maven2/com/sun/facelets/jsf-facelets/1.1.14/ jsf-facelets-1.1.14.pomhttp://repo1.maven.org/maven2/com/sun/facelets/jsf-facelets/1.1.14/jsf-facelets-1.1.14.pom Thanks, -Guillaume This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC10
Multi-module project fails with NPE on assembly:assembly (assembly plugin
used 2.2-beta-1; command used was mvn clean install assembly:assembly
eclipse:eclipse). Same configuration works with Maven 2.0.9. Below you will
find relevant excerpt from the build trace.
Best regards,
Thorsten
[INFO]
[INFO] Building OSIRIS Next
[INFO]task-segment: [assembly:assembly] (aggregator-style)
[INFO]
[INFO] Preparing assembly:assembly
[INFO]
[INFO] Building OSIRIS Next
[INFO]
[INFO] [enforcer:enforce {execution: enforce-maven}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1426)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:410)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1032)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:274)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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)
[INFO]
[INFO] Total time: 55 minutes 18 seconds
[INFO] Finished at: Mon Aug 25 17:18:11 CEST 2008
[INFO] Final Memory: 36M/126M
[INFO]
--
View this message in context:
http://www.nabble.com/-PLEASE-TEST--Maven-2.0.10-RC10-tp19117054p19146039.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: when maven2 downloads dependencies
Emmanuel, Thanks very nice insight, I didnt realize this. Does this mean that any libraries not on central repo should have it's own pom ? If that project wasn't built with maven surely it wouldnt have a pom installed in the repo correct ? Lastly, how do you suggest I cleanup this situation? Should I manually create poms for these artifacts or can I find a way to turnoff pom lookup in repo altogether ? Ok, probably library owners should fix their own maven uploads but Id rather not get into this timeconsuming approach.. :) I tried the -o switch for running maven in offline mode and it seems to fulfill my needs so far. Thanks, GJ From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 11:24 AM To: Maven Users List Subject: Re: when maven2 downloads dependencies This pom isn't in your local repository so maven try to download it, but it doesn' exist on repo1 too so it will try for each build. Emmanuel On Mon, Aug 25, 2008 at 4:58 PM, Jeudy, Guillaume [EMAIL PROTECTED]wrote: Hi, My local repo is populated to build my project, I'm not using any SNAPSHOT versions as dependencies. Can someone tell me why maven stubbornly does a remote lookup to repo1 wasting valuable time ? (it does not download anything I just get log entries like): Downloading: http://repo1.maven.org/maven2/com/sun/facelets/jsf-facelets/1.1.14/ jsf-facelets-1.1.14.pomhttp://repo1.maven.org/maven2/com/sun/facelets/jsf-facelets/1.1.14/jsf-facelets-1.1.14.pom Thanks, -Guillaume This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: when maven2 downloads dependencies
It is always better to create a minimal pom when you install a new artifact instead of no pom. If you use mvn install:install-file, you can add -DgeneratePom=true parameter if you don't want to write one http://maven.apache.org/plugins/maven-install-plugin/examples/generic-pom-generation.html Emmanuel On Mon, Aug 25, 2008 at 5:40 PM, Jeudy, Guillaume [EMAIL PROTECTED]wrote: Emmanuel, Thanks very nice insight, I didnt realize this. Does this mean that any libraries not on central repo should have it's own pom ? If that project wasn't built with maven surely it wouldnt have a pom installed in the repo correct ? Lastly, how do you suggest I cleanup this situation? Should I manually create poms for these artifacts or can I find a way to turnoff pom lookup in repo altogether ? Ok, probably library owners should fix their own maven uploads but Id rather not get into this timeconsuming approach.. :) I tried the -o switch for running maven in offline mode and it seems to fulfill my needs so far. Thanks, GJ From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 11:24 AM To: Maven Users List Subject: Re: when maven2 downloads dependencies This pom isn't in your local repository so maven try to download it, but it doesn' exist on repo1 too so it will try for each build. Emmanuel On Mon, Aug 25, 2008 at 4:58 PM, Jeudy, Guillaume [EMAIL PROTECTED] wrote: Hi, My local repo is populated to build my project, I'm not using any SNAPSHOT versions as dependencies. Can someone tell me why maven stubbornly does a remote lookup to repo1 wasting valuable time ? (it does not download anything I just get log entries like): Downloading: http://repo1.maven.org/maven2/com/sun/facelets/jsf-facelets/1.1.14/ jsf-facelets-1.1.14.pom http://repo1.maven.org/maven2/com/sun/facelets/jsf-facelets/1.1.14/jsf-facelets-1.1.14.pom Thanks, -Guillaume This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: when maven2 downloads dependencies
Hello You can use the maven repo on java.net, which contains facelets. https://maven-repository.dev.java.net/ Don't know if it is a good policy though. Is there a way to make them use the central repo? Regards Marcelo Morales On Mon, Aug 25, 2008 at 10:58 AM, Jeudy, Guillaume [EMAIL PROTECTED] wrote: Hi, My local repo is populated to build my project, I'm not using any SNAPSHOT versions as dependencies. Can someone tell me why maven stubbornly does a remote lookup to repo1 wasting valuable time ? (it does not download anything I just get log entries like): Downloading: http://repo1.maven.org/maven2/com/sun/facelets/jsf-facelets/1.1.14/ jsf-facelets-1.1.14.pom Thanks, -Guillaume This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. - 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: Having trouble with Maven release plugin using SubVersion
I think I found a solution: Before issuing the 'mvn release:prepare' command, an 'svn update' on the parent directory of the directory renamed (or at the top level) will update the SubVersion metadata. The update command doesn't print anything so it appears like it doesn't do anything, but it's required nonetheless. Would there be any harm in having the release plugin perform an 'svn update' at the start of the release:prepare goal? Also found a few flaws with my earlier perl script. Should have issued a 'mvn clean' at line 87 so the target directory is not added to version control. Forgot to add a tags directory: mkdir aProject/tags, after line 106 Could have left out the creation of a sample configuration file (myconf.xml) lines 88 to 100, it wasn't needed to reproduce the problem. The directory name could have been foo and renamed to bar, so this has nothing to do with the standard maven 2 naming convention of src/main/config. If I created a FILE, not a directory, then there would be no error, even without the 'svn update'. -Ken Dennis Lundberg wrote: Did you use the 'svn move ...' command to rename the directory or did you do it directly on the file system for your working copy? If you did the second your working copy will not have correct subversion metadata. Ken Tanaka wrote: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Having trouble with Maven release plugin using SubVersion
Ken Tanaka wrote: Before issuing the 'mvn release:prepare' command, an 'svn update' on the parent directory of the directory renamed (or at the top level) will update the SubVersion metadata. The update command doesn't print anything so it appears like it doesn't do anything, but it's required nonetheless. Would there be any harm in having the release plugin perform an 'svn update' at the start of the release:prepare goal? I have run into problems in the past with the release plugin and working copies that were fully checked in, but not up to date. I would argue that the equivalent of an svn update is performed by the release plugin when the check is made whether everything is checked in. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: Having trouble with Maven release plugin using SubVersion
Would there be any harm in having the release plugin
perform an 'svn update' at the start of the release:prepare goal?
I think this would be no good idea. One of the prerequisites for a project to
be released is that there is NO change between your current work and the branch
your currently on ('trunk' also counts as a branch for this). The
ScmCheckForModificationsPhase calls a scm:status and looks for changed files.
Automatically updating first would mean that you may get changes from another
checkin, which are merged into your own source silently! So you do a release
and CANNOT BE SURE that it really has the contentyou thought of.
LieGrue,
strub
--- Ken Tanaka [EMAIL PROTECTED] schrieb am Mo, 25.8.2008:
Von: Ken Tanaka [EMAIL PROTECTED]
Betreff: Re: Having trouble with Maven release plugin using SubVersion
An: Maven Users List users@maven.apache.org
CC: [EMAIL PROTECTED]
Datum: Montag, 25. August 2008, 19:14
I think I found a solution:
Before issuing the 'mvn release:prepare' command,
an 'svn update' on
the parent directory of the directory renamed (or at the
top level) will
update the SubVersion metadata. The update command
doesn't print
anything so it appears like it doesn't do anything, but
it's required
nonetheless. Would there be any harm in having the release
plugin
perform an 'svn update' at the start of the
release:prepare goal?
Also found a few flaws with my earlier perl script.
Should have issued a 'mvn clean' at line 87 so the
target directory is
not added to version control.
Forgot to add a tags directory: mkdir aProject/tags, after
line 106
Could have left out the creation of a sample configuration
file
(myconf.xml) lines 88 to 100, it wasn't needed to
reproduce the problem.
The directory name could have been foo and
renamed to bar, so this
has nothing to do with the standard maven 2 naming
convention of
src/main/config.
If I created a FILE, not a directory, then there would be
no error, even
without the 'svn update'.
-Ken
Dennis Lundberg wrote:
Did you use the 'svn move ...' command to
rename the directory or did
you do it directly on the file system for your working
copy?
If you did the second your working copy will not have
correct subversion
metadata.
Ken Tanaka wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen
Massenmails.
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Having trouble with Maven release plugin using SubVersion
Would there be any harm in having the release plugin
perform an 'svn update' at the start of the release:prepare goal?
I think this would be no good idea. One of the prerequisites for a project to
be released is that there is NO change between your current work and the branch
your currently on ('trunk' also counts as a branch for this). The
ScmCheckForModificationsPhase calls a scm:status and looks for changed files.
Automatically updating first would mean that you may get changes from another
checkin, which are merged into your own source silently! So you do a release
and CANNOT BE SURE that it really has the contentyou thought of.
LieGrue,
strub
--- Ken Tanaka [EMAIL PROTECTED] schrieb am Mo, 25.8.2008:
Von: Ken Tanaka [EMAIL PROTECTED]
Betreff: Re: Having trouble with Maven release plugin using SubVersion
An: Maven Users List users@maven.apache.org
CC: [EMAIL PROTECTED]
Datum: Montag, 25. August 2008, 19:14
I think I found a solution:
Before issuing the 'mvn release:prepare' command,
an 'svn update' on
the parent directory of the directory renamed (or at the
top level) will
update the SubVersion metadata. The update command
doesn't print
anything so it appears like it doesn't do anything, but
it's required
nonetheless. Would there be any harm in having the release
plugin
perform an 'svn update' at the start of the
release:prepare goal?
Also found a few flaws with my earlier perl script.
Should have issued a 'mvn clean' at line 87 so the
target directory is
not added to version control.
Forgot to add a tags directory: mkdir aProject/tags, after
line 106
Could have left out the creation of a sample configuration
file
(myconf.xml) lines 88 to 100, it wasn't needed to
reproduce the problem.
The directory name could have been foo and
renamed to bar, so this
has nothing to do with the standard maven 2 naming
convention of
src/main/config.
If I created a FILE, not a directory, then there would be
no error, even
without the 'svn update'.
-Ken
Dennis Lundberg wrote:
Did you use the 'svn move ...' command to
rename the directory or did
you do it directly on the file system for your working
copy?
If you did the second your working copy will not have
correct subversion
metadata.
Ken Tanaka wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen
Massenmails.
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC10
It seems that you don't have the maven-compiler-plugin configured correctly. You must set the source as 1.5 to use Enums. See [1] for more information. [1]http://maven.apache.org/general.html#Compiling-J2SE-5 Nope, I have that configured - and as I said, it's working with Maven 2.09... Peter
Re: JavaDoc-Report crashes with TestNG
I think you need to set source instead. If that doesn't work, please describe what the crash looks like. Cheers, Brett 2008/8/25 WolfgangRoessler [EMAIL PROTECTED]: I set the javadocVersion, but the plugin still crashes. - Wolfgang Brett Porter wrote: Do you need to configure it to use Java's 1.5 source level? - Brett 2008/8/25 WolfgangRoessler [EMAIL PROTECTED]: Hello, I have configured the maven-javadoc-plugin in the reporting section. Unfortunately when generating the report, the plugin crashes. The exceptions look like it has problems with the @Test annotation of TestNG. Any ideas or solutions what happens? Greets Wolfgang Roessler -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19139379.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19140451.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: artifact built from maven-nuxeo-plugin being installed before execution of following plugins
You have 3 alternatives:
- put the nuxeo plugin in the install phase (though I assume since
it's also producing an installable artifact you don't want that)
- change the nuxeo plugin to look up the artifact from the already
attached artifacts on the project first before falling back to the
local repository
- manually install the first assembly in the package phase (which
would seem a bit counterintuitive)
The second is probably the best if it is an option.
BTW, the group ID for your nuxeo plugin should probably be something
other than o.a.m.plugins to avoid confusion.
Cheers,
Brett
2008/8/25 Julien CARSIQUE [EMAIL PROTECTED]:
Hi,
I need to build resources artifacts (I use maven-assembly-plugin) and use
them (with our maven-nuxeo-plugin) from the same pom.xml
The built resources artifacts do not need to be in the project dependency
but have to be installed before the execution of the second plugin.
Is it possible to make artifacts built from maven-assembly-plugin being
installed before the execution of the following maven-nuxeo-plugin ?
I have this error when running mvn install:
[INFO]
[INFO] Building Nuxeo EP EAR
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/Users/julien/Documents/workspace/nuxeo/nuxeo-platform/nuxeo-platform-ear/target
...
[INFO] [assembly:attached {execution: make-resources}]
[INFO] Reading assembly descriptor: src/main/assemble/resources/mono.xml
...
[INFO] Building zip:
/Users/julien/Documents/workspace/nuxeo/nuxeo-platform/nuxeo-platform-ear/target/nuxeo-platform-ear-5.1.6-SNAPSHOT-resources-mono.zip
...
[INFO] [nuxeo:assembly {execution: assemble-ear}]
[INFO] Loading assembly descriptor:
/Users/julien/Documents/workspace/nuxeo/nuxeo-platform/nuxeo-platform-ear/src/main/assemble/nuxeo.xml
...
org.apache.maven.plugin.MojoExecutionException: Unable to find artifact.
...
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.nuxeo.ecm.platform
-DartifactId=nuxeo-platform-ear -Dversion=5.1.6-SNAPSHOT
-Dclassifier=resources-mono -Dpackaging=zip -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.nuxeo.ecm.platform
-DartifactId=nuxeo-platform-ear -Dversion=5.1.6-SNAPSHOT
-Dclassifier=resources-mono -Dpackaging=zip -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to run assembly
Here's an extract of my pom.xml:
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptorsrc/main/assemble/resources/mono.xml/descriptor
...
/descriptors
/configuration
executions
execution
idmake-resources/id
phasepackage/phase
goals
goalattached/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-nuxeo-plugin/artifactId
extensionstrue/extensions
executions
execution
idassemble-ear/id
phasepackage/phase
goals
goalassembly/goal
/goals
configuration
...
/configuration
/execution
/executions
/plugin
Thanks,
--
Julien CARSIQUE, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[EMAIL PROTECTED] | Tel: +33 1 40 33 79 87
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reworking Build Reactor Order
It sounds like coreproject2pom should depend on all of the subproject2 jars since it is making an assembly of them. If doing that gives you a cyclic dependency error, make sure nothing depends on coreproject2pom as it doesn't appear it is necessary. What cycle does Maven indicate you have? - Brett 2008/8/25 Arthur Gawronski [EMAIL PROTECTED]: How do I move it to the bottom of the reactor? I've tried changing dependencies but each time I try to make it dependent on the last thing in the reactor, I get a cyclic dependency error. -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Saturday, August 23, 2008 1:19 AM To: Maven Users List Subject: RE: Reworking Build Reactor Order You can influence it by moving it to the bottom of the modules list in the reactor. If that doesn't do it, then insert a dependency on the others so that it builds last. -Original Message- From: Arthur Gawronski [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 2:50 PM To: users@maven.apache.org Subject: Reworking Build Reactor Order Currently, I have Core Project 1 +SubProject 1-1 +SubProject 1-2 +SubProject 1-3 +CoreProject 1pom - pom.xml Core Project 2 +SubProject 2-1 +SubProject 2-2 +SubProject 2-3 +CoreProject2pom - pom.xml I have no flexibility as to the locations of the folders. The pom in CoreProject2pom references all subprojects as modules. When doing a clean install, the reactor list is built similarly to the following: SubProject1-3 SubProject1-1 SubProject1-2 coreProject2pom SubProject2-2 SubProject2-3 SubProject2-1 The problem is that coreProject2pom creates my distributable. It tries to move copy and create an assembly of SubProject2 jars that haven't packaged yet. How do I change a dependency or include a script in order to force the coreProject2pom to be built last in my reactor? Thanks - 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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Change order of plugins in the same phase
You're correct - in all versions of Maven, the default lifecycle
phases are executed first by definition.
Perhaps you can describe more about what your exec plugin execution is
designed to do, and we can offer some alternate suggestions for how to
run it.
Cheers,
Brett
2008/8/26 [EMAIL PROTECTED]:
Hi all,
my problem is the following: I want to execute a plugin (the
exec-maven-plugin ) in the deploy phase. But this should be done before
the maven-deploy-plugin execution. I also know that, as from maven 2.0.5,
the order of the plugin-definition in the pom determine the order in which
they will be executed. But somehow it seems that this does not work for
the 'default'-phase-plugins. Or is it just some kind of incomplete
configuration? See below for my test-pom and test result.
Any help is welcome.
Thanks
Klaus
Test:
I tested it, not with the deploy phase but with the compile. So the
build-plugins-section of my pom was change like the following..
...
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
executions
execution
idRunFileThatStartsProductBuilding/id
phasecompile/phase
goals
goalexec/goal
/goals
/execution
/executions
configuration
executablecmd/executable´
workingDirectory${basedir}/workingDirectory
arguments
argument/c/argument
argumentdir/argument
/arguments
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
/plugin
...
But the result was the following..
[INFO] [clean:clean]
[INFO] Deleting directory c:\heuk\workspaces\mavenProjectBuilding\target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 1 source file to
c:\heuk\workspaces\mavenProjectBuilding\target\classes
[INFO] [exec:exec {execution: RunAntFileThatStartsProductBuildingZip}]
[INFO] Volume in Laufwerk C: hat keine Bezeichnung.
[INFO] Volumeseriennummer: 382D-8F67
[INFO]
[INFO] Verzeichnis von c:\heuk\workspaces\mavenProjectBuilding
[INFO]
[INFO] 25.08.2008 15:45DIR .
[INFO] 25.08.2008 15:45DIR ..
[INFO] 25.08.2008 15:45 4.071 pom.xml
[INFO] 25.08.2008 08:35DIR src
[INFO] 25.08.2008 15:45DIR target
[INFO]1 Datei(en) 4.071 Bytes
[INFO]4 Verzeichnis(se), 3.988.070.400 Bytes frei
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Mon Aug 25 15:45:53 CEST 2008
[INFO] Final Memory: 7M/14M
[INFO]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How to cope with conflicting jar versions
In my project there are many direct and indirect dependencies at the lowest level on springframework jars. One such dependency requires use of the most recent springframework jars. Migrating to latest version of spring is my projects direct dependency causes problems at runtime with other dependencies which expect older versions of apis from spring and its dependencies. Is there a good way to deal with this dependency hell? If so I would appreciate any advice. Thanks. -- Regards, Farrukh Najmi Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PLEASE TEST] Maven 2.0.10-RC11
Hi again, One bug was identified in 2.0.10-RC10 last Friday night. This release candidate addresses that issue. You can find it here: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/ Please give this a spin when you get a chance, and let us know if you find any problems. We'll file any issues in JIRA against version 2.0.10 for tracking purposes, and to give us a JIRA # to use when writing the integration test to verify the fix. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: manipulating an existing archive during assembly
On Fri, Aug 22, 2008 at 2:03 PM, Beyer,Nathan [EMAIL PROTECTED] wrote: I'm using the assembly plugin to generate a few archives for distribution. I'd like to be able to download an existing archive (zip, tar.gz) and extract some of its contents and then include it in an assembly. Does anyone have suggestions on how to go about this? For example, download a tomcat distribution, extract the contents, remove all existing files/dirs in 'webapps' and then add a war file and create an assembly of the results. The WAR plugin can do overlays, but in this case you're not dealing with a WAR. The Shade plugin can also do some serious transformations, although the documentation's pretty spotty. The easiest thing is probably what Brett already suggested. - Geoffrey -- Geoffrey Wiseman
Re: How to cope with conflicting jar versions
in most recent versions of Maven, dependencyManagement can be used to enforce a particular version throughout the entire tree. You can also use the enforcer plugin to ensure this has been properly applied. Cheers, Brett 2008/8/26 Farrukh Najmi [EMAIL PROTECTED]: In my project there are many direct and indirect dependencies at the lowest level on springframework jars. One such dependency requires use of the most recent springframework jars. Migrating to latest version of spring is my projects direct dependency causes problems at runtime with other dependencies which expect older versions of apis from spring and its dependencies. Is there a good way to deal with this dependency hell? If so I would appreciate any advice. Thanks. -- Regards, Farrukh Najmi Web: http://www.wellfleetsoftware.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Questions
I am evaluating transitioning a large Ant build system that manages dozens of Java and .NET projects over to Maven and was hoping someone could answer a few questions: 1) The Java support in Maven seems comprehensive, but .NET support (I'm looking in NMaven) seems very limited. I see support for building .NET libraries and desktop applications. Is there any support for building ASP.NET web applications, .msi installers, manifest signatures, or ClickOnce published installers? Are these things going to be available, even at an incubation/beta level in the near future? 2) My employer's build process uses a custom packaging and installer builder that bundles up binaries, web sites, and other project outputs from dozens of Java/.NET projects and packages them into one huge installer. Can I write some kind of Maven plugin to integrate this into the end of a Maven build? What is the name of the relevant plugin technology that I should investigate using? At a brief, high-level, how would this work? 3) Is there any way that Maven can be configured so that if a single project fails to build, all other projects continue building? At my current job, we have problems that when a single developer checks in a bad change, the whole build fails, even on logically unrelated projects. We depend on an automated nightly central build process and when this breaks, it's a big productivity problem. 4) Does Maven have any build reporting features? I was hoping for basic HTML reports on which projects built successfully, which failed, and how long they took. Do I need to use an external tool to get this kind of functionality? Thanks! -- View this message in context: http://www.nabble.com/Maven-Questions-tp19150963p19150963.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: [PLEASE TEST] Maven 2.0.10-RC10
What's your target and source set to in the compiler plugin configuration? Are you certain the exact same POM is working in 2.0.9? -john Peter Horlock wrote: Using RC10, the following fails, which was working with 2.0.9: (seems like it doesn't like enums?!) mvn clean tomcat:deploy -o [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'tomcat'. [INFO] [INFO] Building webclient [INFO]task-segment: [clean, tomcat:deploy] [INFO] [INFO] [clean:clean] [INFO] Deleting directory target [INFO] Preparing tomcat:deploy [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 57 source files to target\classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure MyClass.java:[22,1] annotations are not supported in -source 1.3 (try -source 1.5 to enable annotations) @SuppressWarnings(nls) *MyEnum.java:[17,7] 'class' or 'interface' expected* [...other, similar errors...] [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:338) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682) ... 20 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Mon Aug 25 13:32:46 CEST 2008 [INFO] Final Memory: 11M/20M [INFO] - -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC10
Can you provide a failing test case we could use as a basis for an integration test? Something that would help us debug your specific use case would be very helpful. Thanks, -john Peter Horlock wrote: It seems that you don't have the maven-compiler-plugin configured correctly. You must set the source as 1.5 to use Enums. See [1] for more information. [1]http://maven.apache.org/general.html#Compiling-J2SE-5 Nope, I have that configured - and as I said, it's working with Maven 2.09... Peter -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC11
Well, looks like I lost track of a few issues that came up with RC10. I'll work on addressing those issues, and probably follow up with an RC12 if we find bugs. -john John Casey wrote: Hi again, One bug was identified in 2.0.10-RC10 last Friday night. This release candidate addresses that issue. You can find it here: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/ Please give this a spin when you get a chance, and let us know if you find any problems. We'll file any issues in JIRA against version 2.0.10 for tracking purposes, and to give us a JIRA # to use when writing the integration test to verify the fix. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC10
Please file a JIRA issue in http://jira.codehaus.org/browse/MNG and
attach a failing test project, if possible, that we could use to verify
the problem. The information below is far too little to diagnose the
problem.
Thanks,
-john
TM wrote:
Multi-module project fails with NPE on assembly:assembly (assembly plugin
used 2.2-beta-1; command used was mvn clean install assembly:assembly
eclipse:eclipse). Same configuration works with Maven 2.0.9. Below you will
find relevant excerpt from the build trace.
Best regards,
Thorsten
[INFO]
[INFO] Building OSIRIS Next
[INFO]task-segment: [assembly:assembly] (aggregator-style)
[INFO]
[INFO] Preparing assembly:assembly
[INFO]
[INFO] Building OSIRIS Next
[INFO]
[INFO] [enforcer:enforce {execution: enforce-maven}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1426)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:410)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1032)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:274)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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)
[INFO]
[INFO] Total time: 55 minutes 18 seconds
[INFO] Finished at: Mon Aug 25 17:18:11 CEST 2008
[INFO] Final Memory: 36M/126M
[INFO]
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: JavaDoc-Report crashes with TestNG
Unfortunately this doesn't work, too. Here are some snippets of my pom: dependencies dependency groupIdorg.testng/groupId artifactIdtestng/artifactId version5.8/version classifierjdk15/classifier scopetest/scope /dependency /dependencies reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId configuration source1.6/source aggregatetrue/aggregate /configuration /plugin /plugins reporting And here part of the error messages (debug-mode): While building project: Group-Id: prototype.codequality Artifact-Id: top Version: 0.0.1-SNAPSHOT From file: S:\src\Exploratory Prototypes\CodeQualityTools\src\top\pom.xml Reason: Error during page generation org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: Exit code: 1 - S:\src\Exploratory Prototypes\CodeQualityTools\src\top\top-module1\src\test\java\codequality\top\module1\TestClassInModule1.java:3: package org.testng does not exist import org.testng.Assert; ^ S:\src\Exploratory Prototypes\CodeQualityTools\src\top\top-module1\src\test\java\codequality\top\module1\TestClassInModule1.java:4: package org.testng.annotations does not exist import org.testng.annotations.Test; ^ ... java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc at com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46) at com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:811) ... Greets Wolfgang Brett Porter wrote: I think you need to set source instead. If that doesn't work, please describe what the crash looks like. Cheers, Brett 2008/8/25 WolfgangRoessler [EMAIL PROTECTED]: I set the javadocVersion, but the plugin still crashes. - Wolfgang Brett Porter wrote: Do you need to configure it to use Java's 1.5 source level? - Brett 2008/8/25 WolfgangRoessler [EMAIL PROTECTED]: Hello, I have configured the maven-javadoc-plugin in the reporting section. Unfortunately when generating the report, the plugin crashes. The exceptions look like it has problems with the @Test annotation of TestNG. Any ideas or solutions what happens? Greets Wolfgang Roessler -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19139379.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19140451.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19151139.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]
JDepend for pom-project
Hello, I have a multi-module project. The top project has the packaging type pom and I have configured jdepend-maven-plugin in the reporting section, so that jdepend gets executed for all modules. But the build stops when executing jdepend for the top project with the following message: Directory does not exist: S:\src\Exploratory Prototypes\CodeQualityTools\src\top\target\classes It looks like JDepend does not work for pom-projects. Any solutions for this? Do I have to configure JDepend for each module? Greets Wolfgang -- View this message in context: http://www.nabble.com/JDepend-for-pom-project-tp19151632p19151632.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: Problems with SCM:UPDATE on linux with Subversion.
I seem to be having problems receiving message from this list so I apologies for the late response. I did not do an su USERNAME and root is not specified in the SCM url. Any other thoughts? Dave. Brett Porter wrote: How did you log in to the account? IF it happened to be su USERNAME from root, you would still have root's environment. Other than that, the only reason I can think of is that root is specified in the SCM URL. - Brett 2008/8/23 Dave Rathnow [EMAIL PROTECTED]: I'm having a problem with SCM plugin on Linux. I've checked out a project from Subversion using my personal account and then tried to do an scm:update. Rather than using the account I am logged in as, the plugin is using root and so the command failes. Below is a snipped from the log: [INFO] [INFO] [scm:update] [INFO] Executing: svn --username root --password * --non-interactive update [INFO] Working directory: /home/cruser/cc/checkout/fine.head/build [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: PROPFIND request failed on '/svn/umsrepo/trunk/fine/build' svn: PROPFIND of '/svn/umsrepo/trunk/fine/build': authorization failed (http://elmer http://elmer/ ) For some reason, the plugin is trying to use root to do the update. I've done the same thing on Windows an do not have this problem. Does anyone know why the plugin is using root and not the user that I am running the update command under? Thanks, Dave. -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Problems-with-SCM%3AUPDATE-on-linux-with-Subversion.-tp19112563p19152219.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: repo1 is down
I agree with this good practice. We have planned to install an Archiva server in the next weeks. On Mon, Aug 25, 2008 at 4:43 PM, Arnaud HERITIER [EMAIL PROTECTED] wrote: Yes it's always one reason of this good practice, but it's not why we don't have to fix it. Contegix is checking if we have another problem ... Arnaud On Mon, Aug 25, 2008 at 4:39 PM, Geoffrey Wiseman [EMAIL PROTECTED] wrote: On Mon, Aug 25, 2008 at 10:29 AM, Jeudy, Guillaume [EMAIL PROTECTED] wrote: temporarily switch to another repo ? From: Bouiaw [mailto:[EMAIL PROTECTED] Sent: Mon 25/08/2008 5:53 AM To: Maven Users List Subject: Re: repo1 is down repo1 respond, but it is very very slow : 30 seconds by request ! This is one of the many reasons I'd recommend that any remotely serious maven user consider using a mirror/proxy arrangement like Nexus or Artifactory. - Geoffrey -- Geoffrey Wiseman -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Questions
2008/8/26 MassimoH [EMAIL PROTECTED]: I am evaluating transitioning a large Ant build system that manages dozens of Java and .NET projects over to Maven and was hoping someone could answer a few questions: 1) The Java support in Maven seems comprehensive, but .NET support (I'm looking in NMaven) seems very limited. I see support for building .NET libraries and desktop applications. Is there any support for building ASP.NET web applications, .msi installers, manifest signatures, or ClickOnce published installers? Are these things going to be available, even at an incubation/beta level in the near future? That's best asked at nmaven-dev@ - I think the first 3 have at least some preliminary support, and I hope you'll find that they're receptive to helping you achieve what you need. 2) My employer's build process uses a custom packaging and installer builder that bundles up binaries, web sites, and other project outputs from dozens of Java/.NET projects and packages them into one huge installer. Can I write some kind of Maven plugin to integrate this into the end of a Maven build? What is the name of the relevant plugin technology that I should investigate using? At a brief, high-level, how would this work? Yes, you can. The general approach is to assemble what you want with the assembly plugin (if necessary) and then create a plugin using the normal Java mojo technique to bundle those files. The installer technology you are using need to either have a Java API or a command line you can execute. 3) Is there any way that Maven can be configured so that if a single project fails to build, all other projects continue building? At my current job, we have problems that when a single developer checks in a bad change, the whole build fails, even on logically unrelated projects. We depend on an automated nightly central build process and when this breaks, it's a big productivity problem. There's --fail-at-end, that should also skip modules that depend on a failed module. Continuum specifically facilitates doing centralised builds that way, and I'm sure other CI servers can be configured as such. 4) Does Maven have any build reporting features? I was hoping for basic HTML reports on which projects built successfully, which failed, and how long they took. Do I need to use an external tool to get this kind of functionality? We generally rely on the continuous integration/build servers to provide that functionality. Maven's built in reporting is generally focused on tools that analyse the source control, not the build activity itself. Cheers, Brett Thanks! -- View this message in context: http://www.nabble.com/Maven-Questions-tp19150963p19150963.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with SCM:UPDATE on linux with Subversion.
I found the problem. I had copied my settings.xml file from a windows box and did not remove a server/server entry. It had specified root as the account to use for this particular machine. I removed it and everything works fine now. Dave Rathnow wrote: I seem to be having problems receiving message from this list so I apologies for the late response. I did not do an su USERNAME and root is not specified in the SCM url. Any other thoughts? Dave. Brett Porter wrote: How did you log in to the account? IF it happened to be su USERNAME from root, you would still have root's environment. Other than that, the only reason I can think of is that root is specified in the SCM URL. - Brett 2008/8/23 Dave Rathnow [EMAIL PROTECTED]: I'm having a problem with SCM plugin on Linux. I've checked out a project from Subversion using my personal account and then tried to do an scm:update. Rather than using the account I am logged in as, the plugin is using root and so the command failes. Below is a snipped from the log: [INFO] [INFO] [scm:update] [INFO] Executing: svn --username root --password * --non-interactive update [INFO] Working directory: /home/cruser/cc/checkout/fine.head/build [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: PROPFIND request failed on '/svn/umsrepo/trunk/fine/build' svn: PROPFIND of '/svn/umsrepo/trunk/fine/build': authorization failed (http://elmer http://elmer/ ) For some reason, the plugin is trying to use root to do the update. I've done the same thing on Windows an do not have this problem. Does anyone know why the plugin is using root and not the user that I am running the update command under? Thanks, Dave. -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Problems-with-SCM%3AUPDATE-on-linux-with-Subversion.-tp19112563p19152363.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: JavaDoc-Report crashes with TestNG
That looks like a bug in the javadoc plugin that it isn't using test scoped dependencies for the test javadoc (if you change the scope of testng to compile or runtime, does it work even though it is not correct?) I'm not sure about the doclet exception - looks like a javadoc error - does running javadoc standalone work? - Brett 2008/8/26 WolfgangRoessler [EMAIL PROTECTED]: Unfortunately this doesn't work, too. Here are some snippets of my pom: dependencies dependency groupIdorg.testng/groupId artifactIdtestng/artifactId version5.8/version classifierjdk15/classifier scopetest/scope /dependency /dependencies reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId configuration source1.6/source aggregatetrue/aggregate /configuration /plugin /plugins reporting And here part of the error messages (debug-mode): While building project: Group-Id: prototype.codequality Artifact-Id: top Version: 0.0.1-SNAPSHOT From file: S:\src\Exploratory Prototypes\CodeQualityTools\src\top\pom.xml Reason: Error during page generation org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: Exit code: 1 - S:\src\Exploratory Prototypes\CodeQualityTools\src\top\top-module1\src\test\java\codequality\top\module1\TestClassInModule1.java:3: package org.testng does not exist import org.testng.Assert; ^ S:\src\Exploratory Prototypes\CodeQualityTools\src\top\top-module1\src\test\java\codequality\top\module1\TestClassInModule1.java:4: package org.testng.annotations does not exist import org.testng.annotations.Test; ^ ... java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc at com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46) at com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:811) ... Greets Wolfgang Brett Porter wrote: I think you need to set source instead. If that doesn't work, please describe what the crash looks like. Cheers, Brett 2008/8/25 WolfgangRoessler [EMAIL PROTECTED]: I set the javadocVersion, but the plugin still crashes. - Wolfgang Brett Porter wrote: Do you need to configure it to use Java's 1.5 source level? - Brett 2008/8/25 WolfgangRoessler [EMAIL PROTECTED]: Hello, I have configured the maven-javadoc-plugin in the reporting section. Unfortunately when generating the report, the plugin crashes. The exceptions look like it has problems with the @Test annotation of TestNG. Any ideas or solutions what happens? Greets Wolfgang Roessler -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19139379.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19140451.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19151139.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 usage
Yes, run: mvn -f child/pom.xml install or similar. Cheers, Brett 2008/8/25 Saket Lakshminarayan Chiluveru [EMAIL PROTECTED]: Hi, I have a Parent Project, and it has a child Project. The Parent is of type 'pom' and it aggregates the child. In order to run mvn install, I need to be either inside the parent or the child projects. Is it possible to selectively execute child goals/phases, from the parent directory ? Regards, Saket CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS*** -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I override a plugin dependency?
sounds right if the group/artifact IDs match up. Maybe this is a bug? - Brett 2008/8/23 Graham Leggett [EMAIL PROTECTED]: Hi all, I have a need to override a specific dependency used by the maven-torque-plugin, and I am struggling to convince maven v2.0.9 to do this. The symptoms are that the original jar is being used, instead of the overridden jar, which is effectively ignored. To test this, I have deleted the original jar completely from my local maven repository, and what I expect to happen is that maven should not try to download this dependency again, because it has been overridden. In practise, maven downloads the original jar, and ignores the overridden jar. Is there anything obvious that I have missed in this process? My plugin definition looks like this: plugin groupIdorg.apache.torque/groupId artifactIdtorque-maven-plugin/artifactId version3.3/version dependencies dependency groupIdorg.apache.derby/groupId artifactIdderby/artifactId version10.4.1.3/version /dependency dependency groupIdorg.apache.torque/groupId artifactIdtorque-templates/artifactId version3.3.1/version /dependency /dependencies /plugin Regards, Graham -- -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Transitive dependencies in multi-module projects
Hi, My application is divided into several transitively dependent projects. Here's a simplified example: libA.jar libB.jar depends on libA.jar libC.jar depends on libB.jar appA.jar depends on libC.jar appB.jar depends on libC.jar Each of these JARs is in its own POM, which specifies the dependencies stated above. I'm actively developing all of these projects simultaneously, so I want Maven to compile the source code of any dependency that's out-of-date (just like Ant's javac task). For example, if I'm testing appA, and I change something in libB, I should only have to run mvn compile on the appA project, since Maven knows that appA depends transitively on libB. Unfortunately, this doesn't happen. I have to manually figure out which dependent project is out of date, compile it, and then compile appA. Needless to say, this is tedious and time-consuming. I've been reading that modules are the solution to this problem. There's a write-up about them here: http://docs.codehaus.org/display/MAVENUSER/Multi-modules+projects However, the solution in the write-up doesn't seem like it would work, at least not in my situation. It says I have to specify libC's parent module, but which parent do I choose? As you can see above, it has two parents: appA and appB. How can I reconcile this? Thanks, Trevor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Questions
Thanks so much! That was extremely helpful. Brett Porter wrote: -- View this message in context: http://www.nabble.com/Maven-Questions-tp19150963p19153453.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: Transitive dependencies in multi-module projects
On Mon, Aug 25, 2008 at 4:15 PM, Trevor Harmon [EMAIL PROTECTED] wrote: I've been reading that modules are the solution to this problem. There's a write-up about them here: http://docs.codehaus.org/display/MAVENUSER/Multi-modules+projects However, the solution in the write-up doesn't seem like it would work, at least not in my situation. It says I have to specify libC's parent module, but which parent do I choose? As you can see above, it has two parents: appA and appB. How can I reconcile this? Thanks, In your example, appA and appB are not parents of libC... they simply have a dependency on it. If you establish a parent pom, and list all five of your projects as modules, Maven will figure out what order to build them in, and compile the changed sources. (It might not be quite as efficient as Ant, for example I think if you run 'mvn install' it will still package up and install the jar, even if nothing needed to be compiled. YMMV.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to cope with conflicting jar versions
Thanks Brett, Can you please share any links or hints or how to use the new dependencyManagement feature introduced in maven 2.0.9. Brett Porter wrote: in most recent versions of Maven, dependencyManagement can be used to enforce a particular version throughout the entire tree. You can also use the enforcer plugin to ensure this has been properly applied. Cheers, Brett 2008/8/26 Farrukh Najmi [EMAIL PROTECTED]: In my project there are many direct and indirect dependencies at the lowest level on springframework jars. One such dependency requires use of the most recent springframework jars. Migrating to latest version of spring is my projects direct dependency causes problems at runtime with other dependencies which expect older versions of apis from spring and its dependencies. Is there a good way to deal with this dependency hell? If so I would appreciate any advice. Thanks. -- View this message in context: http://www.nabble.com/How-to-cope-with-conflicting-jar-versions-tp19150279p19153947.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: How to cope with conflicting jar versions
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html 2008/8/26 Farrukh Najmi [EMAIL PROTECTED]: Thanks Brett, Can you please share any links or hints or how to use the new dependencyManagement feature introduced in maven 2.0.9. Brett Porter wrote: in most recent versions of Maven, dependencyManagement can be used to enforce a particular version throughout the entire tree. You can also use the enforcer plugin to ensure this has been properly applied. Cheers, Brett 2008/8/26 Farrukh Najmi [EMAIL PROTECTED]: In my project there are many direct and indirect dependencies at the lowest level on springframework jars. One such dependency requires use of the most recent springframework jars. Migrating to latest version of spring is my projects direct dependency causes problems at runtime with other dependencies which expect older versions of apis from spring and its dependencies. Is there a good way to deal with this dependency hell? If so I would appreciate any advice. Thanks. -- View this message in context: http://www.nabble.com/How-to-cope-with-conflicting-jar-versions-tp19150279p19153947.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] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to cope with conflicting jar versions
On Mon, Aug 25, 2008 at 3:40 PM, Farrukh Najmi [EMAIL PROTECTED] wrote: In my project there are many direct and indirect dependencies at the lowest level on springframework jars. One such dependency requires use of the most recent springframework jars. Migrating to latest version of spring is my projects direct dependency causes problems at runtime with other dependencies which expect older versions of apis from spring and its dependencies. Is there a good way to deal with this dependency hell? If so I would appreciate any advice. Thanks. Generally, if a project closer to the root pom (fewer number of transitive dependencies away) calls for a version of the same dependency (same group id, artifact id) as a dependency farther away (greater number of transitive dependency hops), the former will be used to the exclusion of the latter, as I understand it. I find this solves the vast majority of the problems right there. A secondary mechanism is dependency management, where you can lock in versions of dependencies using the POM. I find this primarily useful at not requiring versions to be specified in sub-projects with a master POM. Finally, when you have issues where an artifact has been moved/renamed you may need to get into exclusions. - Geoffrey -- Geoffrey Wiseman
Re: How to cope with conflicting jar versions
thirdly version ranges give you deterministic and manageable conflicts. however in the case of spring you should not be mixing the different major revisions that will just give you headaches... use one or the other 1.2.X not compatible with 2.0.X not compatible with 2.5.X, i use version ranges to ensure that no projects cross pollinate... if they do one has to go up or the other down to get a deterministic result. On Tue, 26 Aug 2008 16:06:51 Geoffrey Wiseman wrote: On Mon, Aug 25, 2008 at 3:40 PM, Farrukh Najmi [EMAIL PROTECTED] wrote: In my project there are many direct and indirect dependencies at the lowest level on springframework jars. One such dependency requires use of the most recent springframework jars. Migrating to latest version of spring is my projects direct dependency causes problems at runtime with other dependencies which expect older versions of apis from spring and its dependencies. Is there a good way to deal with this dependency hell? If so I would appreciate any advice. Thanks. Generally, if a project closer to the root pom (fewer number of transitive dependencies away) calls for a version of the same dependency (same group id, artifact id) as a dependency farther away (greater number of transitive dependency hops), the former will be used to the exclusion of the latter, as I understand it. I find this solves the vast majority of the problems right there. A secondary mechanism is dependency management, where you can lock in versions of dependencies using the POM. I find this primarily useful at not requiring versions to be specified in sub-projects with a master POM. Finally, when you have issues where an artifact has been moved/renamed you may need to get into exclusions. - Geoffrey -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 usage
Thanks...works -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 26, 2008 3:40 AM To: Maven Users List Subject: Re: Maven2 usage Yes, run: mvn -f child/pom.xml install or similar. Cheers, Brett 2008/8/25 Saket Lakshminarayan Chiluveru [EMAIL PROTECTED]: Hi, I have a Parent Project, and it has a child Project. The Parent is of type 'pom' and it aggregates the child. In order to run mvn install, I need to be either inside the parent or the child projects. Is it possible to selectively execute child goals/phases, from the parent directory ? Regards, Saket CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS*** -- Brett Porter Blog: http://blogs.exist.com/bporter/ - 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]
