Eclipse Tools for Maven Development
Hi, Anyone who has every tried, or is considering trying, developing a Maven plugin, extension, or feature will want to have a look at our Eclipse Tools for Maven Development[1]. It basically allows you to run and debug anything related to Maven from within the Eclipse workspace without having to install anything in the local repository. No remote debugging sessions, no trying to fiddle around on the command line. You can debug a dynamically loaded extension, you ran run a Maven IT through its execution right into core. It's extremely handy and actually makes it possible for someone relatively new be effective with Maven and makes people with some familiarity even more effective. I haven't tried to develop a Maven plugin, extension or feature without these tools for years as I find it generally futile. If you do Maven development and happen to use Eclipse do yourself a favour and watch the demo. [1]: http://takari.io/2015/01/27/maven-dev-tools.html Thanks, Jason -- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Three people can keep a secret provided two of them are dead. -- Benjamin Franklin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
@Baptiste, so I guess your vote is actually +1 to remove it from documentation, right? M2_HOME is automatically set by the shell or batch script. The M2_HOME variable is here used to easily switch between different Maven distributions. But with this name this can indeed cause NoClassDefFoundErrors. For the majority of the community it's not interesting to have multiple versions of Maven and to switch often. So this M2_HOME might be confusing. Instead just add apache-maven-3.x.x/bin to your path. You have my +1 for this change. Also, there's no need to add JAVA_HOME/bin to the path. Maven picks it up as an environment variable, it won't scan the path searching for the java executable. So I'd like to see that removed as well. thanks, Robert Op Tue, 27 Jan 2015 10:04:28 +0100 schreef Baptiste Mathus m...@batmat.net: -1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Dependency Plugin version 2.10 (Take 2)
Hi, The vote has passed with the following result: +1 (binding): Jason van Zyl, Rober Scholte, Karl Heinz Marbaise +1 (non binding): Anders Hammar I will promote the artifacts to the central repo. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
Hi Benson, What is your verdict? Thanks -D On Tue, Jan 27, 2015 at 3:15 AM, Benson Margulies bimargul...@gmail.com wrote: I know of two cases where it comes up. 1: some of our own ITs. Those aren't a reason for comprehensive doc. 2: an application I wrote for Aether :-) On Tue, Jan 27, 2015 at 4:04 AM, Baptiste Mathus m...@batmat.net wrote: -1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
Hi Benson By many tests are you refer to the incident at release plugin 2.5.1, or maven-core IT Thanks -D On Tue, Jan 27, 2015 at 10:28 AM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Jan 27, 2015 at 1:16 PM, Dan Tran dant...@gmail.com wrote: Hi Benson, What is your verdict? I vote for removing it from the publically facing doc. is there also a thought of removing it from the code? I guess if someone makes sure that all our many tests pass without it, fine with me. I should explain my passing reference to Aether. I wrote a little OSGi utility that uses Aether to fetch some dependencies, and I wanted it to get mirror definitions out of, well, $M2_HOME/conf/settings.xml. That probably counts as acute sloth on my part. Thanks -D On Tue, Jan 27, 2015 at 3:15 AM, Benson Margulies bimargul...@gmail.com wrote: I know of two cases where it comes up. 1: some of our own ITs. Those aren't a reason for comprehensive doc. 2: an application I wrote for Aether :-) On Tue, Jan 27, 2015 at 4:04 AM, Baptiste Mathus m...@batmat.net wrote: -1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
On Tue, Jan 27, 2015 at 2:10 PM, Dan Tran dant...@gmail.com wrote: Hi Benson By many tests are you refer to the incident at release plugin 2.5.1, or maven-core IT I'm guessing that the M-R-P integration tests are not the only plugin integration tests that care. I'm pretty sure I've run into this before. Thanks -D On Tue, Jan 27, 2015 at 10:28 AM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Jan 27, 2015 at 1:16 PM, Dan Tran dant...@gmail.com wrote: Hi Benson, What is your verdict? I vote for removing it from the publically facing doc. is there also a thought of removing it from the code? I guess if someone makes sure that all our many tests pass without it, fine with me. I should explain my passing reference to Aether. I wrote a little OSGi utility that uses Aether to fetch some dependencies, and I wanted it to get mirror definitions out of, well, $M2_HOME/conf/settings.xml. That probably counts as acute sloth on my part. Thanks -D On Tue, Jan 27, 2015 at 3:15 AM, Benson Margulies bimargul...@gmail.com wrote: I know of two cases where it comes up. 1: some of our own ITs. Those aren't a reason for comprehensive doc. 2: an application I wrote for Aether :-) On Tue, Jan 27, 2015 at 4:04 AM, Baptiste Mathus m...@batmat.net wrote: -1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
On Tue, Jan 27, 2015 at 1:16 PM, Dan Tran dant...@gmail.com wrote: Hi Benson, What is your verdict? I vote for removing it from the publically facing doc. is there also a thought of removing it from the code? I guess if someone makes sure that all our many tests pass without it, fine with me. I should explain my passing reference to Aether. I wrote a little OSGi utility that uses Aether to fetch some dependencies, and I wanted it to get mirror definitions out of, well, $M2_HOME/conf/settings.xml. That probably counts as acute sloth on my part. Thanks -D On Tue, Jan 27, 2015 at 3:15 AM, Benson Margulies bimargul...@gmail.com wrote: I know of two cases where it comes up. 1: some of our own ITs. Those aren't a reason for comprehensive doc. 2: an application I wrote for Aether :-) On Tue, Jan 27, 2015 at 4:04 AM, Baptiste Mathus m...@batmat.net wrote: -1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
IMO, M2_HOME is no longer a required env starting 2.2.1, and there for it is used mainly for the exact use case that Manfred mentioned. I myself use a set a wrapper scripts ( mvn221, mvn311, etc) since it is much easier to remember. I also got bitten a number of times where user had M2_HOME set, and install new version of Maven without reset M2_HOME, and fail mysteriously (support call) here is the link to Benson's issue, it is not conclusive http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-Release-Plugin-version-2-5-1-td5805498.html -Dan On Mon, Jan 26, 2015 at 10:47 PM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: I seem to recall Benson ran into a case with either release or site where it was still required no too long ago ? Kristian 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] maven pull request: fix apple jdk detection
Github user makigumo commented on the pull request: https://github.com/apache/maven/pull/24#issuecomment-71620924 fixed in fbd6e53e838d3c77d689adeae19fa6de6ecc050f --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] maven pull request: fix apple jdk detection
Github user makigumo closed the pull request at: https://github.com/apache/maven/pull/24 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
-1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;!
Re: Remove M2_HOME setup from download page instructions
You sure you linked the right commit? The commit you linked is from my experimental branch and it does not change how mvn* scripts use M2_HOME environment variable. -- Regards, Igor On 2015-01-27 16:26, Dan Tran wrote: Just see this change [1] at Maven core where the 'mvn' script get altered. Not sure about the impact of this change when using M2_HOME to support multiple is distributions. -Dan [1] https://git1-us-west.apache.org/repos/asf?p=maven.git;a=commitdiff;h=0a76e91b On Tue, Jan 27, 2015 at 11:38 AM, Dan Tran dant...@gmail.com wrote: Strange I don't have a problem with maven-release build running with -Prun-its -D On Tue, Jan 27, 2015 at 11:20 AM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Jan 27, 2015 at 2:10 PM, Dan Tran dant...@gmail.com wrote: Hi Benson By many tests are you refer to the incident at release plugin 2.5.1, or maven-core IT I'm guessing that the M-R-P integration tests are not the only plugin integration tests that care. I'm pretty sure I've run into this before. Thanks -D On Tue, Jan 27, 2015 at 10:28 AM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Jan 27, 2015 at 1:16 PM, Dan Tran dant...@gmail.com wrote: Hi Benson, What is your verdict? I vote for removing it from the publically facing doc. is there also a thought of removing it from the code? I guess if someone makes sure that all our many tests pass without it, fine with me. I should explain my passing reference to Aether. I wrote a little OSGi utility that uses Aether to fetch some dependencies, and I wanted it to get mirror definitions out of, well, $M2_HOME/conf/settings.xml. That probably counts as acute sloth on my part. Thanks -D On Tue, Jan 27, 2015 at 3:15 AM, Benson Margulies bimargul...@gmail.com wrote: I know of two cases where it comes up. 1: some of our own ITs. Those aren't a reason for comprehensive doc. 2: an application I wrote for Aether :-) On Tue, Jan 27, 2015 at 4:04 AM, Baptiste Mathus m...@batmat.net wrote: -1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
Just see this change [1] at Maven core where the 'mvn' script get altered. Not sure about the impact of this change when using M2_HOME to support multiple is distributions. -Dan [1] https://git1-us-west.apache.org/repos/asf?p=maven.git;a=commitdiff;h=0a76e91b On Tue, Jan 27, 2015 at 11:38 AM, Dan Tran dant...@gmail.com wrote: Strange I don't have a problem with maven-release build running with -Prun-its -D On Tue, Jan 27, 2015 at 11:20 AM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Jan 27, 2015 at 2:10 PM, Dan Tran dant...@gmail.com wrote: Hi Benson By many tests are you refer to the incident at release plugin 2.5.1, or maven-core IT I'm guessing that the M-R-P integration tests are not the only plugin integration tests that care. I'm pretty sure I've run into this before. Thanks -D On Tue, Jan 27, 2015 at 10:28 AM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Jan 27, 2015 at 1:16 PM, Dan Tran dant...@gmail.com wrote: Hi Benson, What is your verdict? I vote for removing it from the publically facing doc. is there also a thought of removing it from the code? I guess if someone makes sure that all our many tests pass without it, fine with me. I should explain my passing reference to Aether. I wrote a little OSGi utility that uses Aether to fetch some dependencies, and I wanted it to get mirror definitions out of, well, $M2_HOME/conf/settings.xml. That probably counts as acute sloth on my part. Thanks -D On Tue, Jan 27, 2015 at 3:15 AM, Benson Margulies bimargul...@gmail.com wrote: I know of two cases where it comes up. 1: some of our own ITs. Those aren't a reason for comprehensive doc. 2: an application I wrote for Aether :-) On Tue, Jan 27, 2015 at 4:04 AM, Baptiste Mathus m...@batmat.net wrote: -1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Apache Maven Dependency Plugin Version 2.10 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Dependecy Plugin, version 2.10 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.10/version /plugin Release Notes - Maven Dependency Plugin - Version 2.10 Bugs: * [MDEP-109] - Dependency plugin loses file permissions when unpacking or copying artifact items * [MDEP-242] - Exclude does not work correctly for tar.gz (but is working for zip) * [MDEP-397] - When using unpack-dependencies with a zip created on unixes, contained symlinks aren't correctly unpackaged * [MDEP-436] - German umlauts in outputDirectory and destFileName getting garbled * [MDEP-466] - analyze fails on multimodule project (regression) Improvements: * [MDEP-465] - Update version of plexus-archiver from 2.4.4 to 2.9 * [MDEP-467] - Update plexus-io from 2.0.9 to 2.2 * [MDEP-472] - Upgrade to maven-plugins parent version 27 New Feature: * [MDEP-476] - add the ability to ignore dependencies in the analyze-* goals Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Fw: Build failed in Jenkins: core-it-maven-3-win
Hello, the core-it-maven-3-win are failing because of some get setup problem (it seems). The job sent a lot of failed mail messages. It looks like I do get a copy because one of my patches was commited meanwhile. Can somebody have a look? Gruss Bernd -- Datum: Mon, 26 Jan 2015 23:27:07 + (UTC) Von: Apache Jenkins Server jenk...@builds.apache.org An: notificati...@maven.apache.org, be...@eckenfels.net Betreff: Build failed in Jenkins: core-it-maven-3-win #746 See https://builds.apache.org/job/core-it-maven-3-win/746/ -- Started by an SCM change Building remotely on windows1 (Windows) in workspace https://builds.apache.org/job/core-it-maven-3-win/ws/ git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository git config remote.origin.url https://git-wip-us.apache.org/repos/asf/maven.git # timeout=10 FATAL: Failed to fetch from https://git-wip-us.apache.org/repos/asf/maven.git hudson.plugins.git.GitException: Failed to fetch from https://git-wip-us.apache.org/repos/asf/maven.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:647) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:889) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:914) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Caused by: hudson.plugins.git.GitException: Command git config remote.origin.url https://git-wip-us.apache.org/repos/asf/maven.git; returned status code 4: stdout: stderr: error: could not commit config file .git/config at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1435) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1411) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1407) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1110) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1120) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.setRemoteUrl(CliGitAPIImpl.java:832) at hudson.plugins.git.GitAPI.setRemoteUrl(GitAPI.java:120) at sun.reflect.GeneratedMethodAccessor801.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:310) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
On 2015-01-27 17:35, Dan Tran wrote: My bad, it is not obvious it is from an experimental branch. However, even if this gets committed master, the configuration changes in that script may impact other distribution using M2_HOME. Can you explain how changes on that branch can impact other distributions using M2_HOME? The change is not supposed to affect M2_HOME in any way, so I must have overlooked something and want to correct it before I propose to merge this to master. -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Surefire Plugin does not handle workingDirectory in fork mode properly
Hi Tibor / Andreas, I found a time to address problem with unit test, will take a look at integration test tomorrow. https://github.com/norbertwnuk/maven-surefire/commit/44b6ffaddc93c34c3e76abd4ea5fd3b8d837a130 NW On Sun, Jan 25, 2015 at 1:32 AM, Tibor Digana tibordig...@apache.org wrote: Hi Norbert, I have updaated PR #82 with comment on GitHub. The Ubuntu builds fail. I would prefer keeping the test anyway. Try to find a solution for Ubuntu as well; otherwise use JUnit assumption statement assumeThat( os, anyOf( is( Windows ), is( Ubuntu1 ) ) ) in the particular IT method, possibly unit test. -- View this message in context: http://maven.40175.n5.nabble.com/Surefire-Plugin-does-not-handle-workingDirectory-in-fork-mode-properly-tp5824054p5824683.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
I switch between versions all the time; this is useful. Sent from my iPhone On 27/01/2015, at 4:47 PM, Manfred Moser manf...@mosabuam.com wrote: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
My bad, it is not obvious it is from an experimental branch. However, even if this gets committed master, the configuration changes in that script may impact other distribution using M2_HOME. Sorry, I am a little side track here. -D On Tue, Jan 27, 2015 at 2:07 PM, Igor Fedorenko i...@ifedorenko.com wrote: You sure you linked the right commit? The commit you linked is from my experimental branch and it does not change how mvn* scripts use M2_HOME environment variable. -- Regards, Igor On 2015-01-27 16:26, Dan Tran wrote: Just see this change [1] at Maven core where the 'mvn' script get altered. Not sure about the impact of this change when using M2_HOME to support multiple is distributions. -Dan [1] https://git1-us-west.apache.org/repos/asf?p=maven.git;a= commitdiff;h=0a76e91b On Tue, Jan 27, 2015 at 11:38 AM, Dan Tran dant...@gmail.com wrote: Strange I don't have a problem with maven-release build running with -Prun-its -D On Tue, Jan 27, 2015 at 11:20 AM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Jan 27, 2015 at 2:10 PM, Dan Tran dant...@gmail.com wrote: Hi Benson By many tests are you refer to the incident at release plugin 2.5.1, or maven-core IT I'm guessing that the M-R-P integration tests are not the only plugin integration tests that care. I'm pretty sure I've run into this before. Thanks -D On Tue, Jan 27, 2015 at 10:28 AM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Jan 27, 2015 at 1:16 PM, Dan Tran dant...@gmail.com wrote: Hi Benson, What is your verdict? I vote for removing it from the publically facing doc. is there also a thought of removing it from the code? I guess if someone makes sure that all our many tests pass without it, fine with me. I should explain my passing reference to Aether. I wrote a little OSGi utility that uses Aether to fetch some dependencies, and I wanted it to get mirror definitions out of, well, $M2_HOME/conf/settings.xml. That probably counts as acute sloth on my part. Thanks -D On Tue, Jan 27, 2015 at 3:15 AM, Benson Margulies bimargul...@gmail.com wrote: I know of two cases where it comes up. 1: some of our own ITs. Those aren't a reason for comprehensive doc. 2: an application I wrote for Aether :-) On Tue, Jan 27, 2015 at 4:04 AM, Baptiste Mathus m...@batmat.net wrote: -1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
If your changes are specific to 3.2.6, however If user has M2_HOME point to an older version MAVEN, would that be a problem? Thanks -D On Tue, Jan 27, 2015 at 3:01 PM, Igor Fedorenko i...@ifedorenko.com wrote: On 2015-01-27 17:35, Dan Tran wrote: My bad, it is not obvious it is from an experimental branch. However, even if this gets committed master, the configuration changes in that script may impact other distribution using M2_HOME. Can you explain how changes on that branch can impact other distributions using M2_HOME? The change is not supposed to affect M2_HOME in any way, so I must have overlooked something and want to correct it before I propose to merge this to master. -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
Strange I don't have a problem with maven-release build running with -Prun-its -D On Tue, Jan 27, 2015 at 11:20 AM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Jan 27, 2015 at 2:10 PM, Dan Tran dant...@gmail.com wrote: Hi Benson By many tests are you refer to the incident at release plugin 2.5.1, or maven-core IT I'm guessing that the M-R-P integration tests are not the only plugin integration tests that care. I'm pretty sure I've run into this before. Thanks -D On Tue, Jan 27, 2015 at 10:28 AM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Jan 27, 2015 at 1:16 PM, Dan Tran dant...@gmail.com wrote: Hi Benson, What is your verdict? I vote for removing it from the publically facing doc. is there also a thought of removing it from the code? I guess if someone makes sure that all our many tests pass without it, fine with me. I should explain my passing reference to Aether. I wrote a little OSGi utility that uses Aether to fetch some dependencies, and I wanted it to get mirror definitions out of, well, $M2_HOME/conf/settings.xml. That probably counts as acute sloth on my part. Thanks -D On Tue, Jan 27, 2015 at 3:15 AM, Benson Margulies bimargul...@gmail.com wrote: I know of two cases where it comes up. 1: some of our own ITs. Those aren't a reason for comprehensive doc. 2: an application I wrote for Aether :-) On Tue, Jan 27, 2015 at 4:04 AM, Baptiste Mathus m...@batmat.net wrote: -1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Enforcer version 1.4
Hi, just a single binding VOTE...;-) Kind regards Karl Heinz Marbaise On 1/27/15 6:54 PM, Karl Heinz Marbaise wrote: Hi, here i my +1... here we need at least two binding VOTE's ... Kind regards Karl Heinz Marbaise On 1/24/15 11:25 PM, Karl Heinz Marbaise wrote: Hi, We solved 34 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530version=19420 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MENFORCER%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1134/ https://repository.apache.org/content/repositories/maven-1134/org/apache/maven/enforcer/enforcer/1.4/enforcer-1.4-source-release.zip Source release checksum(s): enforcer-source-release.zip sha1: 56b47d9549ed74d02f1b23fd2ef674c66f658ee4 Staging site: http://maven.apache.org/enforcer-archives/enforcer-LATEST/index.html Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Remove M2_HOME setup from download page instructions
I know of two cases where it comes up. 1: some of our own ITs. Those aren't a reason for comprehensive doc. 2: an application I wrote for Aether :-) On Tue, Jan 27, 2015 at 4:04 AM, Baptiste Mathus m...@batmat.net wrote: -1 it's a problematic variable, removing it is a good idea IMO, and changing mvn version is indeed just a matter of updating your path. I've been hit many a time by an updated PATH pointing to a different mvn version than the one referenced by M2_HOME, which ends with NoClassDefFoundError or something like that IIRC. That's why I've personally been advising maven users I encounter to never ever set that variable for years. Cheers 2015-01-27 7:19 GMT+01:00 Anders Hammar and...@hammar.net: I would still suggest to make sure its documented somewhere. I find it incredibly useful to just change M2_HOME to simply switch Maven versions. +1, very useful but I guess it doesn't require the name M2_HOME. /Anders manfred Mirko Friedenhagen wrote on 26.01.2015 21:40: Dan, go ahead, I have not set this variable for years. Regards Mirko -- Sent from my mobile On Jan 27, 2015 5:52 AM, Dan Tran dant...@gmail.com wrote: Hi, Any objection to remove the need to setup M2_HOME env variable at maven download page? Thanks -Dan https://jira.codehaus.org/browse/MNGSITE-223 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! nbsp;! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Surefire Plugin does not handle workingDirectory in fork mode properly
Thanks, Norbert! Could you also create a new Pull-Request for it? Then I can fetch it more easily :-) Am Mittwoch, 28. Januar 2015 schrieb Norbert Wnuk : Link after pushing amended commit - https://github.com/norbertwnuk/maven-surefire/commit/d6a8af593fc03e12ecf2dc8047669472f7ca263b On Wed, Jan 28, 2015 at 3:10 AM, Norbert Wnuk norbertw...@gmail.com javascript:; wrote: Hi Tibor / Andreas, I found a time to address problem with unit test, will take a look at integration test tomorrow. https://github.com/norbertwnuk/maven-surefire/commit/44b6ffaddc93c34c3e76abd4ea5fd3b8d837a130 NW On Sun, Jan 25, 2015 at 1:32 AM, Tibor Digana tibordig...@apache.org javascript:; wrote: Hi Norbert, I have updaated PR #82 with comment on GitHub. The Ubuntu builds fail. I would prefer keeping the test anyway. Try to find a solution for Ubuntu as well; otherwise use JUnit assumption statement assumeThat( os, anyOf( is( Windows ), is( Ubuntu1 ) ) ) in the particular IT method, possibly unit test. -- View this message in context: http://maven.40175.n5.nabble.com/Surefire-Plugin-does-not-handle-workingDirectory-in-fork-mode-properly-tp5824054p5824683.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:;
Re: [VOTE] Release Apache Maven Enforcer version 1.4
Hi, here i my +1... here we need at least two binding VOTE's ... Kind regards Karl Heinz Marbaise On 1/24/15 11:25 PM, Karl Heinz Marbaise wrote: Hi, We solved 34 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530version=19420 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MENFORCER%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1134/ https://repository.apache.org/content/repositories/maven-1134/org/apache/maven/enforcer/enforcer/1.4/enforcer-1.4-source-release.zip Source release checksum(s): enforcer-source-release.zip sha1: 56b47d9549ed74d02f1b23fd2ef674c66f658ee4 Staging site: http://maven.apache.org/enforcer-archives/enforcer-LATEST/index.html Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Surefire Plugin does not handle workingDirectory in fork mode properly
Link after pushing amended commit - https://github.com/norbertwnuk/maven-surefire/commit/d6a8af593fc03e12ecf2dc8047669472f7ca263b On Wed, Jan 28, 2015 at 3:10 AM, Norbert Wnuk norbertw...@gmail.com wrote: Hi Tibor / Andreas, I found a time to address problem with unit test, will take a look at integration test tomorrow. https://github.com/norbertwnuk/maven-surefire/commit/44b6ffaddc93c34c3e76abd4ea5fd3b8d837a130 NW On Sun, Jan 25, 2015 at 1:32 AM, Tibor Digana tibordig...@apache.org wrote: Hi Norbert, I have updaated PR #82 with comment on GitHub. The Ubuntu builds fail. I would prefer keeping the test anyway. Try to find a solution for Ubuntu as well; otherwise use JUnit assumption statement assumeThat( os, anyOf( is( Windows ), is( Ubuntu1 ) ) ) in the particular IT method, possibly unit test. -- View this message in context: http://maven.40175.n5.nabble.com/Surefire-Plugin-does-not-handle-workingDirectory-in-fork-mode-properly-tp5824054p5824683.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
