[ANN] Maven Dependency Plugin 2.6 Released
The Apache Maven team is pleased to announce the release of the Maven Dependency Plugin, version 2.6 The dependency plugin provides the capability to manipulate artifacts. It can copy and/or unpack artifacts from local or remote repositories to a specified location. http://maven.apache.org/plugins/maven-dependency-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.6/version /plugin Release Notes - Maven Dependency Plugin - Version 2.6 ** Bug * [MDEP-122] - Analyze target does not work correctly when only using a constant defined in a different module * [MDEP-124] - Dependency incorrectly reported as Unused declared * [MDEP-176] - excludes not considered in analyze? * [MDEP-205] - type configuration ignored in sources goal * [MDEP-253] - Purge does not purge released artifacts * [MDEP-256] - invoking purge-local-repository leads to deletion of %JDK_HOME%/lib/tools.jar * [MDEP-272] - purge-local-repository does nothing if certain dependencies are included * [MDEP-298] - mvn dependency:sources lists parameters 'classifier' and 'type', but manually overrides them * [MDEP-300] - Unpacking artifacts should be based on type, with fallback on file-extension * [MDEP-328] - scriptableOutput/scriptableFlag have no effect * [MDEP-353] - Unit tests fail on Windows * [MDEP-366] - NPE when running site * [MDEP-371] - useJvmChmod true by default * [MDEP-376] - -Dexcludes filtering not working anymore * [MDEP-383] - Update purge-local-repository to work in Maven 3 * [MDEP-388] - NPE in analyze-report ** Improvement * [MDEP-173] - Support 'includes' in purge-local-repository * [MDEP-246] - purge-local-repository inclusions * [MDEP-285] - Document abstract method org.apache.maven.plugin.dependency.AbstractDependencyFilterMojo.getMarkedArtifactFilter() * [MDEP-287] - Make maven-dependency-plugin @threadSafe * [MDEP-343] - Add skip parameter for copy-dependencies * [MDEP-360] - Allow using folder as dependency:get destination parameter * [MDEP-377] - use last plexus-utils 3.0.7 which is faster on copying files. * [MDEP-384] - build-classpath should be able to use the artifact's baseVersion * [MDEP-385] - Default fuzziness level should be version instead of file * [MDEP-386] - Split purge-local-repository into manual and transitive ** New Feature * [MDEP-210] - Support includes/excludes configuration in analyze * [MDEP-380] - copy-dependencies should be able to use the artifact's baseVersion * [MDEP-381] - Unpack an artifact from commandline Enjoy, -The Apache Maven team
Apache Maven has its Google+ Page
Hi all, I created a Google+ page for maven. Sadly we cannot yet share the ability to manage it and to post content. As soon as it will be possible I'll give the access to PMCs and probably dev members. For now ping me if you want that we publish something. On my side I'll try to forward announcements and things like that. https://plus.google.com/u/0/b/114843822427522708527/ Cheers, Arnaud
Re: Settings.xml : Maven repositories releases, updatePolicy = utility
The update policy for releases isn't use to define when metadata are updated when you use a range for example ? On Friday, January 1, 2010, Brian Fox bri...@infinity.nu wrote: It should be ignored, it stems from the fact that both fields use the same modello object internally. On Tue, Dec 29, 2009 at 5:18 AM, fabrice.mercier1 beufm...@yahoo.fr wrote: hi I am wonder me the utility of the updatePolicy rule for releases repositories. I set i to always for snapshots repository but in my opinion updatePolicy for releases repo is not needed. Except if Maven works like nexus with a request cache ? Fabrice - http://old.nabble.com/file/u1297858/ft.gif Architect Almerys, activité santé d'Orange Business Services, TOULOUSE http://www.orange-business.com http://www.orange-business.com -- View this message in context: http://old.nabble.com/Settings.xml-%3A-Maven-repositories-releases%2C-updatePolicy-%3D%3E-utility-tp26952952p26952952.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 2: How can I avoid hard-coding the version multiple times?
Not in Maven 2.X Will be possible in Maven 3.x But personally I don't see the problem to have them if you use the release plugin and if required the versions plugin to update them. Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Nov 30, 2009 at 4:27 PM, laredotornado laredotorn...@gmail.comwrote: Hi, I'm using Maven 2.2. In my maven project, I have this fragment in my pom.xml at the project root ... nameMyco GA Capitol Tours/name descriptionMyco GA Capitol Tours/description inceptionYear2009/inceptionYear groupIdMyco.galc.capitol.tours/groupId artifactIdMyco-galc-capitol-tours/artifactId version1.0-SNAPSHOT/version packagingpom/packaging Then I have a webapp sub-folder and I have this in the webapp/pom.xml ... parent groupIdMyco.galc.capitol.tours/groupId artifactIdMyco-galc-capitol-tours/artifactId version1.0-SNAPSHOT/version /parent nameMyco GA Capitol Tours Webapp/name descriptionMyco GA Capitol Tours Webapp/description artifactIdMyco-galc-capitol-tours-webapp/artifactId version1.0-SNAPSHOT/version packagingwar/packaging You'll notice I have 1.0-SNAPSHOT hard-coded a couple of times in my webapp/pom.xml. Is there any way I can replace that with something that will be automatically inherited from the parent? Thanks, - Dave -- View this message in context: http://old.nabble.com/Maven-2%3A--How-can-I-avoid-hard-coding-the-version-multiple-times--tp26576290p26576290.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 2: How can I avoid hard-coding the version multiple times?
Yes you just put it in the parent part. The module doesn't need to redefine it. You inherit it from the parent. Each pom need to have the version at least one version defined in project/parent/version or in project/version Cheers, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Nov 30, 2009 at 11:06 PM, Baptiste MATHUS m...@batmat.net wrote: Err, this is exactly what we do. I might be wrong, but the only thing that's compulsory is the version of the referenced parent pom. If the child project has the same version (or the same groupId) you can just remove it from the child pom. This is what we have been doing for something like 6 or seven releases of a multimodules project (20+ modules) with same version for the whole tree without any problem, but I have might have missed something. Cheers. 2009/11/30 Arnaud HERITIER aherit...@gmail.com Not in Maven 2.X Will be possible in Maven 3.x But personally I don't see the problem to have them if you use the release plugin and if required the versions plugin to update them. Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Nov 30, 2009 at 4:27 PM, laredotornado laredotorn...@gmail.com wrote: Hi, I'm using Maven 2.2. In my maven project, I have this fragment in my pom.xml at the project root ... nameMyco GA Capitol Tours/name descriptionMyco GA Capitol Tours/description inceptionYear2009/inceptionYear groupIdMyco.galc.capitol.tours/groupId artifactIdMyco-galc-capitol-tours/artifactId version1.0-SNAPSHOT/version packagingpom/packaging Then I have a webapp sub-folder and I have this in the webapp/pom.xml ... parent groupIdMyco.galc.capitol.tours/groupId artifactIdMyco-galc-capitol-tours/artifactId version1.0-SNAPSHOT/version /parent nameMyco GA Capitol Tours Webapp/name descriptionMyco GA Capitol Tours Webapp/description artifactIdMyco-galc-capitol-tours-webapp/artifactId version1.0-SNAPSHOT/version packagingwar/packaging You'll notice I have 1.0-SNAPSHOT hard-coded a couple of times in my webapp/pom.xml. Is there any way I can replace that with something that will be automatically inherited from the parent? Thanks, - Dave -- View this message in context: http://old.nabble.com/Maven-2%3A--How-can-I-avoid-hard-coding-the-version-multiple-times--tp26576290p26576290.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
[ANN] [FR] Apache Maven, enfin un livre en Français
Hi community, This mail is to announce the availability of a new book about Maven, but in French this time ! Thus let's talk in French, non-french readers can mute this thread :-) Bonjour à tous, Petit mail pour vous prévenir de la disponibilité d'un nouvel ouvrage en Français sur votre produit préféré : Maven. Il s'agit d'un ouvrage original qui a pour but de vous livrer un concentré d'expérience autour de cet outil que Nicolas De loof et moi-même avons acquis en plus de 6 ans de pratique. Nous avons essayé d'être inventif en créant un nouveau style littéraire : Le roman informatique. On vous laisse découvrir tout cela en espérant que vous y appreniez beaucoup de choses et que les 300 pages de Français vous seront plus accessibles. La préface est rédigée par Jason Van Zyl (pas la peine que je vous rappelle de qui il s'agit ?? ;-) ) Plus de détails et actualités sur cet ouvrage sur mon blog ( http://blog.aheritier.net/apache-maven-enfin-un-livre-en-francais/), celui de Nicolas (http://blog.loof.fr/) et sur le site de l'éditeur ( http://www.pearson.fr/livre/?GCOI=27440100730370). Cordialement, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net
[ANN] Signature of Apple Java 1.6 Runtime for use with Animal Sniffer released
Hi all, I just released the signature of Apple Java 1.6 Runtime for use with Animal Sniffer released. You'll find documentation about Animal Sniffer here : http://mojo.codehaus.org/animal-sniffer/ Apple Java 1.6 Signature doc is here : http://mojo.codehaus.org/signatures/java16-apple/ Cheers, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net
Re: maven-eclipse-plugin configuration for pom packaging
The plugin doesn't support it. I think there's a an issue already opened about that. You can vote for it. It is supported by m2eclipse or Q4E. Cheers, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Thu, Nov 5, 2009 at 5:39 PM, james.w.jackson james.w.jack...@baesystems.com wrote: I'm using maven 2.2.1 and maven-eclipse-plugin 2.7 with a multi-module project. When I run 'mvn eclipse:eclipse' in the multi-module project, it doesn't generate .project eclipse files for the projects that are marked as packagingpom/packaging. How can I configure the plugin to generate .project files for projects that have the pom packaging? Thanks, Jim -- View this message in context: http://old.nabble.com/maven-eclipse-plugin-configuration-for-pom-packaging-tp26215800p26215800.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Source Plugin 2.1.1 Released
Hi, The Maven team is pleased to announce the release of the Maven Source Plugin, version 2.1.1 The Source Plugin creates a jar archive of the source files of the current project. http://maven.apache.org/plugins/maven-source-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-source-plugin/artifactId version2.1.1/version /plugin Release Notes - Maven 2.x Souce Plugin - Version 2.1.1 ** Bugs fixed : * [MSOURCES-44] - If project doesn't contain sources (contains only test sources) source:jar will fail * [MSOURCES-47] - test-jar goal fails if no source files exist Enjoy, -The Maven team # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net
Re: Slow maven compile after upgrading JDK from 1.5 to 1.6
Yes I don't understand how we can find such a problem which isn't yet fix by SUN :-( Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Mon, Oct 12, 2009 at 1:02 PM, j_ri jochen.riedlin...@l-bank.de wrote: It's really sad that SUN hasn't fixed this yet;-( I wonder that there are not more people are affected by this issue. Actually everybody who uses build tools like Maven should have slower compile times. Our workaround is, that our build isn't generating the class-path entry in the manifest any more. But this workaround only works for jars that get deployed to our application server within a EAR file. Arnaud HERITIER wrote: We are facing the same issue actually ( https://jira.jboss.org/jira/browse/GTNPORTAL-27) and several months after the issues was reported to SUN it is not yet fixed in JDK :-( Please vote for it : http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6843751 Nobody found a workaround ? Arnaud On Mon, May 25, 2009 at 11:38 AM, j_ri jochen.riedlin...@l-bank.de wrote: Hi, meanwhile I posted in the Sun Developer Network, since my tests lead to the conclusion that the problem occures because of a bug in the javac compiler of Java 6. see http://forums.sun.com/thread.jspa?threadID=5386732tstart=0 http://forums.sun.com/thread.jspa?threadID=5386732tstart=0 and http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6843751 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6843751 but what I wonder about is that nobody else who compiles quite large prohjects using maven has the same problems as we do. another question I have is the follwing: why does maven put all transitive dependencies in the compile classpath? it is best practise to have all jars I really depend on for my compilation as direct dependency in my pom. why don't force this and just put the direct dependencies in the compile classpath and pass the transitive ones only to the other tasks (packaging, etc.)? -- View this message in context: http://n2.nabble.com/Slow-maven-compile-after-upgrading-JDK-from-1.5-to-1.6-tp2868702p2968777.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://n2.nabble.com/Slow-maven-compile-after-upgrading-JDK-from-1-5-to-1-6-tp2868702p3807303.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release a version
It isn't possible actually.We do that to enforce our users to have SNAPSHOTs version in their SVN Arnaud On Tue, Oct 6, 2009 at 11:50 PM, Rémy remy.tempora...@gmail.com wrote: Hello, The maven-release-plugin works like that : * Check that there are no uncommitted changes in the sources * Check that there are no SNAPSHOT dependencies * Change the version in the poms from x-SNAPSHOT to a new version (you will be prompted for the versions to use) * Transform the SCM information in the POM to include the final destination of the tag * Run the project tests against the modified POMs to confirm everything is in working order * Commit the modified POMs * Tag the code in the SCM with a version name (this will be prompted for) * Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for) * Commit the modified POMs http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html Is it possible to run everything except the last two points. I don't want to initialize the snapshots of all projects for the next version. Thanks. Rémy -- View this message in context: http://www.nabble.com/Release-a-version-tp25777117p25777117.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] New book - Apache Maven 2: Effective Implementation
And where is the problem ? Even if the book isn't free, it is always a good thing for our community and its users... Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Wed, Sep 23, 2009 at 3:40 PM, Peter Horlock peter.horl...@googlemail.com wrote: Is there any open source version like from The Definitive Guide? I doesn't seem like it. So in otherwords, your post is plain propaganda for you, packtpub and amazon. Peter
Re: [ANN] New book - Apache Maven 2: Effective Implementation
The chapter 6 is available on the web site. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Wed, Sep 23, 2009 at 4:03 PM, Quintin Beukes quin...@skywalk.co.zawrote: Have a sample chapter available? Quintin Beukes On Tue, Sep 22, 2009 at 2:50 PM, Brett Porter br...@apache.org wrote: The final release of Apache Maven 2: Effective Implementation is now available online! It is available in both eBook and printed + eBook versions, and is written by Deng Ching and myself with help from our reviewers Wendy Smoak, Emmanuel Venisse, and Carsten Ziegler. http://www.packtpub.com/apache-maven-2-effective-implementations/book http://www.amazon.com/Apache-Maven-2-Effective-Implementation/dp/1847194540/ In this book, we wanted to focus on “best practices” and tying everything together in a way that shows how Maven was meant to be used. It works through a reasonably useful example application from scratch, up to an assembly, building it in CI, deploying it to the repository, and releasing it. The book includes: Chapter 1: Maven in a Nutshell Chapter 2: Staying in Control with Archiva Chapter 3: Building an Application Using Maven Chapter 4: Application Testing with Maven Chapter 5: Reporting and Checks Chapter 6: Useful Maven Plugins Chapter 7: Maven Best Practices Chapter 8: Continuum: Ensuring the Health of your Source Code Chapter 9: Continuum in Depth Chapter 10: Archiva in a Team Chapter 11: Archetypes Chapter 12: Maven, Archiva, and Continuum in the Enterprise Appendix A: Troubleshooting Maven Appendix B: Recent Maven Features Appendix C: Migrating Archiva and Continuum Data Full contents: http://www.packtpub.com/article/apache-maven-2-effective-implementations-table-of-contents Chapter 6: Useful Maven Plugins is available now as a sample from the book site. Cheers, Brett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: (maven.)apache.org down
Yes it's is down :http://monitoring.apache.org/status/ On Fri, Aug 28, 2009 at 11:28 AM, Juven Xu ju...@sonatype.com wrote: hmm... I got this: *.apache.org is currently offline. No ETA for resumption of services is available. On Fri, Aug 28, 2009 at 5:24 PM, Stevo Slavić ssla...@gmail.com wrote: Hello maven users, Is (maven.)apache.org down or is it just my network connectivity? Regards, Stevo. -- - juven
Re: RE : [Versions Maven Plugin 1.0] FATAL Error thrown for versions:dependency-updates-report GOAL
They are here : http://repo1.maven.org/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.2/ I published them few days before the release of versions plugin Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Tue, Aug 25, 2009 at 2:02 PM, HARDION Vincent vincent.hard...@synchrotron-soleil.fr wrote: Hi, It seems the new version need also org.apache.maven.shared:maven-common-artifact-filters:jar:1.2 but only version 1.1 is accessible from central. Best regards, Vincent Hardion -Message d'origine- De : Arnaud HERITIER [mailto:aherit...@gmail.com] Envoyé : lundi 24 août 2009 10:37 À : Maven Users List Cc : u...@mojo.codehaus.org Objet : Re: [Versions Maven Plugin 1.0] FATAL Error thrown for versions:dependency-updates-report GOAL it seems to be a doxia incompabilityWe have to verify it. Can you open an issue here please : http://jira.codehaus.org/browse/MVERSIONS If you can also give us the result of mvn help:effective-pom in your module MBS - utilities. You can remove all private information if needed. NOTE : this plugin isn't maintain by the maven team thus I recommend that you contact the mojo team on u...@mojo.codehaus.org Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Mon, Aug 24, 2009 at 10:25 AM, subir.sasiku...@wipro.com wrote: Hi, I tried to use this plugin to check the dependency version updates I might need for the project. I use Maven 2.1.0, on WinXP professional, and JDK 1.6.0 I got the following exceptions: E:\maven-work\main\bsmmvn versions:dependency-updates-report [WARNING] Not decrypting password for server 'repo.mobiletv.org-releases' due to exception in security handler. Ensure that you have configured your master password file (and relocation if app ropriate) See the installation instructions for details. Cause: C:\Documents and Settings\subirs.W\.m2\settings-security.xml (The sys tem cannot find the file specified) [WARNING] Not decrypting password for server 'repo.mobiletv.org-snapshots' due t o exception in security handler. Ensure that you have configured your master password file (and relocation if app ropriate) See the installation instructions for details. Cause: C:\Documents and Settings\subirs.W\.m2\settings-security.xml (The sys tem cannot find the file specified) [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] MBS - utilities [INFO] BSM - model [INFO] BSM - GUI Web Application Module [INFO] BSM - WSI Web Application Module [INFO] BSM - Welcome Web Application Module [INFO] BSM - Root [INFO] Searching repository for plugin with prefix: 'versions'. [INFO] [INFO] Building MBS - utilities [INFO]task-segment: [versions:dependency-updates-report] [INFO] Downloading: http://10.150.137.44:8080/artifactory/repo/org/hibernate/hibernate- core/3.3.2.GA/hibernate-core-3.3.2.GA.pom [INFO] Unable to find resource 'org.hibernate:hibernate-core:pom:3.3.2.GA' in re pository central (http://10.150.137.44:8080/artifactory/repo) Downloading: http://10.150.137.44:8080/artifactory/repo/org/hibernate/hibernate- core/3.3.2.GA/hibernate-core-3.3.2.GA.jar 2255K downloaded (hibernate-core-3.3.2.GA.jar) [INFO] [versions:dependency-updates-report] [INFO] artifact axis:axis-wsdl4j: checking for updates from central [INFO] artifact c3p0:c3p0: checking for updates from central [INFO] artifact c3p0:c3p0-oracle-thin-extras: checking for updates from central [INFO] artifact com.oracle:ojdbc14: checking for updates from central [INFO] artifact commons-discovery:commons-discovery: checking for updates from c entral [INFO] artifact commons-fileupload:commons-fileupload: checking for updates from central [INFO] artifact commons-io:commons-io: checking for updates from central [INFO] artifact commons-lang:commons-lang: checking for updates from central [INFO] artifact commons-logging:commons-logging: checking for updates from centr al [INFO] artifact javax.activation:activation: checking for updates from central [INFO] artifact javax.mail:mail: checking for updates from central [INFO] artifact javax.servlet:jsp-api: checking for updates from central [INFO] artifact javax.servlet:jstl: checking for updates from central [INFO] artifact javax.servlet:servlet-api: checking for updates from central [INFO] artifact json_simple:json_simple: checking for updates from central [INFO] artifact log4j:log4j: checking for updates from central [INFO] artifact net.sf.mime-util:mime-util: checking for updates from central [INFO] artifact
Re: [Versions Maven Plugin 1.0] FATAL Error thrown for versions:dependency-updates-report GOAL
it seems to be a doxia incompabilityWe have to verify it. Can you open an issue here please : http://jira.codehaus.org/browse/MVERSIONS If you can also give us the result of mvn help:effective-pom in your module MBS - utilities. You can remove all private information if needed. NOTE : this plugin isn't maintain by the maven team thus I recommend that you contact the mojo team on u...@mojo.codehaus.org Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Mon, Aug 24, 2009 at 10:25 AM, subir.sasiku...@wipro.com wrote: Hi, I tried to use this plugin to check the dependency version updates I might need for the project. I use Maven 2.1.0, on WinXP professional, and JDK 1.6.0 I got the following exceptions: E:\maven-work\main\bsmmvn versions:dependency-updates-report [WARNING] Not decrypting password for server 'repo.mobiletv.org-releases' due to exception in security handler. Ensure that you have configured your master password file (and relocation if app ropriate) See the installation instructions for details. Cause: C:\Documents and Settings\subirs.W\.m2\settings-security.xml (The sys tem cannot find the file specified) [WARNING] Not decrypting password for server 'repo.mobiletv.org-snapshots' due t o exception in security handler. Ensure that you have configured your master password file (and relocation if app ropriate) See the installation instructions for details. Cause: C:\Documents and Settings\subirs.W\.m2\settings-security.xml (The sys tem cannot find the file specified) [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] MBS - utilities [INFO] BSM - model [INFO] BSM - GUI Web Application Module [INFO] BSM - WSI Web Application Module [INFO] BSM - Welcome Web Application Module [INFO] BSM - Root [INFO] Searching repository for plugin with prefix: 'versions'. [INFO] [INFO] Building MBS - utilities [INFO]task-segment: [versions:dependency-updates-report] [INFO] Downloading: http://10.150.137.44:8080/artifactory/repo/org/hibernate/hibernate- core/3.3.2.GA/hibernate-core-3.3.2.GA.pom [INFO] Unable to find resource 'org.hibernate:hibernate-core:pom:3.3.2.GA' in re pository central (http://10.150.137.44:8080/artifactory/repo) Downloading: http://10.150.137.44:8080/artifactory/repo/org/hibernate/hibernate- core/3.3.2.GA/hibernate-core-3.3.2.GA.jar 2255K downloaded (hibernate-core-3.3.2.GA.jar) [INFO] [versions:dependency-updates-report] [INFO] artifact axis:axis-wsdl4j: checking for updates from central [INFO] artifact c3p0:c3p0: checking for updates from central [INFO] artifact c3p0:c3p0-oracle-thin-extras: checking for updates from central [INFO] artifact com.oracle:ojdbc14: checking for updates from central [INFO] artifact commons-discovery:commons-discovery: checking for updates from c entral [INFO] artifact commons-fileupload:commons-fileupload: checking for updates from central [INFO] artifact commons-io:commons-io: checking for updates from central [INFO] artifact commons-lang:commons-lang: checking for updates from central [INFO] artifact commons-logging:commons-logging: checking for updates from centr al [INFO] artifact javax.activation:activation: checking for updates from central [INFO] artifact javax.mail:mail: checking for updates from central [INFO] artifact javax.servlet:jsp-api: checking for updates from central [INFO] artifact javax.servlet:jstl: checking for updates from central [INFO] artifact javax.servlet:servlet-api: checking for updates from central [INFO] artifact json_simple:json_simple: checking for updates from central [INFO] artifact log4j:log4j: checking for updates from central [INFO] artifact net.sf.mime-util:mime-util: checking for updates from central [INFO] artifact net.sourceforge.stripes:stripes: checking for updates from centr al [INFO] artifact org.apache.ant:ant: checking for updates from central [INFO] artifact org.apache.axis:axis: checking for updates from central [INFO] artifact org.apache.axis:axis-jaxrpc: checking for updates from central [INFO] artifact org.apache.axis:axis-saaj: checking for updates from central [INFO] artifact org.apache.maven:jspc-compiler-tomcat6: checking for updates fro m central [INFO] artifact org.apache.maven:maven-archiver: checking for updates from centr al [INFO] artifact org.apache.maven:maven-artifact: checking for updates from centr al [INFO] artifact org.apache.maven:maven-project: checking for updates from centra l [INFO] artifact org.apache.tomcat:juli: checking for updates from central [INFO] artifact org.apache.tomcat:tribes: checking for updates from central [INFO] artifact org.codehaus.mojo:rpm-maven-plugin: checking for updates from ce ntral [INFO]
Re: [Versions Maven Plugin 1.0] FATAL Error thrown for versions:dependency-updates-report GOAL
A quick workaround can be to use maven 2.2.1 instead of 2.1.02.1.x have many issues. 2.2.1 will give you a better satisfaction On Mon, Aug 24, 2009 at 10:37 AM, Arnaud HERITIER aherit...@gmail.comwrote: it seems to be a doxia incompabilityWe have to verify it. Can you open an issue here please : http://jira.codehaus.org/browse/MVERSIONS If you can also give us the result of mvn help:effective-pom in your module MBS - utilities. You can remove all private information if needed. NOTE : this plugin isn't maintain by the maven team thus I recommend that you contact the mojo team on u...@mojo.codehaus.org Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Mon, Aug 24, 2009 at 10:25 AM, subir.sasiku...@wipro.com wrote: Hi, I tried to use this plugin to check the dependency version updates I might need for the project. I use Maven 2.1.0, on WinXP professional, and JDK 1.6.0 I got the following exceptions: E:\maven-work\main\bsmmvn versions:dependency-updates-report [WARNING] Not decrypting password for server 'repo.mobiletv.org-releases' due to exception in security handler. Ensure that you have configured your master password file (and relocation if app ropriate) See the installation instructions for details. Cause: C:\Documents and Settings\subirs.W\.m2\settings-security.xml (The sys tem cannot find the file specified) [WARNING] Not decrypting password for server 'repo.mobiletv.org-snapshots' due t o exception in security handler. Ensure that you have configured your master password file (and relocation if app ropriate) See the installation instructions for details. Cause: C:\Documents and Settings\subirs.W\.m2\settings-security.xml (The sys tem cannot find the file specified) [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] MBS - utilities [INFO] BSM - model [INFO] BSM - GUI Web Application Module [INFO] BSM - WSI Web Application Module [INFO] BSM - Welcome Web Application Module [INFO] BSM - Root [INFO] Searching repository for plugin with prefix: 'versions'. [INFO] [INFO] Building MBS - utilities [INFO]task-segment: [versions:dependency-updates-report] [INFO] Downloading: http://10.150.137.44:8080/artifactory/repo/org/hibernate/hibernate- core/3.3.2.GA/hibernate-core-3.3.2.GA.pomhttp://10.150.137.44:8080/artifactory/repo/org/hibernate/hibernate-%0Acore/3.3.2.GA/hibernate-core-3.3.2.GA.pom [INFO] Unable to find resource 'org.hibernate:hibernate-core:pom:3.3.2.GA' in re pository central (http://10.150.137.44:8080/artifactory/repo) Downloading: http://10.150.137.44:8080/artifactory/repo/org/hibernate/hibernate- core/3.3.2.GA/hibernate-core-3.3.2.GA.jar 2255Khttp://10.150.137.44:8080/artifactory/repo/org/hibernate/hibernate-%0Acore/3.3.2.GA/hibernate-core-3.3.2.GA.jar%0A2255Kdownloaded (hibernate-core-3.3.2.GA.jar) [INFO] [versions:dependency-updates-report] [INFO] artifact axis:axis-wsdl4j: checking for updates from central [INFO] artifact c3p0:c3p0: checking for updates from central [INFO] artifact c3p0:c3p0-oracle-thin-extras: checking for updates from central [INFO] artifact com.oracle:ojdbc14: checking for updates from central [INFO] artifact commons-discovery:commons-discovery: checking for updates from c entral [INFO] artifact commons-fileupload:commons-fileupload: checking for updates from central [INFO] artifact commons-io:commons-io: checking for updates from central [INFO] artifact commons-lang:commons-lang: checking for updates from central [INFO] artifact commons-logging:commons-logging: checking for updates from centr al [INFO] artifact javax.activation:activation: checking for updates from central [INFO] artifact javax.mail:mail: checking for updates from central [INFO] artifact javax.servlet:jsp-api: checking for updates from central [INFO] artifact javax.servlet:jstl: checking for updates from central [INFO] artifact javax.servlet:servlet-api: checking for updates from central [INFO] artifact json_simple:json_simple: checking for updates from central [INFO] artifact log4j:log4j: checking for updates from central [INFO] artifact net.sf.mime-util:mime-util: checking for updates from central [INFO] artifact net.sourceforge.stripes:stripes: checking for updates from centr al [INFO] artifact org.apache.ant:ant: checking for updates from central [INFO] artifact org.apache.axis:axis: checking for updates from central [INFO] artifact org.apache.axis:axis-jaxrpc: checking for updates from central [INFO] artifact org.apache.axis:axis-saaj: checking for updates from central [INFO] artifact org.apache.maven:jspc-compiler-tomcat6: checking for updates fro m central [INFO] artifact org.apache.maven:maven-archiver
Re: Can I access timestamp version of SNAPSHOT dependency within a build?
The timestamp is generated when maven deploys the artifact and it doesn't keep this info.I don't think you can do better. Arnaud On Fri, Aug 7, 2009 at 3:08 AM, Stephen Duncan Jr stephen.dun...@gmail.comwrote: On Fri, Jul 31, 2009 at 10:53 AM, Stephen Duncan Jr stephen.dun...@gmail.com wrote: I'm trying to manually build an assembly that aggregates multiple assemblies, to make an installer. So, I depend on the .tar.gz produced from other assemblies, I use the dependency-plugin to unpack those dependencies. While versions are SNAPSHOTs, all of the directories after unpacking have names like artifactId-1.0-SNAPSHOT. I'd like to rename them to match the timestamped version when the dependencies are pulled from the repository. Is there a way to access the timestamped version number from the build? (From there I could use the antrun plugin or the GMaven plugin to do the rename) -- Stephen Duncan Jr www.stephenduncanjr.com For now, I'm using the maven-assembly-plugin to to create a directory assembly with dependencySet. This is the only tool I know of right now that produces the dependency files with the timestamp in the name instead of SNAPSHOT. I'm then looping over the files in the directory produced and extracting out the names and the versions from the name. I'd love to find out a cleaner way of getting this information... -- Stephen Duncan Jr www.stephenduncanjr.com
Re: [Solved] Re: [Maven assembly plugin] Error using the assembly plugin on CentOs4.7
I'm just having the same issue on MacOS after upgrading the assembly plugin from 2.1 to 2.2-beta-4 I think we could consider that it is a regression ? In my case the build hangs and I have to do a CTRL+C to have the error. Googling it I found this thread. Even if it took for me only few minutes to find, it can be very annoying for our users. What could we do ? Arnaud 2009/3/12 Raphaël Piéroni raphaelpier...@gmail.com Hi I solved my problem: I should have not specified directory/directory in the descriptor. I should have removed that line. Sorry for the noise. Thanks Raphaël 2009/3/12 Raphaël Piéroni raphaelpier...@gmail.com: Thanks, Santos Right the command seems OK with adding double-quotes. But : 1. The error comes from Plexus. Caused by: java.io.IOException: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' at org.codehaus.plexus.components.io.attributes.PlexusIoResourceAttributeUtils.executeLs(PlexusIoResourceAttributeUtils.java:238) 2. Plexus is used by the assembly plugin 3. The same plugin using plexus worked fine just in the precedent module of my multi-module build. Should i raise Jira against the assembly plugin ? Regards, Raphaël 2009/3/12 Santos Patel santos.pa...@tcs.com: hi, i think the problem is with the command... /bin/sh -c ls -1nlaR as you have shown only results in the result given by /bin/sh -c ls It doesn't seem to take the ls options in to consideration. the options a -- show all files including ones starting with . R -- follow sub directories recursively. /bin/sh -c ls -1nlaR works fine and shows the results with the file attributes as required. Santosh =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How get current svn revision via maven?
It could do what you want :
http://mojo.codehaus.org/buildnumber-maven-plugin/
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Wed, Jul 29, 2009 at 1:19 PM, Alexander the.malk...@gmail.com wrote:
Hello,
I want Maven to insert current svn revision to my version.properties. Sure
I could manually insert into pom.xml property ${revision} every build. But
Im searching a way to automate it. Any ideas? [?]
Re: [MAVEN - PMD]
The issue is already opened : http://jira.codehaus.org/browse/MPMD-97pmd-jdk14 is used because maven 2.2.0 has to be compatible with Java 1.4 In the meantime you can try to upgrade locally the pmd version used in the plugin with : build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.3/version dependencies dependency groupIdpmd/groupId artifactIdpmd-jdk14/artifactId version4.2.5/version /dependency /dependencies /plugin /plugins /build Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Thu, Jul 16, 2009 at 8:02 AM, javadevd...@googlemail.com javadevd...@googlemail.com wrote: Hi! thanks for that answer... but why does it use pmd-jdk14 and not the pmd-4.2.2.jar ? (i looked for this jar as dependency and so i couldnt find the version...) Is there a plan to adapt the maven-pmd-plugin to 4.2.5? (cause ruleset- exclude patterns doesnt work with the actual plugin... but with pm 4.2.5 ) Or is there another way, to say to the plugin to use pmd version 4.2.5? thanks 2009/7/15 Arnaud HERITIER aherit...@gmail.com: PMD 4.2.2 http://maven.apache.org/plugins/maven-pmd-plugin/dependencies.html Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Wed, Jul 15, 2009 at 3:42 PM, javadevd...@googlemail.com javadevd...@googlemail.com wrote: Hello! Does anybody know which PMD Version is included in the actual Maven-PMD plugin ? I cant find it on the website.. thanks... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [MAVEN - PMD]
It's possible. I don't know. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Thu, Jul 16, 2009 at 12:40 PM, javadevd...@googlemail.com javadevd...@googlemail.com wrote: he, thanks, again for the answer.. but ... ...my real problem is, that the behavior of the maven plugin using dependency to pmd-jdk14(4.2.5), is another than pmd version 4.2.5 applied from console! Im have my own ruleset configuration with an exlude pattern. This exclude-pattern is correctly used from pmd, but ignored when I start from maven-pmd-plugin... Is this a bug? thanks 2009/7/16 Arnaud HERITIER aherit...@gmail.com: The issue is already opened : http://jira.codehaus.org/browse/MPMD-97pmd-jdk14 is used because maven 2.2.0 has to be compatible with Java 1.4 In the meantime you can try to upgrade locally the pmd version used in the plugin with : build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.3/version dependencies dependency groupIdpmd/groupId artifactIdpmd-jdk14/artifactId version4.2.5/version /dependency /dependencies /plugin /plugins /build Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Thu, Jul 16, 2009 at 8:02 AM, javadevd...@googlemail.com javadevd...@googlemail.com wrote: Hi! thanks for that answer... but why does it use pmd-jdk14 and not the pmd-4.2.2.jar ? (i looked for this jar as dependency and so i couldnt find the version...) Is there a plan to adapt the maven-pmd-plugin to 4.2.5? (cause ruleset- exclude patterns doesnt work with the actual plugin... but with pm 4.2.5 ) Or is there another way, to say to the plugin to use pmd version 4.2.5? thanks 2009/7/15 Arnaud HERITIER aherit...@gmail.com: PMD 4.2.2 http://maven.apache.org/plugins/maven-pmd-plugin/dependencies.html Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Wed, Jul 15, 2009 at 3:42 PM, javadevd...@googlemail.com javadevd...@googlemail.com wrote: Hello! Does anybody know which PMD Version is included in the actual Maven-PMD plugin ? I cant find it on the website.. thanks... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [MAVEN - PMD]
yes and there is no patch :-( On Thu, Jul 16, 2009 at 1:48 PM, javadevd...@googlemail.com javadevd...@googlemail.com wrote: it's a bug for one year now... :-( http://jira.codehaus.org/browse/MPMD-84 2009/7/16 Arnaud HERITIER aherit...@gmail.com: It's possible. I don't know. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Thu, Jul 16, 2009 at 12:40 PM, javadevd...@googlemail.com javadevd...@googlemail.com wrote: he, thanks, again for the answer.. but ... ...my real problem is, that the behavior of the maven plugin using dependency to pmd-jdk14(4.2.5), is another than pmd version 4.2.5 applied from console! Im have my own ruleset configuration with an exlude pattern. This exclude-pattern is correctly used from pmd, but ignored when I start from maven-pmd-plugin... Is this a bug? thanks 2009/7/16 Arnaud HERITIER aherit...@gmail.com: The issue is already opened : http://jira.codehaus.org/browse/MPMD-97pmd-jdk14 is used because maven 2.2.0 has to be compatible with Java 1.4 In the meantime you can try to upgrade locally the pmd version used in the plugin with : build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId version2.3/version dependencies dependency groupIdpmd/groupId artifactIdpmd-jdk14/artifactId version4.2.5/version /dependency /dependencies /plugin /plugins /build Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Thu, Jul 16, 2009 at 8:02 AM, javadevd...@googlemail.com javadevd...@googlemail.com wrote: Hi! thanks for that answer... but why does it use pmd-jdk14 and not the pmd-4.2.2.jar ? (i looked for this jar as dependency and so i couldnt find the version...) Is there a plan to adapt the maven-pmd-plugin to 4.2.5? (cause ruleset- exclude patterns doesnt work with the actual plugin... but with pm 4.2.5 ) Or is there another way, to say to the plugin to use pmd version 4.2.5? thanks 2009/7/15 Arnaud HERITIER aherit...@gmail.com: PMD 4.2.2 http://maven.apache.org/plugins/maven-pmd-plugin/dependencies.html Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Wed, Jul 15, 2009 at 3:42 PM, javadevd...@googlemail.com javadevd...@googlemail.com wrote: Hello! Does anybody know which PMD Version is included in the actual Maven-PMD plugin ? I cant find it on the website.. thanks... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [MAVEN - PMD]
PMD 4.2.2http://maven.apache.org/plugins/maven-pmd-plugin/dependencies.html Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net On Wed, Jul 15, 2009 at 3:42 PM, javadevd...@googlemail.com javadevd...@googlemail.com wrote: Hello! Does anybody know which PMD Version is included in the actual Maven-PMD plugin ? I cant find it on the website.. thanks... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cookbook
On Thu, Jul 9, 2009 at 7:30 AM, Peter Horlock peter.horl...@googlemail.comwrote: The priority for a while has been this book: http://tr.im/rnFW Look for the repo book to get a little thicker over the next month, and then expect the m2eclipse book Why working on the Nexus book? Nexus is soo easy it doesn't need a book! :-) You probably didn't play with security settings ;-) Same counts for m2eclipse - you just install it, and it works. It's more about practices to use maven from an IDE Maven, though, is the basis of it all, and way more complicated, especially if you want to master it. +1 Do the cookbook, now! ;-) Plase? I started a survey, let's see what the comunity thinks! :-) FYI, French readers will have one before the end of the year. Peter
Re: Cookbook
How about a +1 to make then fully-finished :) you want to take the lead ?? :-)
Re: Cookbook
On Wed, Jul 8, 2009 at 3:15 PM, Tim O'Brien tobr...@discursive.com wrote: Don't get me started on the Maven site, I'd like to remain on speaking terms with the Maven Developer's list. I don't believe that the Site plugin produces documentation for a few reasons. I'm currently an advocate of removing any and all pages on the Maven site that are half-finished. +1 Arnaud
Re: [maven-eclipse-plugin]: MECLIPSE-548 requires attention
We asked several times to test the 2.7-SNAPSHOT before the release and we had no feedback about this issue which wasn't solved. Thus I don't know if it impacts so many projects.We'll try to fix it in 2.8, but I don't know in how many weeks/monthes, we'll be able to do it Cheers Cheers, Arnaud # Arnaud Héritier # http://blog.aheritier.net On Tue, Jun 16, 2009 at 8:08 AM, Ben Caradoc-Davies ben.caradoc-dav...@csiro.au wrote: MECLIPSE-548 is a showstopper for many projects that would otherwise use maven-eclipse-plugin. I suspect many projects using the plugin are now pinned to 2.5. This issue is marked as Critical priority, has six votes and four watchers. Can anyone take at look at this issue? If you do not intend to address this issue, or cannot address it at this time, please comment on it to explain the situation. Kind regards, Ben. Original Message Subject: [jira] Commented: (MECLIPSE-548) MECLIPSE-442 should be reverted. Classpath container entries should come before 3rd party jars in .classpath Date: Tue, 16 Jun 2009 01:25:42 +0800 From: Joe Freeman (JIRA) j...@codehaus.org To: Caradoc-Davies, Ben (EM, Kensington) ben.caradoc-dav...@csiro.au [ http://jira.codehaus.org/browse/MECLIPSE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=180352#action_180352 ] Joe Freeman commented on MECLIPSE-548: -- How many votes does this have to have before it makes a release. Version 2.7 just came out and it still has the same incorrect classpath ordering for the JDK/JRE :-( MECLIPSE-442 should be reverted. Classpath container entries should come before 3rd party jars in .classpath Key: MECLIPSE-548 URL: http://jira.codehaus.org/browse/MECLIPSE-548 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path (.classpath) Affects Versions: 2.6 Environment: all Reporter: Joe Freeman Priority: Critical A patch was accepted into maven 2.6 as part of jira MECLIPSE-442 that configures eclipse to compile with a different order than the jre will load with. This patch moved the container classpaths to the end of the classpath in eclipse. This behavior is incorrect. The JRE's jar files should come before any 3rd party libraries on the classpath because those classes will be loaded before any of the 3rd party jars and because the JRE's classes cannot be overridden by classes in a 3rd party jar. I understand why MECLIPSE-442 wanted to reverse the order so they could pick up the properties files. The best way to do this was to create properties files in the indvidual projects if he needed at run time or in the test/resources directory if it was only needed for unit testing. project resources come before everything in eclipse With this patch added to maven 2.6, we have a situation where eclipse tells us we have compiler error when maven command line compilations do not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: update all projects maven version
http://mojo.codehaus.org/versions-maven-plugin/update-child-modules-mojo.htmlYou change the version in the reactor and you call mvn versions:update-child-modules Cheers, Arnaud # Arnaud Héritier # http://blog.aheritier.net On Sat, Jun 13, 2009 at 5:42 PM, EJ Ciramella ecirame...@upromise.comwrote: Is there a way to programattically update all the projects maven version (or jdk or ant or w/e else)? With cruise control, we'd just check out 20 or so projname.config.xml files and just search/replace all the paths to the maven installation directory. I see the CLI bit for hudson, but not sure if this is how I should do it.
Re: [maven-eclipse-plugin] We need your help to test the future 2.7
I just deployed it in the snapshots repo. It's numbered : 2.7-20090529.071922-5Thx for your hard work Barrie. Cheers Arnaud On Fri, May 29, 2009 at 6:05 AM, Barrie Treloar baerr...@gmail.com wrote: On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar baerr...@gmail.com wrote: I went quickly hacking an existing IT test to include the resources definition you provided and some debugging output (as ERROR so I could see it) Great! So src/main/resources is correctly on the resources list. The problem is that the list of directories to parse is a Set and the second addition is returning false to add() but nothing is checking this condition. Now I need to work out how to handle the collision Let me know when there's a new snapshot to try. http://jira.codehaus.org/browse/MECLIPSE-551 has code committed to fix this problem with a suitable IT as well. But I can't create snapshots at work. You might want to pull down the source and build a snapshot yourself. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven-eclipse-plugin] We need your help to test the future 2.7
Hi Ari, Thanks for your feedback. Did you follow this doc to setup your eclipse project : http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html ?? Arnaud On Tue, May 26, 2009 at 2:29 AM, ari.meyer ari.me...@gmail.com wrote: Hi Arnaud, I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and I'm getting the same error when using Wicket: org.apache.wicket.markup.MarkupNotFoundException: Markup not found. Reverting again back to 2.5.1, everything worked properly. Best regards, Ari Arnaud HERITIER wrote: Hi Community, The recent release 2.6 of the maven-eclipse-plugin created many problems for all of those who had/wanted to store non-java files under src/*/java (which is required for wicket, ajdt, and probably others usecases). Even we have many integration tests in this plugin we didn't notice this issue because our testcases allow us to check that generated configuration files aren't evolving and that we are able to import and use a project in eclipse (too heavy to do). To fix this issue we (Barrie to be honest) improved the plugin to allow the usage of includes and excludes. : http://jira.codehaus.org/browse/MECLIPSE-104 The documentation of these feature is here : http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html There are many broken links on the site and I don't know why. I'll investigate later. Others pages are the same in http://maven.apache.org/plugins/maven-eclipse-plugin/ For AJDT project you can have a look at this page : http://maven.apache.org/plugins/maven-eclipse-plugin- 2.7-SNAPSHOT/examples/ajdt-projects.html To test the plugin you have to add in your project or in your settings this repository : https://repository.apache.org/content/repositories/snapshots/ (be careful to the https protocol) The last version I deployed is : 2.7-20090416.000603-3 Please, test it and give us your feedback. If it is positive this week, we'll launch the release process the next one. cheers, -- Arnaud -- View this message in context: http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2972277.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven-eclipse-plugin] We need your help to test the future 2.7
Did you try to use m2eclipse or q4e ?They'll be the future. maven-eclipse-plugin will probably die under its own weight. There are too many use cases and testing coverage isn't conclusive because we only checks what we generate and not that we are able to import/use it in eclipse . We have really few developpers involved in it and the darkness of the eclipse configuration doesn't help. Now many settings are stored in files. I'll try to have a look at MECLIPSE-443 but I cannot say when it will be. I think it sould be better for you to be able to use plugins like m2eclipse or q4e. Arnaud On Tue, May 26, 2009 at 3:33 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: In my opinion MECLIPSE-443 is a very bad idea. Should every plugin be configured so that the resources available in src/main/java are treated as classpath entries? According to me the eclipse plugin should take the resources part of the pom into account, rather than invent yet another way of specifying where resources live. This fix break so many existing builds and archetypes it is not fun anymore. I for one don't like being the helpdesk for maven on the Wicket user list. Martijn On Tue, May 26, 2009 at 9:21 AM, Arnaud HERITIER aherit...@gmail.com wrote: Hi Ari, Thanks for your feedback. Did you follow this doc to setup your eclipse project : http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html ?? Arnaud On Tue, May 26, 2009 at 2:29 AM, ari.meyer ari.me...@gmail.com wrote: Hi Arnaud, I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and I'm getting the same error when using Wicket: org.apache.wicket.markup.MarkupNotFoundException: Markup not found. Reverting again back to 2.5.1, everything worked properly. Best regards, Ari Arnaud HERITIER wrote: Hi Community, The recent release 2.6 of the maven-eclipse-plugin created many problems for all of those who had/wanted to store non-java files under src/*/java (which is required for wicket, ajdt, and probably others usecases). Even we have many integration tests in this plugin we didn't notice this issue because our testcases allow us to check that generated configuration files aren't evolving and that we are able to import and use a project in eclipse (too heavy to do). To fix this issue we (Barrie to be honest) improved the plugin to allow the usage of includes and excludes. : http://jira.codehaus.org/browse/MECLIPSE-104 The documentation of these feature is here : http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html There are many broken links on the site and I don't know why. I'll investigate later. Others pages are the same in http://maven.apache.org/plugins/maven-eclipse-plugin/ For AJDT project you can have a look at this page : http://maven.apache.org/plugins/maven-eclipse-plugin- 2.7-SNAPSHOT/examples/ajdt-projects.html To test the plugin you have to add in your project or in your settings this repository : https://repository.apache.org/content/repositories/snapshots/ (be careful to the https protocol) The last version I deployed is : 2.7-20090416.000603-3 Please, test it and give us your feedback. If it is positive this week, we'll launch the release process the next one. cheers, -- Arnaud -- View this message in context: http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2972277.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: About Maven 1.0.2
You have probably a coorupted jar in your local repositoryYou can try to remove it. Arnaud On Thu, May 21, 2009 at 8:22 AM, Kerry Zhu houkun@gmail.com wrote: Hi, all. How to solve these problem? Could someone give me the reason? java:compile: [taskdef] [DEBUG] Finding class org.apache.avalon.meta.info.ant.MetaTask [taskdef] [VERBOSE] Ignoring Exception java.util.zip.ZipException: error in opening zip file reading resource org/apache/avalon/meta/info/ant/MetaTask.class from C:\Documents and Settings\xxx\.maven\repository\qdox\jars\qdox-1.1.jar [taskdef] [VERBOSE] Ignoring Exception java.util.zip.ZipException: error in opening zip file reading resource org/apache/avalon/meta/info/ant/MetaTask.class from C:\Documents and Settings\xxx\.maven\repository\avalon-framework\jars\avalon-framework-api-4.1.5-RC3.jar [taskdef] [VERBOSE] Ignoring Exception java.util.zip.ZipException: error in opening zip file reading resource org/apache/avalon/meta/info/ant/MetaTask.class from C:\Documents and Settings\xxx\.maven\repository\avalon-framework\jars\avalon-framework-impl-4.1.5-RC3.jar [taskdef] [VERBOSE] Ignoring Exception java.util.zip.ZipException: error in opening zip file reading resource org/apache/avalon/meta/info/ant/MetaTask.class from C:\Documents and Settings\xxx\.maven\repository\avalon-meta\jars\avalon-meta-tools-1.1-RC1.jar [taskdef] [VERBOSE] Ignoring Exception java.util.zip.ZipException: error in opening zip file reading resource org/apache/avalon/meta/info/ant/MetaTask.class from C:\Documents and Settings\xxx\.maven\repository\avalon-meta\jars\avalon-meta-api-1.1-RC1.jar [taskdef] [VERBOSE] Ignoring Exception java.util.zip.ZipException: error in opening zip file reading resource org/apache/avalon/meta/info/ant/MetaTask.class from C:\Documents and Settings\xxx\.maven\repository\avalon-meta\jars\avalon-meta-spi-1.1-RC1.jar [taskdef] [VERBOSE] Ignoring Exception java.util.zip.ZipException: error in opening zip file reading resource org/apache/avalon/meta/info/ant/MetaTask.class from C:\Documents and Settings\xxx\.maven\repository\avalon-meta\jars\avalon-meta-impl-1.1-RC1.jar popping off org.apache.maven.jelly.mavenjellycont...@118d189 for org.apache.maven.jelly.mavenjellycont...@648016 in maven-java-plugin:maven-java-plugin Thanks -- Arnaud
Re: [PLEASE TEST] Maven 2.2.0-RC2
I thought the wagon-lightweight was always here.It's with the 2.2.0-RC you delivered. Arnaud On Mon, May 18, 2009 at 5:35 PM, John Casey jdca...@commonjava.org wrote: Arnaud, are you saying that you see something like: May 6, 2009 1:58:26 PM hidden.org.apache.commons.httpclient.HttpMethodBase processCookieHeaders WARNING: Cookie rejected: $Version=0; JSESSIONID=E545E65FB5E46552ED8473D17DF1DC80; $Path=/servlets. Illegal path attribute /servlets. Path of origin: /nonav/repository//com.google.collections/jars/google-collections-0.9.jar even when using the lightweight http wagon? Is that using 2.1.0, or did you roll your own Maven 2.2.0-* with wagon-lightweight reintroduced? -john Arnaud HERITIER wrote: With the lightweight http wagon I have the issue NEXUS-1967 (rejected cookies) also for downloads. Arnaud On Fri, May 15, 2009 at 8:47 AM, Markku Saarela markku.saar...@iki.fi wrote: Hi, Our release failed. There are two problems. Command line: mvn -Psome -Denv=some-dev release:perform -X 1. Command line -Psome profile activation is not working, at least prepare perform and rollback goals. [WARNING] Profile with id: 'some' has not been activated. 2. release:perform failed for some weird -f option [INFO] Failed to re-parse additional arguments for Maven invocation. Unrecognized option: -f [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycl eExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor. java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultL ifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleE xecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java :181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:597) 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.MojoExecutionException: Failed to re-parse additional arguments f or Maven invocation. at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:133) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:678) ... 16 more Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase .java:89) at org.apache.maven.shared.release.phase.RunPerformGoalsPhase.execute(RunPerformGoalsPhase.j ava:67) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java: 336) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java: 282) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java: 262) at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:129) ... 18 more Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Failed to re-parse additiona l arguments for Maven invocation. at org.apache.maven.shared.release.exec.InvokerMavenExecutor.setupRequest(InvokerMavenExecut or.java:335) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecut or.java:377) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecut or.java:413) at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase .java:81) ... 23 more Caused
Re: Maven: The Definitive Guide in French
I think you can create a google group to discuss in french.I'll join it, even if I don't think I'll have the time to help you before september. Arnaud On Mon, May 18, 2009 at 7:17 PM, Fabien KRUBA fabien.kr...@gmail.comwrote: Same here, but it could be a good starting point to learn it:)Should we create a mailing list in order to manage the translation with you and Baptiste and avoiding pollution of us...@maven mailing list with french text ? Already have some questions regarding translation coherence..(which terms should we use, should we translate technical words etc..) Fabien. On Mon, May 18, 2009 at 1:13 PM, Emmanuel Hugonnet ehsavoi...@gmail.com wrote: You will have to be indulgent my git skills are very low :o( Ma maitrise de git est au niveau débutant alors faut pas trop m'en demander :o( Emmanuel -- Arnaud
Re: [PLEASE TEST] Maven 2.2.0-RC2
No I'm not sure. I just supposed it was it.Sorry Arnaud On Mon, May 18, 2009 at 10:13 PM, John Casey jdca...@commonjava.org wrote: I just grepped the uberjar file listing in RC2 for 'ightweight' and came up with nothing. Are you sure the lightweight wagon is present in the copy you have? Arnaud HERITIER wrote: I thought the wagon-lightweight was always here.It's with the 2.2.0-RC you delivered. Arnaud On Mon, May 18, 2009 at 5:35 PM, John Casey jdca...@commonjava.org wrote: Arnaud, are you saying that you see something like: May 6, 2009 1:58:26 PM hidden.org.apache.commons.httpclient.HttpMethodBase processCookieHeaders WARNING: Cookie rejected: $Version=0; JSESSIONID=E545E65FB5E46552ED8473D17DF1DC80; $Path=/servlets. Illegal path attribute /servlets. Path of origin: /nonav/repository//com.google.collections/jars/google-collections-0.9.jar even when using the lightweight http wagon? Is that using 2.1.0, or did you roll your own Maven 2.2.0-* with wagon-lightweight reintroduced? -john Arnaud HERITIER wrote: With the lightweight http wagon I have the issue NEXUS-1967 (rejected cookies) also for downloads. Arnaud On Fri, May 15, 2009 at 8:47 AM, Markku Saarela markku.saar...@iki.fi wrote: Hi, Our release failed. There are two problems. Command line: mvn -Psome -Denv=some-dev release:perform -X 1. Command line -Psome profile activation is not working, at least prepare perform and rollback goals. [WARNING] Profile with id: 'some' has not been activated. 2. release:perform failed for some weird -f option [INFO] Failed to re-parse additional arguments for Maven invocation. Unrecognized option: -f [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycl eExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor. java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultL ifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleE xecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java :181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:597) 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.MojoExecutionException: Failed to re-parse additional arguments f or Maven invocation. at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:133) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:678) ... 16 more Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase .java:89) at org.apache.maven.shared.release.phase.RunPerformGoalsPhase.execute(RunPerformGoalsPhase.j ava:67) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java: 336) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java: 282) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java: 262) at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:129) ... 18 more Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Failed to re-parse additiona l arguments for Maven invocation. at org.apache.maven.shared.release.exec.InvokerMavenExecutor.setupRequest(InvokerMavenExecut or.java:335
Re: [PLEASE TEST] Maven 2.2.0-RC2
With the lightweight http wagon I have the issue NEXUS-1967 (rejected cookies) also for downloads. Arnaud On Fri, May 15, 2009 at 8:47 AM, Markku Saarela markku.saar...@iki.fiwrote: Hi, Our release failed. There are two problems. Command line: mvn -Psome -Denv=some-dev release:perform -X 1. Command line -Psome profile activation is not working, at least prepare perform and rollback goals. [WARNING] Profile with id: 'some' has not been activated. 2. release:perform failed for some weird -f option [INFO] Failed to re-parse additional arguments for Maven invocation. Unrecognized option: -f [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycl eExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor. java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultL ifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleE xecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java :181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:597) 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.MojoExecutionException: Failed to re-parse additional arguments f or Maven invocation. at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:133) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:678) ... 16 more Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Failed to re-parse additional arguments for Maven invocation. at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase .java:89) at org.apache.maven.shared.release.phase.RunPerformGoalsPhase.execute(RunPerformGoalsPhase.j ava:67) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java: 336) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java: 282) at org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java: 262) at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:129) ... 18 more Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Failed to re-parse additiona l arguments for Maven invocation. at org.apache.maven.shared.release.exec.InvokerMavenExecutor.setupRequest(InvokerMavenExecut or.java:335) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecut or.java:377) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecut or.java:413) at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase .java:81) ... 23 more Caused by: org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -f at org.apache.commons.cli.Parser.processOption(Parser.java:363) at org.apache.commons.cli.Parser.parse(Parser.java:199) at org.apache.commons.cli.Parser.parse(Parser.java:85) at org.apache.maven.shared.release.exec.InvokerMavenExecutor.setupRequest(InvokerMavenExecut or.java:186) ... 26 more rgds, Markku John Casey wrote: Hi again, After finding and cleaning up some code that seems to be tainted during some of our efforts at generifying the codebase, we've respun a new release candidate. If you have time, please give it a whirl:
Re: Apache snapshot repository metadata incorrect.
I'm not administrator to verify but perhaps, the job to fix metadata isn't scheduled ? On Fri, May 1, 2009 at 6:09 PM, Nord, James jn...@nds.com wrote: Hi all, The metadata served by nexus for http://repository.apache.org/snapshots/ is incorrect for the archetype plugin. (https://repository.apache.org/content/groups/snapshots/org/apache/maven /plugins/maven-archetype-plugin/) metadata contains lots of snapshot versions but only 2.0-alpha-5-SNAPSHOT is available. (and hence running mvn archetype:generate from the command line fails as it tries to get 12-SNAPSHOT /James ?xml version=1.0 encoding=UTF-8 ? - https://repository.apache.org/content/groups/snapshots/org/apache/maven /plugins/maven-archetype-plugin/maven-metadata.xml# metadata xsi:schemaLocation=http://maven.apache.org/METADATA/1.0.0 http://maven.apache.org/xsd/metadata-1.0.0.xsd; xmlns=http://maven.apache.org/METADATA/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; groupIdorg.apache.maven.plugins/groupId artifactIdmaven-archetype-plugin/artifactId version2.0-alpha-4-SNAPSHOT/version - https://repository.apache.org/content/groups/snapshots/org/apache/maven /plugins/maven-archetype-plugin/maven-metadata.xml# versioning latest12-SNAPSHOT/latest release / - https://repository.apache.org/content/groups/snapshots/org/apache/maven /plugins/maven-archetype-plugin/maven-metadata.xml# versions version2.0-alpha-4-SNAPSHOT/version version2.0-alpha-5-SNAPSHOT/version version0.3.0-SNAPSHOT/version version1.0-SNAPSHOT/version version1.0-alpha-2-SNAPSHOT/version version1.0-alpha-3-SNAPSHOT/version version1.0-beta-3-SNAPSHOT/version version1.0.2-SNAPSHOT/version version1.1-SNAPSHOT/version version1.1.1-SNAPSHOT/version version1.2-SNAPSHOT/version version1.2.2-SNAPSHOT/version version1.3-SNAPSHOT/version version2.0-beta-9-SNAPSHOT/version version2.0-beta-10-SNAPSHOT/version version2.0.11-SNAPSHOT/version version2.1.0-SNAPSHOT/version version2.1-SNAPSHOT/version version2.1.0-M2-SNAPSHOT/version version2.2-SNAPSHOT/version version2.3-SNAPSHOT/version version2.4.4-SNAPSHOT/version version2.5-SNAPSHOT/version version3.0-alpha-2-SNAPSHOT/version version11-SNAPSHOT/version version12-SNAPSHOT/version /versions lastUpdated20090417213533/lastUpdated /versioning /metadata ** This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmas...@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS. To protect the environment please do not print this e-mail unless necessary. NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00 ** -- Arnaud
Re: [maven-eclipse-plugin] We need your help to test the future 2.7
How is doing the m2eclipse/q4e plugins (these are now for me references on how to integrate eclipse and maven). Arnaud On Wed, Apr 29, 2009 at 11:50 AM, Jörg Schaible joerg.schai...@gmx.dewrote: Hi Barrie, Barrie Treloar wrote at Mittwoch, 29. April 2009 09:03: On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible joerg.schai...@gmx.de wrote: Arnaud HERITIER wrote at Donnerstag, 16. April 2009 10:42: Hi Community, The recent release 2.6 of the maven-eclipse-plugin created many problems for all of those who had/wanted to store non-java files under src/*/java (which is required for wicket, ajdt, and probably others usecases). Even we have many integration tests in this plugin we didn't notice this issue because our testcases allow us to check that generated configuration files aren't evolving and that we are able to import and use a project in eclipse (too heavy to do). Regarding the new classpath ordering invented with 2.6, can you please comment again in MECLIPSE-544 for my proposal (I mention it here, since the issue is already closed). A classpath order like src/test/resource src/main/java src/test/java src/main/resource Will solve also the test resources first problem. Since Eclipse will complain anyway if you have to classes with the same name in src/main/java and src/test/java, their order does not really matter for Eclipse projects. What is wrong with having a classpath that matches Maven? Because every developer I've seen using the new plugin immediately thinks something is broken after refreshing the IDE. And when you explain them the situation, most of them moan about opening always the wrong node looking for the code. Actually, it is confusing, since Maven projects are now even more alienated in Eclipse as usual. Since mvn test will fail with a different error than Eclipse with your suggestion. Not really. It simply means that you created a situation (class files with same name in target/classes and target/test-classes) that is always reported as error in Eclipse and it does not matter which path comes first in this situation. In contrast will Maven simply compile, possibly even run the tests and actually behaves therefore always different. For an own test simply create a class Foo in src/main/java and interface Foo in src/test/java. Therefore I'd rather like to have my generated .classpath file to match what I'm used since years. I'd be willing to change my habits if there's actually a necessity, but obviously it is not. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
Re: [maven-eclipse-plugin] We need your help to test the future 2.7
thx for this feedbackI deployed a new snapshot : 2.7-20090427.230850-4 It includes the fixe for MECLIPSE-455http://jira.codehaus.org/browse/MECLIPSE-455 : Invalid dependent module archive name for EJB artifact * * Cheers Arnaud On Tue, Apr 21, 2009 at 2:15 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: The co-worker reported back that the plugin works as advertised (latest snapshot) Martijn On Tue, Apr 21, 2009 at 10:27 AM, Martijn Dashorst martijn.dasho...@gmail.com wrote: A co-worker tested it, and found it not working. He'll comment later. Martijn On Tue, Apr 21, 2009 at 12:20 AM, Arnaud HERITIER aherit...@gmail.com wrote: Ping ??Nobody wants to test it ? Without your help, will never be able to produce a plugin which replies to your needs. Cheers, Arnaud On Thu, Apr 16, 2009 at 10:42 AM, Arnaud HERITIER aherit...@gmail.com wrote: Hi Community, The recent release 2.6 of the maven-eclipse-plugin created many problems for all of those who had/wanted to store non-java files under src/*/java (which is required for wicket, ajdt, and probably others usecases). Even we have many integration tests in this plugin we didn't notice this issue because our testcases allow us to check that generated configuration files aren't evolving and that we are able to import and use a project in eclipse (too heavy to do). To fix this issue we (Barrie to be honest) improved the plugin to allow the usage of includes and excludes. : http://jira.codehaus.org/browse/MECLIPSE-104 The documentation of these feature is here : http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html There are many broken links on the site and I don't know why. I'll investigate later. Others pages are the same in http://maven.apache.org/plugins/maven-eclipse-plugin/ For AJDT project you can have a look at this page : http://maven.apache.org/plugins/maven-eclipse-plugin- 2.7-SNAPSHOT/examples/ajdt-projects.html To test the plugin you have to add in your project or in your settings this repository : https://repository.apache.org/content/repositories/snapshots/ (be careful to the https protocol) The last version I deployed is : 2.7-20090416.000603-3 Please, test it and give us your feedback. If it is positive this week, we'll launch the release process the next one. cheers, -- Arnaud -- Arnaud -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
Re: maven eclipse plugin problem with ejb projects
hi Steffen, Thx a lot. I'll apply it soon (I'll try this WE) cheers Arnaud On Fri, Apr 24, 2009 at 2:24 AM, Steffen Grunwald steffen.grunw...@gmail.com wrote: Hello Arnaud, Can you also provide an integration test to validate the issue ? If you give me ne, I'll apply them on 2.7 Great. There you go. I attached the testcase to [1]. Thanks, Steffen [1] http://jira.codehaus.org/browse/MECLIPSE-455 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
Re: maven eclipse plugin problem with ejb projects
I just reviewed it.Thx for your help. Can you also provide an integration test to validate the issue ? If you give me ne, I'll apply them on 2.7 Cheers, Thx On Thu, Apr 23, 2009 at 1:03 PM, Steffen Grunwald steffen.grunw...@gmail.com wrote: Hello, I'm facing an issue mentioned in bug [1] and [2] that causes a wrong extension in the eclipse .settings files. This problem still exists in the 2.6 release. I submitted a patch quite a while ago and would like to know, if there are some plans to commit the patch or fix the problem in another way for a next release. Thanks, Steffen [1] http://jira.codehaus.org/browse/MECLIPSE-451 [2] http://jira.codehaus.org/browse/MECLIPSE-455 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
Re: [maven-eclipse-plugin] We need your help to test the future 2.7
Ping ??Nobody wants to test it ? Without your help, will never be able to produce a plugin which replies to your needs. Cheers, Arnaud On Thu, Apr 16, 2009 at 10:42 AM, Arnaud HERITIER aherit...@gmail.comwrote: Hi Community, The recent release 2.6 of the maven-eclipse-plugin created many problems for all of those who had/wanted to store non-java files under src/*/java (which is required for wicket, ajdt, and probably others usecases). Even we have many integration tests in this plugin we didn't notice this issue because our testcases allow us to check that generated configuration files aren't evolving and that we are able to import and use a project in eclipse (too heavy to do). To fix this issue we (Barrie to be honest) improved the plugin to allow the usage of includes and excludes. : http://jira.codehaus.org/browse/MECLIPSE-104 The documentation of these feature is here : http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html There are many broken links on the site and I don't know why. I'll investigate later. Others pages are the same in http://maven.apache.org/plugins/maven-eclipse-plugin/ For AJDT project you can have a look at this page : http://maven.apache.org/plugins/maven-eclipse-plugin- 2.7-SNAPSHOT/examples/ajdt-projects.html To test the plugin you have to add in your project or in your settings this repository : https://repository.apache.org/content/repositories/snapshots/ (be careful to the https protocol) The last version I deployed is : 2.7-20090416.000603-3 Please, test it and give us your feedback. If it is positive this week, we'll launch the release process the next one. cheers, -- Arnaud -- Arnaud
[maven-eclipse-plugin] We need your help to test the future 2.7
Hi Community, The recent release 2.6 of the maven-eclipse-plugin created many problems for all of those who had/wanted to store non-java files under src/*/java (which is required for wicket, ajdt, and probably others usecases). Even we have many integration tests in this plugin we didn't notice this issue because our testcases allow us to check that generated configuration files aren't evolving and that we are able to import and use a project in eclipse (too heavy to do). To fix this issue we (Barrie to be honest) improved the plugin to allow the usage of includes and excludes. : http://jira.codehaus.org/browse/MECLIPSE-104 The documentation of these feature is here : http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html There are many broken links on the site and I don't know why. I'll investigate later. Others pages are the same in http://maven.apache.org/plugins/maven-eclipse-plugin/ For AJDT project you can have a look at this page : http://maven.apache.org/plugins/maven-eclipse-plugin- 2.7-SNAPSHOT/examples/ajdt-projects.html To test the plugin you have to add in your project or in your settings this repository : https://repository.apache.org/content/repositories/snapshots/ (be careful to the https protocol) The last version I deployed is : 2.7-20090416.000603-3 Please, test it and give us your feedback. If it is positive this week, we'll launch the release process the next one. cheers, -- Arnaud
Re: eclipse:eclipse and sorting in .classpath
In maven when you are executing tests, tests classes and ressources are in the classpath before your main classes and ressources. In eclipse when you reorder the classpath in the project, you also reorder how entries are displayed in the UI. Our goal is to be sure that you have the same classpath in eclipse and in maven when you launch tests and not to annoy you by changing the order of entries in the UI. Is it more clear ? 2009/4/15 Ingo Düppe mailing-li...@dueppe.com Hello, what do you mean with this the order used to build by maven? I mean you cannot build test sources before you build the main code. Or does Eclipse compile the source folder in the oposite order? Regards, Ingo Arnaud HERITIER schrieb: This the order used to build by maven. It was done to be sure that you won't have something building in a tool and not in the other.You can continue to use the old 2.5.1 if you prefer by setting the version of the plugin (best pratice) in your pluginsManagement. Arnaud On Tue, Apr 14, 2009 at 5:17 AM, alien.sulin sulinchong1...@gmail.com wrote: yeah, it is the same to me ,since maven has download the eclipse-plugin(version:2.6), anybody comes to help us? Thanks! On Tue, Apr 14, 2009 at 12:05 AM, Ingo Düppe mailing-li...@dueppe.com wrote: Hello, I don't know what I did or what happened, but since a week the order of the source folder within the .classpath file of eclipse had changed after I ran mvn eclipse:clean eclipse:eclipse. Now the test folders come first and than the main folder. So the order of my source folders in eclipse is src/main/java, src/test/java instead of src/test/java,src/main/java. Does anybody know how to reset the default order? Regards Ingo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- 漠洋(苏琳冲) SuLinchong Phone 13656669328 Qq387973308 Msn sulinch...@hotmail.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
Re: maven-eclipse-plugin 2.6 project references
Hi Stephen, Thx a lot for this feedback. I don't remember when and why we did these changes but I understand your problem. It seems that the autodiscovery of projects dependencies in the workspace is activated by default. I think that this feature should be deativated by default (First issue to open). The problem about projects naming is that maven identifies a project from groupId/artifactId/version. In Eclipse a link betwwen project is done using project's name which is by default the artifactId. Having groupID/artifactId and version in eclipse project's name is the better solution to not have problem of identification but after that projects are unreadable (except if you are working on a 54 display). I don't know what to do to have something logical to identify a maven project in eclipse. I didn't have a look to see how m2eclise and Q4E are doing to mange these case (several branches of a project in the same workspace) On Mon, Apr 13, 2009 at 7:09 PM, Stephen Duncan Jr stephen.dun...@gmail.com wrote: Amongst several other surprising changes in the 2.6 release of the maven-eclipse-plugin, I'd like to explain on one change caused some confusion for myself and other members of my development team. I'm not sure it's really a bug, or exactly what feature enhancement to file, so I'm hoping this thread can help determine a better future outcome. Background: We have many different components as individual maven projects, no multi-project/reactor projects, and Hudson continuously building and deploying SNAPSHOTs to Nexus. The typical workflow for a developer would be to check out any particular component they needed to work on, and they could run 'mvn eclipse:eclipse' to get the classpath right, and to download the latest versions of any dependent components (settings.xml defined the repository with a updatePolicy of always). If they wanted to make changes to a dependent component locally, they'd make the changes, run mvn install, and then refresh the project to get those changes. This all worked without any extra configuration of the eclipse plugin. Also, the name of the project in eclipse didn't necessarily match the artifactId in anyway; typically it matched the folder in Subversion (which is sometimes, though rarely, different from the artifactId), or the the name of the branch in Subversion (artifactId-version, where version might be a SNAPSHOT, or be something like 1.2.x). With the eclipse plugin 2.6, it seems new work has been done to try to identify other projects in the eclipse workspace, and use those as project dependencies, instead of jar dependencies in the local repository. To get the workflow described above, I've gone ahead and configured (in our corporate parent pom) the eclipse plugin to not do project references at all. However, I didn't have to specify that before (I think it only used to affect reactor-builds), and therefore our team did get confused by the new behavior. When all SNAPSHOT dependencies were being downloaded from the repository, the version was the timestamp version of the SNAPSHOT, and never matched a project in the workspace, and so it behaved as before, so no problem. However, once somebody installed a dependency locally, the version was just -SNAPSHOT, so the eclipse plugin believed it found a match in the workspace. However, the name it tried to use for the project reference was the artifactId, not the actual name of the project in eclipse, and therefore the project showed up as broken in eclipse, due to the unsatisfied dependency. I think it would be better if the default went back to only doing project references for reactor builds. I also don't know if there's some better way to figure out the right project name to use for the reference. Even if our dependency had been named to match the project reference, somebody working on the branch may have gotten the WRONG project reference (the trunk would have the artifactId, but the wrong version, the branch project name would be the right version, but not match the expected name). -- Stephen Duncan Jr www.stephenduncanjr.com -- Arnaud
Re: eclipse:eclipse and sorting in .classpath
This the order used to build by maven. It was done to be sure that you won't have something building in a tool and not in the other.You can continue to use the old 2.5.1 if you prefer by setting the version of the plugin (best pratice) in your pluginsManagement. Arnaud On Tue, Apr 14, 2009 at 5:17 AM, alien.sulin sulinchong1...@gmail.comwrote: yeah, it is the same to me ,since maven has download the eclipse-plugin(version:2.6), anybody comes to help us? Thanks! On Tue, Apr 14, 2009 at 12:05 AM, Ingo Düppe mailing-li...@dueppe.com wrote: Hello, I don't know what I did or what happened, but since a week the order of the source folder within the .classpath file of eclipse had changed after I ran mvn eclipse:clean eclipse:eclipse. Now the test folders come first and than the main folder. So the order of my source folders in eclipse is src/main/java, src/test/java instead of src/test/java,src/main/java. Does anybody know how to reset the default order? Regards Ingo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- 漠洋(苏琳冲) SuLinchong Phone 13656669328 Qq387973308 Msn sulinch...@hotmail.com -- Arnaud
Re: eclipse:eclipse suddenly adding including=**/*.java to .classpath
1) The Maven convention and good practice is to put ressources files like *.txt in src/main/resources. 2) The change you have is due to the new version 2.6 of the plugin which was released few days ago. To avoid such a surprise in the future, the good practice is to set the version of each plugin your are using the pluginsManagement of your (parent) pom. You can set it to 2.5.1 for the eclipse plugin to keep the old behavior. cheers arnaud On Thu, Apr 9, 2009 at 5:28 AM, Zach Cox zcox...@gmail.com wrote: Before this week, running mvn eclipse:eclipse would put a line like this in .classpath: classpathentry kind=src path=src/main/java/ Now this week it is putting this line in .classpath instead: classpathentry kind=src path=src/main/java including=**/*.java/ We have some .txt files that sit alongside .java files in the package structure in src/main/java. When running mvn compile all of those .txt files are copied into target/classes. Before this week, rebuilding in Eclipse also copied those .txt files into target/classes. However, now that the src/main/java line in .classpath contains including=**/*.java, Eclipse no longer copies the .txt files into target/classes. While I realize that technically only .java files should exist in src/main/java, it's a pain to create a duplicate package hierarchy in src/main/resources and this greatly reduces visibility of these .txt files. Did something just recently change with eclipse:eclipse to cause it to start putting including=**/*.java in .classpath? Is there any way I can get it to not put that in .classpath? Thanks, Zach - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
Re: buildpath probleme with eclipse:eclipse goal
there are several thread and issues opened about problem in the release 2.6 of the plugin with aspectj projects.Set the version of the maven-eclipse-plugin to 2.5.1 in the dependencyManagement part of your pom to use the previous version while we are fixing it. On Tue, Apr 7, 2009 at 7:39 PM, florian.cavagn...@ingdirect.fr wrote: Hello Since two days, I don't know why but when I generate the eclipse configuration files (.classpath and .project) of my maven project with the eclipse plugin (goal eclipse:eclipse), it don't add all the dependencies listed in my pom.xml! And one in particular: org.aspectj.aspectjrt-1.5.4 I tried with a simple pom with only one dependency: dependency groupIdorg.aspectj/groupId artifactIdaspectjrt/artifactId version1.6.0/version scopecompile/scope /dependency Depencency tree shows: [INFO] [INFO] Building Unnamed - mon.cul:prout:jar:1.0 [INFO]task-segment: [dependency:tree] [INFO] [INFO] [dependency:tree] [INFO] mon.cul:prout:jar:1.0 [INFO] \- org.aspectj:aspectjrt:jar:1.6.0:compile [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 6 seconds [INFO] Finished at: Tue Apr 07 19:36:49 CEST 2009 [INFO] Final Memory: 11M/127M [INFO] But when I run eclipse:eclipse, I have nothing in my buildpath, only JRE library! [INFO] [INFO] Building Unnamed - mon.cul:prout:jar:1.0 [INFO]task-segment: [eclipse:clean, eclipse:eclipse] [INFO] [INFO] [eclipse:clean] [INFO] Deleting file: .project [INFO] Deleting file: .classpath [INFO] Deleting file: .wtpmodules [INFO] Deleting file: .component [INFO] Deleting file: org.eclipse.wst.common.component [INFO] Deleting file: org.eclipse.wst.common.project.facet.core.xml [INFO] Deleting file: org.eclipse.jdt.core.prefs [INFO] Deleting file: org.eclipse.ajdt.ui.prefs [INFO] Preparing eclipse:eclipse [INFO] No goals needed for project - skipping [INFO] [eclipse:eclipse] [INFO] Using Eclipse Workspace: D:\workspaces\SRC_MCA\Intense_Dev [INFO] no substring wtp server match. [INFO] Using as WTP server : Apache Tomcat v5.5 [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] Not writing settings - defaults suffice [INFO] Wrote Eclipse project for prout to D:\workspaces\SRC_MCA\Intense_Dev\prout. [INFO] Sources for some artifacts are not available. Please run the same goal with the -DdownloadSources=true parameter in order to check remote repositories for sources. List of artifacts without a source archive: o org.aspectj:aspectjrt:1.6.0 Javadoc for some artifacts is not available. Please run the same goal with the -DdownloadJavadocs=true parameter in order to check remote repositories for javadoc. List of artifacts without a javadoc archive: o org.aspectj:aspectjrt:1.6.0 [INFO] [INFO] BUILD SUCCESSFUL [INFO] Did you know how to solve that? thanks - ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it. Messages and attachments are scanned for all viruses known. If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
Re: Eclipse plugin 2.6 and package explorer order
yes it was intentional. It is annoying but you'll be sure to have the same behavior in eclipse and in maven. cheers arnaud On Mon, Apr 6, 2009 at 1:02 PM, Paul Nyheim hurrag...@gmail.com wrote: I think this is intentional to be aligned with the classpath order that maven sets up when running tests. See http://jira.codehaus.org/browse/MECLIPSE-318 On Mon, Apr 6, 2009 at 11:07 AM, Martin Gilday martin.li...@imap.cc wrote: I am running Maven 2.1.0 and 2.6 of the eclipse plugin. For some reason after running an eclipse:eclipse on both new and existing projects I am now getting src/test/java and resources appearing above src/main/java and resources. This is happening for all developers using our corporate POM and the version is the only thing I remember changing. It is slightly frustrating as everyone is used to the original order. Is this a change to the plugin or something wrong with my POM? When I look in .classpath I can see that src/test/java is the first entry, and in older .classpath it is the 3rd entry. Thanks, Martin. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
[ANN] IDLJ Maven Plugin 1.1 Released
The Mojo team is pleased to announce the release of the IDLJ Maven Plugin, version 1.1 This plugin will process all corba *.idl files in the sourceDirectory into a common generated sources output directory. This will occur during the generate-sources phase and the sources directory will be added to the project for the compile phase. The plugin supports also to generate test sources from idl files. http://mojo.codehaus.org/idlj-maven-plugin/ You could run 'mvn -up' to get the latest version of this plugin, or specify the version in your project's plugin configuration: project ... build !-- To define the plugin version in your parent POM -- pluginManagement plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdidlj-maven-plugin/artifactId version1.1/version /plugin ... /plugins /pluginManagement !-- To use the plugin goals in your POM or parent POM -- plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdidlj-maven-plugin/artifactId version1.1/version /plugin ... /plugins /build ... /project This new version only fixes new issues and doesn't add new features but we prefered to bump the minor version because we changed many lines of code. Issues fixed are : * [MIDLJ-1] - IBM JVM not recognised * [MIDLJ-6] - Plugin doesn't fail if parsing of IDL fails * [MIDLJ-7] - IDLs in sub-directories are always recompiled * [MIDLJ-8] - Generated java files not found by java compiler * [MIDLJ-9] - IDLJ fails on unix with absolute path if you don't have the right to write in a parent directory. Replace absolute paths in the command line by relative paths Enjoy, -The Mojo team -- Arnaud
Re: [mojo-dev] [vote] idlj-maven-plugin v 1.1
On Fri, Apr 3, 2009 at 5:34 PM, Benjamin Bentmann benjamin.bentm...@udo.edu
wrote:
Arnaud HERITIER wrote:
I propose to release the idlj plugin v 1.1.
+0, not using it. Notes:
mvn dependency:analyze reports issues with the proper declaration of
plexus-utils. Also, the plugin's dependencies include
plexus-container-default once from the old group id plexus and once from
the current one.
ok I excluded them
There are some javadoc warnings when building the site.
fixed
The POM snippet on the usage page does not include a version element for
the plugin, promoting bad practices.
fixed
From TestIDLJMojo:
* @parameter default-value=${basedir}/src/test/idl
*/
private List includeDirs;
I haven't actually tried but I could imagine this would choke when trying
to assign a scalar value to a collection-typed field. So the default-value
probably needs to be removed.
yes. It was an error. fixed
Furthermore, includeDirs is used as a ListString where the strings denote
paths. Without some form of manual basedir-alignment, relative paths won't
work properly in reactor builds. Changing the field-type to File[] should be
an easy fix.
Fixed
Thx a lot for all your feedbacks
I deployed a new SNAPSHOT (1.1-20090403.222528-19) if some users want to
give it a try.
cheers
arnaud
Benjamin
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Arnaud
Re: [Vote] findbugs-maven-plugin v 2.0 release
1.3.8 isn't in the central repo : http://repo1.maven.org/maven2/com/google/code/findbugs/findbugs/ Arnaud On Thu, Mar 26, 2009 at 3:43 PM, TM thorsten.moel...@unibas.ch wrote: -1 Background: According to http://jira.codehaus.org/browse/MFINDBUGS-66, the plugin integrates Findbugs version 1.3.6. Meanwhile, version 1.3.8 was released. I suggest to catch up with that release before releasing the plugin. -- Thorsten Garvin LeClaire-2 wrote: The Maven Findbugs team would like to release Maven Findbugs Plugin version 2.0 This plugin allows the developer to run Findbugs analysis against a Maven project and produce site output in HTML to match other site reports. There are option to produce other XML outputs which are used by other plugins. Issues fixed in this release: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truefixfor=14335pid=11701status=6sorter/field=issuekeysorter/order=DESCsorter/field=issuetypesorter/order=DESC More information can be found at the plugin site: http://mojo.codehaus.org/findbugs-maven-plugin/ Issues Can be registered in JIRA at: http://jira.codehaus.org/browse/MFINDBUGS More information on FindBugs http://findbugs.sourceforge.net/index.html You can test the Maven Findbugs Plugin in your own project by adding the following dependency: dependency groupIdorg.codehaus.mojo/groupId artifactIdfindbugs-maven-plugin/artifactId version2.0-SNAPSHOT/version /dependency *NOTE* Version 2.0 and greater of the Maven Findbugs plugin will require Maven to be run with a minimum of Java 5. This is consistent with Findbugs requirement for their versions of 1.3.X and greater. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Regards, Garvin LeClaire garvin.lecla...@gmail.com -- View this message in context: http://www.nabble.com/-Vote--findbugs-maven-plugin-v-2.0--release-tp22715803p22723449.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
Re: How to set correct EAR facet version in Eclipse
with which plugin ? maven-eclipse-plugin, m2eclipse, q4e ? On Thu, Mar 5, 2009 at 10:19 AM, Roland Bali roland.b...@gmail.com wrote: Hi, I've created a EAR project but can't seem to get the Eclipse plugin to generate the correct project facet version. It's set to 1.4 but should be 5.0. How can I set this? Kind regards, Roland -- Arnaud
Re: How to set correct EAR facet version in Eclipse
I think there's no parameter to set itIt's auto-magicaly discovered from your dependencies It could be something to add in the eclipse plugin (a jeeVersion parameter) On Fri, Mar 6, 2009 at 6:59 AM, Roland Bali roland.b...@gmail.com wrote: Oh, sorry. I'm using the maven-ear-plugin and maven-eclipse-plugin. Since yesterday I've been looking thru the source for the ear-plugin and found that it looks for some JEE dependencies but I don¨'t have these, instead I have a JBoss 4.2.1. dependency which include the JEE libraries. But I'm still interested in a way of specifying which version I would like to use instead of having to include those libraries that the plugin looks for. Any clues? Kind regards, Roland On Thu, Mar 5, 2009 at 11:38 PM, Arnaud HERITIER aherit...@gmail.com wrote: with which plugin ? maven-eclipse-plugin, m2eclipse, q4e ? On Thu, Mar 5, 2009 at 10:19 AM, Roland Bali roland.b...@gmail.com wrote: Hi, I've created a EAR project but can't seem to get the Eclipse plugin to generate the correct project facet version. It's set to 1.4 but should be 5.0. How can I set this? Kind regards, Roland -- Arnaud -- Arnaud
Re: classpath attributes for maven-eclipse-plugin
Hi Is it this issue : http://jira.codehaus.org/browse/MECLIPSE-270 ? can you test a 1.6-SNAPSHOT ? arnaud On Wed, Mar 4, 2009 at 7:11 AM, Andrew Eisenberg and...@eisenberg.aswrote: Hi all, I was wondering if it is possible to add classpath attributes to the .classpath file when the maven eclipse plugin creates an eclipse project. For example, this is what i would like to do something like this (the attribute section): ?xml version=1.0 encoding=UTF-8? classpath ...normal classpath... classpathentry kind=var path=M2_REPO/.../com.springsource.org.asp ectj.runtime-1.6.2.RELEASE.jar/ attributes attribute name=org.eclipse.ajdt.aspectpath value=org.eclipse.ajdt.aspectpath/ /attributes /classpathentry ...normal classpath... /classpath thanks, --andrew - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
Re: maven-eclipse-plugin
why a plugin in eclipse to support maven doesn't fit your needs ? Arnaud 2009/2/16 Dmitri Ilyin ilyin.dmi...@googlemail.com well, this is an eclipse plugin, i need maven plugin. 2009/2/16 Jason van Zyl jvan...@sonatype.com http://m2eclipse.sonatype.org/ -- Arnaud
Re: maven-eclipse-plugin
yes, thus your problem is the lack of support on some maven/eclipse features. And not because you don't want to use it. I suppose you'll take it as soon as it'll have those missing features. Arnaud On Mon, Feb 16, 2009 at 11:32 PM, Siarhei Dudzin siarhei.dud...@gmail.comwrote: I don't know for Dmitri but for me it doesn't support war overlays :) Best regards, Siarhei Dudzin On Mon, Feb 16, 2009 at 10:58 PM, Arnaud HERITIER aherit...@gmail.com wrote: why a plugin in eclipse to support maven doesn't fit your needs ? Arnaud 2009/2/16 Dmitri Ilyin ilyin.dmi...@googlemail.com well, this is an eclipse plugin, i need maven plugin. 2009/2/16 Jason van Zyl jvan...@sonatype.com http://m2eclipse.sonatype.org/ -- Arnaud -- Arnaud
Re: slightly [ot] Help setting up a MAC for Maven
You can download java 1.4, 1.5 1.6 updates here : http://support.apple.com/kb/HT2733 You can switch between them using Java Preferences in Applications Utilities Java For maven you just have to extract it somewhere (in a local Application directory of your user's home for example) and you put it's bin directory before the predefined PATH in your ~/.bash_login script Arnaud On Thu, Feb 12, 2009 at 11:50 PM, David C. Hicks dhi...@i-hicks.org wrote: The Mac isn't much different than your Linux systems. The trickiest part is that they don't use the /home directory. Users are located in /Users, instead. (I can't imagine why they did that, but it doesn't matter.) You still have .bashrc and .bash_profile available to you in your user's home directory. So, it's no trouble to install Maven there and set up your environment variables the as you might on Linux. If you prefer to set things up so that they are more universally available on the Mac, you can always sudo bash and go to town as the root user. I'm not at my Mac, right now, so I can't speak in specifics. If you would like more details, shoot me back a private email and we can take it offline. As far as I know, there is no Java6 for Mac, yet. So far, the only compatibility difference I've run across, as compared to the available Java5, is that the String.isEmpty() method doesn't exist in Java5. We simply changed our code to use commons StringUtils.isEmpty(). Dave Mick Knutson wrote: I am used to configuring Windows and Linux as a developer machine. But want to setup a mac now. And I am finding it tough to add maven 2.0.9 along with MAVEN_HOME, as well as a newer JDK 6 and JAVA_HOME so I can run command line builds on a Mac. Can anyone point me to a tutorial or something? --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com --- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Arnaud
Re: ITs/verification and comparison of results - tools to support this?
I think you have in mind to replace ITs in the maven-eclipse-plugin ?? Arnaud On Wed, Dec 17, 2008 at 9:32 PM, Barrie Treloar baerr...@gmail.com wrote: Does anyone know any tools to support integration tests and verifying that the results match what was expected? Something that checks the files created against the expected files after replacing variables or perhaps using pattern matching. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- .. Arnaud HERITIER 12 guidelines to boost your productivity with a Java software factory - http://tinyurl.com/56s9tw .. 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: Problems with maven 2.0.9, 2.1.0-M1 and profiles.
What I learned recently is that activation of profiles isn't inherited.
Can't it be your problem ? By default in a child project you won't have
access to the properties values defined in the local profile.
Arnaud
On Mon, Dec 15, 2008 at 11:56 PM, Carlos Chávez ccha...@agssa.net wrote:
Hello everyone.
I have defined in a parent POM some profiles and some properties,
then in the child profile i have defined some resources
that use those properties, it looks like:
parent POM:
project
...
...
profiles
profile
idlocal/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
gator.smtp.serverlocalhost/gator.smtp.server
gator.smtp.fromr...@localhost/gator.smtp.from
store-janitor.freememory2048000/store-janitor.freememory
store-janitor.heapsize6660/store-janitor.heapsize
/properties
/profile
profile
idgator/id
properties
gator.smtp.serverserver.com.ni/gator.smtp.server
gator.smtp.fromsist...@server.com.ni/gator.smtp.from
store-janitor.freememory10737000/store-janitor.freememory
store-janitor.heapsize526133000/store-janitor.heapsize
/properties
/profile
/profiles
/project
The following is the child POM:
build
...
...
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
/resource
resource
directorysrc/main/webapp/WEB-INF/properties/directory
filteringtrue/filtering
targetPath../gator/WEB-INF/properties/targetPath
/resource
/resources
/build
There is a file in src/main/webapp/WEB-INF/properties with the following:
# smtp properties
gator.smtp.server = ${gator.smtp.server}
gator.smtp.from = ${gator.smtp.from}
This configuration work perfectly on maven 2.0.7, the maven build
depending on the profile change the properties for his value. Now in
maven 2.0.9 and 2.1.0-M1 this configuration seems like is not working,
there is no error messages or warning.
The other issue is that i can not override a property defined in the POM
by a property from the command line.
--
Cheers.
Carlos Chávez.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
..
Arnaud HERITIER
12 guidelines to boost your productivity with a Java software factory -
http://tinyurl.com/56s9tw
..
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: Release aggregating parent poms
You can use the -N comand line option in the release plugin options and in the command line to not call the release for modules. The problem is that it will tag the parent pom and all submodules, which can be very long. Arnaud On Fri, Dec 5, 2008 at 12:36 PM, jallen [EMAIL PROTECTED] wrote: Could someone from the dev team possibly explain their process of releasing parent poms such as the maven-plugins. i see that the trunk of this includes modules for everything. However the release versions have this commented out. I presume this change is made just before a release is performed preventing the release plugin from processing the modules, which are not the things being 'released'. And then added again to the new SNAPSHOT version. Does this mean that the modules section in that pom is just developer aid and not a real part of the nature of that project., i.e. if we checkout a released version of maven-plugins we do not repeat the build that the trunk performs. I alsways get confused between the relationship and 'integration' of a parent, the indepence of children that can inherit from on older versions of the parent and the SCM domain (i.e. SVN will be copying all the child directories into the tag, even though they're not being released). couldnt find anything on the net explaining these kinds of scenarios and my head hurts from trying to anticipate the various pom relationships and ther overall dev and release lifecycle. Cheers, John -- View this message in context: http://www.nabble.com/Release-aggregating-parent-poms-tp20852139p20852139.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] -- .. Arnaud HERITIER 12 guidelines to boost your productivity with a Java software factory - http://tinyurl.com/56s9tw .. 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: Release plugin woes
[commit aborted]: lock failed - giving up [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Unable to commit files Provider message: The cvs command failed. Command output: cvs commit: failed to create lock directory for `/home/CVS/AR' (/home/CVS/AR/#cvs.lock): No such file or directory cvs commit: lock failed - giving up cvs [commit aborted]: lock failed - giving up at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:697) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:551) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:521) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:369) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) 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:597) 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.MojoFailureException: Unable to commit files Provider message: The cvs command failed. Command output: cvs commit: failed to create lock directory for `/home/CVS/AR' (/home/CVS/AR/#cvs.lock): No such file or directory cvs commit: lock failed - giving up cvs [commit aborted]: lock failed - giving up at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:144) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:676) ... 16 more [INFO] -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER 12 guidelines to boost your productivity with a Java software factory - http://tinyurl.com/56s9tw .. 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: how to use plexus-maven-plugin to both generate and merge descriptor ?
I don't know and I had to fix it in the project's build when I upgraded the version of the plugin in the release plugin. I bound it in the process-ressources On Fri, Nov 28, 2008 at 4:30 PM, nicolas de loof [EMAIL PROTECTED] wrote: Hi according to plexus doc, the plexus-maven-plugin has a merge goal (process-resources phase) and an descriptor goal (process-classes phase) Based on declared phases, It seems not possible to merge with the generated descriptor, is it ? Why does descriptor set process-classes phase and not generate-resources ??) -- .. Arnaud HERITIER 12 guidelines to boost your productivity with a Java software factory - http://tinyurl.com/56s9tw .. 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: mvn release:perform blowing up?
: Could not find the model file '/home/rusty/java/cars/cars_parent/target/cars_net'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file '/home/rusty/java/cars/cars_parent/target/cars_net'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.j ava: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.project.ProjectBuildingException: Could not find the model file '/home/rusty/java/cars/cars_parent/target/cars_net'. for project unknown at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProj ectBuilder.java:1557) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInterna l(DefaultMavenProjectBuilder.java:504) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectB uilder.java:198) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) ... 11 more Caused by: java.io.FileNotFoundException: /home/rusty/java/cars/cars_parent/target/cars_net (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at hidden.org.codehaus.plexus.util.xml.XmlReader.init(XmlReader.java:123) at hidden.org.codehaus.plexus.util.xml.XmlStreamReader.init(XmlStreamReader.jav a:67) at hidden.org.codehaus.plexus.util.ReaderFactory.newXmlReader(ReaderFactory.java: 113) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProj ectBuilder.java:1552) ... 17 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Nov 24 13:42:28 PST 2008 [INFO] Final Memory: 1M/2M [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Maven execution failed, exit code: '1' - 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] - 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] -- .. Arnaud HERITIER 12 guidelines to boost your productivity with a Java software factory - http://tinyurl.com/56s9tw .. 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: generate PDF site
I just re-uploaded all our doxia artefacts in the SNAPSHOTs repository Arnaud On Wed, Nov 19, 2008 at 7:23 PM, Wendy Smoak [EMAIL PROTECTED] wrote: You can check out Doxia from https://svn.apache.org/repos/asf/maven/doxia/trunks The doxia-doc-renderer module is under doxia-sitetools. If you need help building it (and better, if you want to help Lukas fix it!) please join us on the development mailing list. :) -- Wendy On Wed, Nov 19, 2008 at 9:27 AM, Marc Lustig [EMAIL PROTECTED] wrote: The build fails due to missing artifact org.apache.maven.doxia:doxia-doc-renderer:jar:1.0-beta-1-SNAPSHOT Do you know where to get this snapshot? - 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: Experimental Grails archetype
Hi Ed, As soon as Peter and the grails team will release the new version of the plugin, I'll update our pages @ OCTO to note that we deprecate this plugin and encourage to use the new one. Arnaud On Tue, Nov 11, 2008 at 2:09 PM, Ed [EMAIL PROTECTED] wrote: I'm confused. Is the groupId for the grails-maven-plugin changing from com.octo.mtg to org.grails? If so is this web page out of date? http://forge.octo.com/maven/sites/mtg/grails-maven-plugin/usage.html I'm using the grails plugin in a bamboo build plan currently. Will I need to updated the plugin descriptors in my settings.xml? Please advise... and Thanks for your great work! On Tue, Nov 11, 2008 at 1:26 AM, Peter Ledbrook [EMAIL PROTECTED] wrote: PabloS wrote: Thanks. Where shall I subscribe to report bugs in the maven-grails-plugin? I can't generate a domain class :) See the end of my first e-mail - there's a link to a JIRA issue :) Anyway, I have fixed the problem with creating a domain class (as well as all the other Grails commands). Note that the group ID for the plugin is now org.grails rather than com.octo.mtg. There seems to be a problem in that the tests aren't being picked up, but I'll look into that. Cheers, Peter -- View this message in context: http://www.nabble.com/Experimental-Grails-archetype-tp20395006p20435285.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] -- Ed - 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: maven-release-plugin svn branch command failed
The beta-8 was just released but I didn't notice this bug when I tried it. You can try the 2.0-beta-7 If it doesn't solve your problem you can try to change you're svn version like Borut proposes. If it solves it, you can open an issue ;-) On Tue, Nov 4, 2008 at 3:11 PM, Peter Nedonosko [EMAIL PROTECTED] wrote: Hi, Thank you for fast feedback! 2008/11/4 Arnaud HERITIER [EMAIL PROTECTED] Hi Peter, which version of the release plugin are you using? We just released a new version, perhaps there's an issue in it ? I use 2.0-beta-8 version of the plugin. Which version do you release? If you didn't change your version of the plugin it's probably an issue in svn because you are reproducing the issue with the svn command line. There are several problems to create tags with svn 1.5.x. I thought it was fixed, but I'm not sure. There was several threads about this on this mailing list. cheers Arnaud On Tue, Nov 4, 2008 at 1:59 PM, Peter Nedonosko [EMAIL PROTECTED] wrote: Hi guys! I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java 1.5.0_15 and svn 1.5.4. I cannot run release:branch goal from trunk successful. Branch commit failed on command svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit . http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC I have tried this command manually svn copy . http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC it fails too. But if I replace '.' on full path of the trunk it will works svn copy http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/trunk http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC I feel it's a bug, but may be I do smth wrong here? Anybody can help or comment the usecase? Full error message [INFO] [INFO] Building eXo Kernel [INFO]task-segment: [release:branch] (aggregator-style) [INFO] [INFO] [release:branch] [INFO] Verifying that there are no local modifications... [INFO] Executing: cmd.exe /X /C svn --non-interactive status [INFO] Working directory: D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk What is the new working copy version for eXo Kernel? (org.exoplatform.kernel:config) 2.0.5-SNAPSHOT: : [INFO] Transforming 'eXo Kernel'... [INFO] Transforming 'eXo Kernel Commons'... [INFO] Transforming 'eXo Container'... [INFO] Updating exo.kernel.commons to 2.0.4-SNAPSHOT [INFO] Transforming 'Common service'... [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT [INFO] Transforming 'Remote service implementation'... [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT [INFO] Transforming 'Cache service api'... [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT [INFO] Updating exo.kernel.component.remote to 2.0.4-SNAPSHOT [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT [INFO] Transforming 'Command service impl'... [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT [INFO] Checking in modified POMs... [INFO] Executing: cmd.exe /X /C svn --non-interactive commit --file D:\Tmp\maven-scm-142291247.commit --targets D:\Tmp\maven-scm-61108-targets [INFO] Working directory: D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk [INFO] Branching release with the label 2.0.4-RC... [INFO] Executing: cmd.exe /X /C svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit . http://svn.exoplatform.org/svnroot/exoplatform/projects/ kernel-new/branches/2.0.4-RChttp://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC [INFO] Working directory: D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to branch SCM Provider message: The svn branch command failed. Command output: svn: Commit failed (details follow): svn: File '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/pom.xml' already exists at org.apache.maven.shared.release.phase.ScmBranchPhase.execute(ScmBranchPhase.java:98) at org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:379) at org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:350) at org.apache.maven.plugins.release.BranchReleaseMojo.execute(BranchReleaseMojo.java:133) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493
Re: maven-release-plugin svn branch command failed
) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) 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] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to branch SCM Provider message: The svn branch command failed. Command output: svn: Commit failed (details follow): svn: File '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/pom.xml' already exists Thanks you, Peter Nedonosko, eXo Platform SAS -- .. 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: local repository grows indefinitely on CI server
Aren't you using i your build a bogus version of the enforcer plugin. 1.0-alpha-3 has such a bug (MENFORCER-11) which forced to download dependencies. Arnaud On Thu, Sep 25, 2008 at 1:55 AM, Craig [EMAIL PROTECTED] wrote: Our CI server builds and deploys snapshots to our nexus repository server every time someone commits. During the build of a snapshot multi-module project, it downloads the previous snapshots of the modules to the local repository, even though they are in the reactor about to be built. This has the effect of causing the local repository to very quickly increase in size, containing every snapshot ever built. I can easily create a cron job to clean these up, but it does seem like incorrect behaviour on the part of maven (version 2.0.9). Will the resolution of this issue http://jira.codehaus.org/browse/MNG-3685 (Dependency can't be resolved but has been found in the reactor) fix my problem? thanks. Craig - 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: Status of repo1.maven.org
What is your problem. the repo is up. On Fri, Oct 31, 2008 at 6:19 PM, Clark, Michael [EMAIL PROTECTED]wrote: Does anyone know what he status of repo1.maven.org is. It appears to be non-responsive. -Mclark -- .. 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 ...
How to fix maven-eclipse-plugin issues
Hi community, I noticed that there is a lot of activity on maven-eclipse-plugin jira. You proposed several patchs and added comments on several issues. Did you consider to use m2eclipse instead of this plugin ? If yes, and if you aren't able to use it, did you contact its team to say why We'll never be able with this plugin to have the same level of services than m2eclipse those this is important to help then to propose a nice integration between maven and eclipse. For those who have to use the maven-eclipse-plugin and are waiting for some fixes, did you vote for issues related to your problems ? I'll try to work on it soon and I'll fix those with the most important number of votes because there are more than 200 issues opened :-( https://jira.codehaus.org/browse/MECLIPSE?report=com.atlassian.jira.plugin.system.project:popularissues-panel For those who are giving patches. Thanks a lot but did you add in your patch some tests to validate the fix ? did you update the documentation if necessary ? It'll help a lot to apply them quickly. Thanks a lot for your help. -- .. 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: How to fix maven-eclipse-plugin issues
Hi Ivan, If you can add a little project as a testcase to reproduce the issue and to check that the patch fixes it, it will help me. I'll add it in our integration tests. Cheers. On Fri, Oct 24, 2008 at 3:19 PM, IvanPopov [EMAIL PROTECTED] wrote: Hi Arnaud, The m2eclipse makes my eclipse unstable and really slow, so I prefer to use the maven-eclipse-plugin. I have one open issue on the maven-eclipse-plugin that is http://jira.codehaus.org/browse/MECLIPSE-490. The patch I propose is really basic, just to understand the issue. I have no idea how to make it clean but if you guide me I am able to do it. Thanks and regards. Arnaud HERITIER wrote: Hi community, I noticed that there is a lot of activity on maven-eclipse-plugin jira. You proposed several patchs and added comments on several issues. Did you consider to use m2eclipse instead of this plugin ? If yes, and if you aren't able to use it, did you contact its team to say why We'll never be able with this plugin to have the same level of services than m2eclipse those this is important to help then to propose a nice integration between maven and eclipse. For those who have to use the maven-eclipse-plugin and are waiting for some fixes, did you vote for issues related to your problems ? I'll try to work on it soon and I'll fix those with the most important number of votes because there are more than 200 issues opened :-( https://jira.codehaus.org/browse/MECLIPSE?report=com.atlassian.jira.plugin.system.project:popularissues-panel For those who are giving patches. Thanks a lot but did you add in your patch some tests to validate the fix ? did you update the documentation if necessary ? It'll help a lot to apply them quickly. Thanks a lot for your help. -- .. 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 ... -- View this message in context: http://www.nabble.com/How-to-fix-maven-eclipse-plugin-issues-tp20149724p20149971.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] -- .. 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: New to Maven - need help
You'll have more information in : - http://www.sonatype.com/community/definitive_guide.html - http://www.exist.com/better-build-maven Arnaud On Tue, Oct 14, 2008 at 12:54 PM, Jan K [EMAIL PROTECTED] wrote: I am very new to maven.I have downloaded apache-maven-2.0.9.I read the doc's and installed maven. I executed the following commands in command prompt, mvn archetype:create \ -DarchetypeGroupId=org.apache.maven.archetypes \ -DgroupId=com.mycompany.app \ -DartifactId=my-app I got a folder as my-app in my local path.I can see the pom.xml.Please help me what should i do next?How to change it the project i am willing to run? -- View this message in context: http://www.nabble.com/New-to-Maven---need-help-tp19971205p19971205.html Sent from the Maven - Users mailing list archive at Nabble.com. -- .. 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: Grails Maven plugin
Did you used this one : http://forge.octo.com/maven/sites/mtg/grails-maven-plugin/index.html ??? Arnaud On Tue, Oct 14, 2008 at 12:01 AM, Ed [EMAIL PROTECTED] wrote: I asked this on the Grails user list, and haven't gotten any resolution yet, so I'm posting here too. Hope no one minds. I'm concerned about the size of my grails projects, and I'm wondering if the use of the grails maven plugin will allow me to keep my jar files in my repositories rather than in the lib directory and the plugins directories. The dependencies I'd need would be specified in the pom as is normal for maven projects, and kept either in a local repository or proxy. This way, when I check in to svn it's much smaller and when I check out and build it builds against the dependencies in the repository, rather than keeping it in the project itself. I tried to specify some of the jar files in the dependency list of the pom file, but they didn't resolve, even though I made sure that the groupId and artifactId matched what was in iblio or other repos. Thanks, -- Ed -- .. 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: how to remove de default task in the life phase?
In maven 1 projects you can use maven 2 ant tasks http://maven.apache.org/ant-tasks.html cheers Arnaud 2008/10/7 陈思淼 [EMAIL PROTECTED] our company have a own build tool derived from maven 1.0, and have lots of our own features, after few year we decide to transfer our works to maven 2.0 and contribute some tools to the community. now the maven 2.0 and our own build tool are exist togother, we must transfer project by project to the new maven 2.0 repository. but for maven project .we must to commit our artifactory to the old repository format and then use a tool to tranform all the repository to the maven repository. here is our situation. 2008/10/7 Brett Porter [EMAIL PROTECTED] it is not presently possible to remove lifecycle phases, other than creating your own lifecycle, or disabling a plugin through configuration (like as is done with the surefire plugin). Perhaps it would be better to discuss what your need is for a different deployment plugin? - Brett 2008/10/7 陈思淼 [EMAIL PROTECTED]: for example. when I runmvn deploy I want to deploy the artifactory to my own reposition use my own deploy-plugin ,but the phase must run the default maven-delploy-plugin, is there any method I can replace the default plugin and use my own plugin ? -- Brett Porter Blog: http://blogs.exist.com/bporter/ -- .. 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: where to get the SVN url of maven source code?
https://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.9/ Arnaud On Thu, Sep 18, 2008 at 1:39 PM, 陈思淼 [EMAIL PROTECTED] wrote: Im trying to get use mvnDebug and the the source code of maven ,my maven version is Maven version: 2.0.9, Who can tell me where to get the according source code of it? thanks! -- .. 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: NPE using eclipse:install-plugins
perfect thx On Wed, Sep 17, 2008 at 1:07 AM, Barrie Treloar [EMAIL PROTECTED] wrote: Then this jar will be included in the project without any problem. I really think it's better. And obviously, I'll be happy to manually test the new version once the modification is applied. Fixed, with unit test as well. I just created a zip file with no manifest and renamed to jar. - 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: NPE using eclipse:install-plugins
units tests and integration tests passed on my laptop (mac os x) I'll do more checks on existing projects at work (for my personal devs I'm more often using m2eclipse) cheers arnaud On Wed, Sep 17, 2008 at 4:18 AM, Barrie Treloar [EMAIL PROTECTED] wrote: On Wed, Sep 17, 2008 at 9:08 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote: perfect thx I'd feel happier if you could check it works in your envionment. I've build and tested on my windows xp box and on minotaur, but since I'm just tinkering around the edges I'm not confident I haven't stuffed something up. Cheers. - 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: AW: Release fails during SVN commit
. - 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] -- .. 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
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 ...
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
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 ...
Re: Maven and Eclipse Project
using the workspace property the eclipse plugin can find references to others projects and link them. Otherwise without having an inheritence but a reactor pom with 3 modules will also link them together. On Thu, Aug 21, 2008 at 4:51 PM, Lam Hayward [EMAIL PROTECTED]wrote: Hi there, I have an issue with maven classpath generation (mvn eclipse:eclipse) for eclipse. I have 3 independent projects (say A, B and C) with no common root. Project A is the common project (jar) which project B and C will include. In pom.xml in project B and project C, there is a dependency defined for A. However, in eclipse, I'd like to have project B and project C to include the project A as reference project instead of the jar. Is this possible without using the project hierarchy approach? HL - 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: Release fails during SVN commit
I have the same issue on Leopard with svn 1.5 As a workaround I have to checkout the trunk of the project just before to do the release and it works. Arnaud On Thu, Aug 21, 2008 at 5:07 PM, Beyer,Nathan [EMAIL PROTECTED] wrote: Does your POM have any SVN keyword substitutions in it? For example $Id$ or $Revision$? I have had issues with releases that at the root was a file locking problem that I was able to alleviate by removing the keywords substitutions. -Nathan -Original Message- From: Andreas Heinecke [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 3:04 AM To: users@maven.apache.org Subject: 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] -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. - 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: [PLEASE TEST] Maven 2.0.10-RC9
or critical issues we may have missed BEFORE we do the release, instead of having to put up with major flaws for another release cycle. Please, if you have the time, take 2.0.10-RC9 for a spin and tell us what you think! Thanks, -john P.S. To see the list of issues that were closed for this release (so far), check out: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 -- 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] -- 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] -- 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] -- .. 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: Error while executing Maven javadoc
I deployed a new snapshot. Can you check if it changes something ? On Mon, Aug 11, 2008 at 11:20 PM, EJ Ciramella [EMAIL PROTECTED]wrote: What is really interesting is running javadoc directly produces NO errors. When run from mvn site, these errors show up. I don't even see a 2.5 branch for the javadoc plugin in the source repo, anyone care to comment on this issue? -Original Message- From: Michael Delaney [mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2008 12:36 PM To: Maven Users List Subject: Error while executing Maven javadoc All, There seems to have been a new maven Javadoc plug-in uploaded that is causing some issues on our side. Is anyone else seeing this issue? We are using Maven 2.0.9 and this is encountered during the call 'mvn site install' [ Console Errors ] Downloading: http://build.corp.upromise.com:8080/archiva/repository/internal//org/apa che/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin -2.5-20080810.123323-30.pom 17Khttp://build.corp.upromise.com:8080/archiva/repository/internal//org/apache/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin-2.5-20080810.123323-30.pom17Kdownloaded Downloading: http://build.corp.upromise.com:8080/archiva/repository/bertha//org/apach e/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin-2 .5-20080810.123323-30.jarhttp://build.corp.upromise.com:8080/archiva/repository/bertha//org/apache/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin-2.5-20080810.123323-30.jar Downloading: http://build.corp.upromise.com:8080/archiva/repository/internal//org/apa che/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin -2.5-20080810.123323-30.jar 114Khttp://build.corp.upromise.com:8080/archiva/repository/internal//org/apache/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin-2.5-20080810.123323-30.jar114Kdownloaded [WARNING] Attempting to build MavenProject instance for Artifact (org.apache.maven.plugins:maven-javadoc-plugin:2.5-20080810.123323-30) of type: maven-plugin; constructing POM artifact instead. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Unresolved compilation problems: Syntax error, insert } to complete ClassBody The method append(StringBuffer, String, int) is undefined for the type HelpMojo ... repeating ... The method append(StringBuffer, String, int) is undefined for the type HelpMojo Syntax error, insert } to complete Block Syntax error, insert else Statement to complete IfStatement Syntax error, insert } to complete MethodBody Syntax error, insert else Statement to complete IfStatement Syntax error, insert ) to complete MethodInvocation Syntax error, insert ; to complete Statement Syntax error, insert } to complete Block - 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: Setting output folders in Eclipse
No Arnaud On Wed, Jul 23, 2008 at 3:52 AM, Pierre Thibault [EMAIL PROTECTED] wrote: Hello, Is it possible to set the output folders for different source folders when creating the Eclipse project with 'mvn eclipse:eclipse'? Pierre __ Get the name you've always wanted @ymail.com or @rocketmail.com! Go to http://ca.promos.yahoo.com/jacko/ -- .. 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: Maven definitive guide parent POM child POM example: creates modules jar and war but not jar in war?
you have to had in the war project a dependency to the jar project. Arnaud On Tue, Jul 22, 2008 at 10:33 PM, David Brown [EMAIL PROTECTED] wrote: Hello maven gurus, users and mere mortals. I have a parent POM similar to the maven definitive guide multi-module example. The parent POM locates the the child POMs as expected. Both modules are built correctly: 1 (dot).war file and 1 (dot).jar file but the (dot).jar is not included in the (dot).war file. How-to complete this step of the POM? Please advise, David Yet some, not wise, go to the other side of the globe, to barbarous and unhealthy regions, and devote ten or twenty years, in that they may live,-that is, keep comfortably warm,- and die in New England at last. Henry David Thoreau - Walden - 1845 - 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 ...
[ANN] Clirr Maven Plugin, version 2.2.2 released
The Mojo team is pleased to announce the release of the Maven Clirr Plugin, version 2.2.2 This plugin is used to check Java libraries for binary and source compatibility with older releases. http://mojo.codehaus.org/clirr-maven-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdclirr-maven-plugin/artifactId version2.2.2/version /plugin This release fixes one bug while analyzing your code : * MCLIRR-14: Fail's checking with a ClassNotFoundException followed by a NullPointerException Enjoy, -The Mojo team .. 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: Does the maven version prerequisite only apply to plugins, or not?
What I understood about this element : - it's not inherited, you have to define it in all modules - for any project/module, maven checks before to build if its own version is greater than the one in the prerequisite - for plugins, this value is also used in the update mechanism to check the compatibility. Arnaud On Thu, Jul 10, 2008 at 7:01 PM, Wendy Smoak [EMAIL PROTECTED] wrote: In the model [1], the prerequisitesmaven element is described as: prerequisites - Describes the prerequisites a project can have. Element Description maven The minimum version of Maven required to build the project, or to use this plugin. I thought this *only* applied to plugins, and seem to recall a recent commit where someone removed it from a non-plugin build. (Not that I can find it now...) The description implies that it also applies to generic projects. Which is correct? [1] http://maven.apache.org/ref/2.0.9/maven-model/maven.html#class_prerequisites Thanks, Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tip about Skinny Wars
My workaround is more a hack that something else. It's not really logical to have in a project to dependencies to a pom and a war of a same artifact. This is certainly a bug in the core of maven which doesn't support it :-( I'm trying to see how I can change the ear plugin to fix this issue. Arnaud On Tue, Jul 1, 2008 at 2:58 PM, Martin Höller [EMAIL PROTECTED] wrote: Hi Arnaud! I think I found one BIG problem with your workaround: it only works if you already have (the latest version of) your WAR's pom.xml file in the repository, otherwise maven 2.0.9 reports a missing dependency. So this approach is not useable with the maven-release-plugin :-( I made up a simple test project consisting of a parent and three modules: myJar, myWar, and myEar. myEar depends on myWar and myWar depends on myJar. With your approach and an empty repository the build fails due to a missing myWar:pom dependency. As I think this list doesn't allow attachments I've made the sample available at http://www.xss.co.at/~martin/tmp/m2-skinny-war-demo.tar.bz2http://www.xss.co.at/%7Emartin/tmp/m2-skinny-war-demo.tar.bz2 A 'mvn package' fails, while a 'mvn install' succeeds. Any comments? - martin On Tuesday 03 June 2008 Arnaud HERITIER wrote: Hi all, I would like to share with you a workaround I found for the problem of transitive dependencies in skinny wars. In the documentation it is said that : Now the painful part. Your EAR's pom.xml needs to list every dependency that the WAR has. This is because Maven assumes fat WARs and does not include transitive dependencies of WARs within the EAR. A workaround of this is to define for each war 2 dependencies. One for the war itself and another for the war's pom to retrieve transitive dependencies. With that you'll have something like that in your ear dependencies : dependencies dependency groupIdcom.acme/groupId artifactIdwar1/artifactId version1.0.0/version typewar/type /dependency dependency groupIdcom.acme/groupId artifactIdwar1/artifactId version1.0.0/version typepom/type /dependency /dependencies I'm using maven 2.0.9. I'll do more tests tomorrow and I'll update the doc : http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.htm l Cheers arnaud
Re: Replacement of WAR lifecycle
I had a similar issue and I added the parameter packaging in the maven-eclipse-plugin to use a custom packaging but to have the behavior of another one. http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#packaging The problem is that in maven 2.0.X we don't have actually an inheritence of packaging. Arnaud On Tue, Jun 24, 2008 at 10:54 AM, Piotr Oktaba [EMAIL PROTECTED] wrote: Hi, I have following problem. I would like to write my own maven2 war plugin with my own lifecycle. Currently available maven-war-plugin does not fit my requirements. I have chosen war packaging instead of my own (for example portal) because I do not want to lose support from other tools (for example maven plugin for netbeans or maven-eclipse-plugin - the last one doesn't generate project if packaging is non standard). However, only way of replacement war lifecycle which I have found is commenting part of components.xml file in uberjar file in maven2 installation and provide my own component definition in plugin. Is there any more ellegant solution than commenting that file? Cheers, Piotr Oktaba
Re: Maven and RAD 7
Hi gabriel. M2_REPO entries are created from your dependencies with eclipse:eclipse, eclipse:rad, and others mojos. We created a mojo eclipse:m2eclipse to create a classpath without these entries but with the org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER entry used by the m2eclipse plugin. We don't have actually a support for RAD and m2eclipse. You can open an issue but I don't know when I'll have the time to work on it. ou can also ask to the m2eclipse plugin team to improve the support for RAD. cheers arnaud On Mon, Jun 23, 2008 at 5:55 PM, [EMAIL PROTECTED] wrote: Hi Arnaud, how are you doing? I found a post where you've answered about the eclipse:rad plugin. ( http://www.mail-archive.com/users@maven.apache.org/msg66951.html) I'm trying to use the eclipse:rad plugin to generate the .classpath and .project for my RAD7 projects but I couldn't figure out how to remove the M2_REPO individual entries on my .classpath as you can see below: classpath classpathentry kind=src path=src/ classpathentry kind=src path=src/main/resources excluding=**/*.java/ classpathentry kind=src path=target/generated-resources/rad6 excluding=**/*.java/ classpathentry kind=output path=target/classes/ classpathentry kind=var path=M2_REPO/javax/xml/jax-qname/1.1/jax-qname-1.1.jar/ classpathentry kind=var path=M2_REPO/javax/xml/bind/jaxb-api/1.0.1/jaxb-api-1.0.1.jar/ classpathentry kind=var path=M2_REPO/javax/xml/jaxb-impl/1.0.2/jaxb-impl-1.0.2.jar/ classpathentry kind=var path=M2_REPO/javax/xml/jaxb-libs/1.0.2/jaxb-libs-1.0.2.jar/ classpathentry kind=var path=M2_REPO/javax/xml/jaxb-xjc/1.0.2/jaxb-xjc-1.0.2.jar/ classpathentry kind=var path=M2_REPO/javax/xml/namespace/1.0.1/namespace-1.0.1.jar/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=con path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/ classpathentry kind=var path=M2_REPO/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar sourcepath=M2_REPO/dom4j/dom4j/1.6.1/dom4j-1.6.1-sources.jar/ classpathentry kind=var path=M2_REPO/relaxngDatatype/relaxngDatatype/20020414/relaxngDatatype-20020414.jar sourcepath=M2_REPO/relaxngDatatype/relaxngDatatype/20020414/relaxngDatatype-20020414-sources.jar/ classpathentry kind=var path=M2_REPO/com/sun/msv/datatype/xsd/xsdlib/20060615/xsdlib-20060615.jar/ /classpath From the file above, I only need this: ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=con path=org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/ classpathentry kind=output path=bin/ /classpath Could you please help me to figure out how could I configure the eclipse:rad plugin in order to generate the file above? My current plugin configuration are like: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId configuration buildcommands buildcommand org.eclipse.jdt.core.javabuilder /buildcommand buildcommand org.maven.ide.eclipse.maven2Builder /buildcommand /buildcommands projectnatures projectnature org.eclipse.jdt.core.javanature /projectnature projectnature org.maven.ide.eclipse.maven2Nature /projectnature /projectnatures classpathContainers classpathContainer org.eclipse.jdt.launching.JRE_CONTAINER /classpathContainer classpathContainer org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER /classpathContainer /classpathContainers /configuration /plugin I'm looking forward your feedbacks... Best Regards... Gabriel Pereira Borges Lenovo Care Center Support Transition - Java Specialist Phoenix II Migration to zLinux Environment Global Business Services - IBM Brazil Phone: +55-19-2118-7238 [EMAIL PROTECTED] Sun Certified Java Programmer (SCJP) Sun Certified Web Component Developer (SCWCD)
Re: Tip about Skinny Wars
Not totally. It can fix : Automatically inherit transitive dependencies from the war artifact (the default Maven behaviour is not to inherit transitively from war dependencies). But not : Develop with classes included in the war artifact /WEB-INF/classes directory by including them in the project classpath. Arnaud On Wed, Jun 4, 2008 at 11:17 AM, Milos Kleint [EMAIL PROTECTED] wrote: i'm wondering if the solution would render the war-path plugin obsolete? it's causing trouble in embedded use. http://issues.appfuse.org/browse/APF-645 Milos On 6/3/08, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi all, I would like to share with you a workaround I found for the problem of transitive dependencies in skinny wars. In the documentation it is said that : Now the painful part. Your EAR's pom.xml needs to list every dependency that the WAR has. This is because Maven assumes fat WARs and does not include transitive dependencies of WARs within the EAR. A workaround of this is to define for each war 2 dependencies. One for the war itself and another for the war's pom to retrieve transitive dependencies. With that you'll have something like that in your ear dependencies : dependencies dependency groupIdcom.acme/groupId artifactIdwar1/artifactId version1.0.0/version typewar/type /dependency dependency groupIdcom.acme/groupId artifactIdwar1/artifactId version1.0.0/version typepom/type /dependency /dependencies I'm using maven 2.0.9. I'll do more tests tomorrow and I'll update the doc : http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html Cheers arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-(
I made additional tests and I found that it is another side effect of the usage of the enforcer plugin (build from trunk rev 651824). :-( I will have a look at its code to see if this bug of the enforcer plugin can become a feature in the war plugin ;-) Arnaud On Tue, Jun 3, 2008 at 7:31 PM, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi all, I would like to share with you a workaround I found for the problem of transitive dependencies in skinny wars. In the documentation it is said that : Now the painful part. Your EAR's pom.xml needs to list every dependency that the WAR has. This is because Maven assumes fat WARs and does not include transitive dependencies of WARs within the EAR. A workaround of this is to define for each war 2 dependencies. One for the war itself and another for the war's pom to retrieve transitive dependencies. With that you'll have something like that in your ear dependencies : dependencies dependency groupIdcom.acme/groupId artifactIdwar1/artifactId version1.0.0/version typewar/type /dependency dependency groupIdcom.acme/groupId artifactIdwar1/artifactId version1.0.0/version typepom/type /dependency /dependencies I'm using maven 2.0.9. I'll do more tests tomorrow and I'll update the doc : http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html Cheers arnaud
Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-(
I think it is not the same problem. MWAR-131 is about to reuse classes defined in a war. attachClasses will generate a secondary artifact that we'll be able to reuse as dependency in another project. The problem for skinny WARs is that EARs didn't package WARs transitive dependencies. It's not about classes bundled in the war (which are always in the war). Arnaud On Wed, Jun 4, 2008 at 4:20 PM, Mark Struberg [EMAIL PROTECTED] wrote: Hi Arnaud! The maven-war-plugin already has a similar mechanism with attachClassestrue/attachClasses, but this hasn't yet been released. As I wrote in my previous mail: see MWAR-131 (and partly obsolete MWAR-73) for further details. This workaround should also work in conjunction with the maven-ear-plugin. LieGrü, strub --- Arnaud HERITIER [EMAIL PROTECTED] schrieb am Mi, 4.6.2008: Von: Arnaud HERITIER [EMAIL PROTECTED] Betreff: Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-( An: Maven Users List users@maven.apache.org CC: Maven Developers List [EMAIL PROTECTED] Datum: Mittwoch, 4. Juni 2008, 15:28 I made additional tests and I found that it is another side effect of the usage of the enforcer plugin (build from trunk rev 651824). :-( I will have a look at its code to see if this bug of the enforcer plugin can become a feature in the war plugin ;-) Arnaud On Tue, Jun 3, 2008 at 7:31 PM, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi all, I would like to share with you a workaround I found for the problem of transitive dependencies in skinny wars. In the documentation it is said that : Now the painful part. Your EAR's pom.xml needs to list every dependency that the WAR has. This is because Maven assumes fat WARs and does not include transitive dependencies of WARs within the EAR. A workaround of this is to define for each war 2 dependencies. One for the war itself and another for the war's pom to retrieve transitive dependencies. With that you'll have something like that in your ear dependencies : dependencies dependency groupIdcom.acme/groupId artifactIdwar1/artifactId version1.0.0/version typewar/type /dependency dependency groupIdcom.acme/groupId artifactIdwar1/artifactId version1.0.0/version typepom/type /dependency /dependencies I'm using maven 2.0.9. I'll do more tests tomorrow and I'll update the doc : http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html Cheers arnaud __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-(
ok I didn't think about that. It can be a usable workaround. Thx Arnaud On Wed, Jun 4, 2008 at 6:08 PM, Jörg Schaible [EMAIL PROTECTED] wrote: Hi Arnaud, Arnaud HERITIER wrote: I think it is not the same problem. MWAR-131 is about to reuse classes defined in a war. attachClasses will generate a secondary artifact that we'll be able to reuse as dependency in another project. Yes, this other project might be the ear ... The problem for skinny WARs is that EARs didn't package WARs transitive dependencies. It's not about classes bundled in the war (which are always in the war). ... and the attached jar will transport the transitive deps. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tip about Skinny Wars
Hi all, I would like to share with you a workaround I found for the problem of transitive dependencies in skinny wars. In the documentation it is said that : Now the painful part. Your EAR's pom.xml needs to list every dependency that the WAR has. This is because Maven assumes fat WARs and does not include transitive dependencies of WARs within the EAR. A workaround of this is to define for each war 2 dependencies. One for the war itself and another for the war's pom to retrieve transitive dependencies. With that you'll have something like that in your ear dependencies : dependencies dependency groupIdcom.acme/groupId artifactIdwar1/artifactId version1.0.0/version typewar/type /dependency dependency groupIdcom.acme/groupId artifactIdwar1/artifactId version1.0.0/version typepom/type /dependency /dependencies I'm using maven 2.0.9. I'll do more tests tomorrow and I'll update the doc : http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html Cheers arnaud
Re: Announcing Grails Maven Plugin 0.3
In fact it's only the 0.3 ;-) Arnaud On Mon, Jun 2, 2008 at 1:53 PM, Trygve Laugstøl [EMAIL PROTECTED] wrote: The third release of the grails-maven-plugin is now available. You'll find the full list of changes in [jira| http://forge.octo.com/jira/secure/ReleaseNote.jspa?projectId=10120styleName=Htmlversion=10332 ] A lot of small bugs has been fixed and a few improvements has been implemented. As more users are using the Grails integration, more use-cases are discovered and integrated into the plugin. If you have a particular feature that you want to get in the plugin, don't hesitate to create issues in JIRA. JIRA: http://forge.octo.com/jira/browse/MTG Mailing list: Send an email with the subject subscribe mtg to [EMAIL PROTECTED] or just press [here|mailto:[EMAIL PROTECTED] ?subject=subscribe%20mtg] Have Fun with Grails+Maven. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
