Re: [VOTE] Release Apache Maven Clean Plugin version 2.6.1 and maven-shared-utils 0.7
+1 ( none binding) tested with my internal build on windows. Does it mean the clean task is faster due to NIO. My apology if i happen to hijack this thread. -D On Mon, Oct 13, 2014 at 1:34 PM, Kristian Rosenvold krosenv...@apache.org wrote: Hi, Maven-shared-utils: We solved N=3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20207styleName=TextprojectId=11761 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11761status=1component=15606 http://repository.apache.org/content/repositories/maven-1076/org/apache/maven/shared/maven-shared-utils/0.7/maven-shared-utils-0.7-source-release.zip Source checksum: 8b2a6f31505a158d295d5b06c800d61f821a15c2 (sha1) Staging site: http://maven.apache.org/shared-archives/maven-shared-utils-LATEST/ Clean plugin: We solved 3 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20685styleName=HtmlprojectId=11128 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MCLEAN%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1076/ http://repository.apache.org/content/repositories/maven-1076/org/apache/maven/plugins/maven-clean-plugin/2.6.1/maven-clean-plugin-2.6.1-source-release.zip Source release checksum(s): maven-clean-plugin-2.6.1-source-release.zip sha1: 9570fcfab513e98138680c44432e16c1d31bf639 Staging site: http://maven.apache.org/plugins-archives/maven-clean-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1626943 - in /maven/plugins/trunk: maven-acr-plugin/ maven-assembly-plugin/ maven-dependency-plugin/ maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/ maven-
wow, including tar from common-compress?? -D On Mon, Sep 22, 2014 at 11:52 PM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Not any more :) https://jira.codehaus.org/browse/PLXCOMP/fixforversion/20630 2.5 has full commons-compress support, java 7 file attribute support. Kristian 2014-09-23 8:42 GMT+02:00 Karl Heinz Marbaise khmarba...@gmx.de: Hi Kristian, I have short question You seemed to have released a new version of plexus-archiver 2.5 but in JIRA there is one issue related with plexus-archiver 2.5 not solved ? Kind regards Karl-Heinz Marbaise On 9/23/14 7:18 AM, krosenv...@apache.org wrote: Author: krosenvold Date: Tue Sep 23 05:18:12 2014 New Revision: 1626943 URL: http://svn.apache.org/r1626943 Log: plexus-archiver 2.5 Modified: maven/plugins/trunk/maven-acr-plugin/pom.xml maven/plugins/trunk/maven-assembly-plugin/pom.xml maven/plugins/trunk/maven-dependency-plugin/pom.xml maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/pom.xml maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/plugin/pom.xml maven/plugins/trunk/maven-ear-plugin/pom.xml maven/plugins/trunk/maven-eclipse-plugin/pom.xml maven/plugins/trunk/maven-ejb-plugin/pom.xml maven/plugins/trunk/maven-jar-plugin/pom.xml maven/plugins/trunk/maven-javadoc-plugin/pom.xml maven/plugins/trunk/maven-repository-plugin/pom.xml maven/plugins/trunk/maven-site-plugin/pom.xml maven/plugins/trunk/maven-source-plugin/pom.xml maven/plugins/trunk/maven-war-plugin/pom.xml Modified: maven/plugins/trunk/maven-acr-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-acr-plugin/pom.xml?rev=1626943r1=1626942r2=1626943view=diff == --- maven/plugins/trunk/maven-acr-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-acr-plugin/pom.xml Tue Sep 23 05:18:12 2014 @@ -110,7 +110,7 @@ under the License. dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-archiver/artifactId - version2.4.4/version + version2.5/version exclusions exclusion groupIdorg.codehaus.plexus/groupId Modified: maven/plugins/trunk/maven-assembly-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-assembly-plugin/pom.xml?rev=1626943r1=1626942r2=1626943view=diff == --- maven/plugins/trunk/maven-assembly-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-assembly-plugin/pom.xml Tue Sep 23 05:18:12 2014 @@ -125,7 +125,7 @@ under the License. dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-archiver/artifactId - version2.4.4/version + version2.5/version exclusions exclusion groupIdorg.codehaus.plexus/groupId Modified: maven/plugins/trunk/maven-dependency-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/pom.xml?rev=1626943r1=1626942r2=1626943view=diff == --- maven/plugins/trunk/maven-dependency-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-dependency-plugin/pom.xml Tue Sep 23 05:18:12 2014 @@ -155,7 +155,7 @@ under the License. dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-archiver/artifactId - version2.4.4/version + version2.5/version /dependency dependency groupIdorg.codehaus.plexus/groupId Modified: maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/pom.xml?rev=1626943r1=1626942r2=1626943view=diff == --- maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/pom.xml (original) +++ maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/pom.xml Tue Sep 23 05:18:12 2014 @@ -33,7 +33,7 @@ under the License. dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-archiver/artifactId - version2.2/version + version2.5/version /dependency /dependencies Modified: maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/plugin/pom.xml URL:
Re: svn commit: r1626943 - in /maven/plugins/trunk: maven-acr-plugin/ maven-assembly-plugin/ maven-dependency-plugin/ maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/ maven-
And soft link preserved after unpack?? Thanks On Tuesday, September 23, 2014, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Yup. Everything. I even just created https://jira.codehaus.org/browse/PLXCOMP-240 to document it :) It even seems like the compression is quite a lot better with cc. Kristian 2014-09-23 8:54 GMT+02:00 Dan Tran dant...@gmail.com javascript:;: wow, including tar from common-compress?? -D On Mon, Sep 22, 2014 at 11:52 PM, Kristian Rosenvold kristian.rosenv...@gmail.com javascript:; wrote: Not any more :) https://jira.codehaus.org/browse/PLXCOMP/fixforversion/20630 2.5 has full commons-compress support, java 7 file attribute support. Kristian 2014-09-23 8:42 GMT+02:00 Karl Heinz Marbaise khmarba...@gmx.de javascript:;: Hi Kristian, I have short question You seemed to have released a new version of plexus-archiver 2.5 but in JIRA there is one issue related with plexus-archiver 2.5 not solved ? Kind regards Karl-Heinz Marbaise On 9/23/14 7:18 AM, krosenv...@apache.org javascript:; wrote: Author: krosenvold Date: Tue Sep 23 05:18:12 2014 New Revision: 1626943 URL: http://svn.apache.org/r1626943 Log: plexus-archiver 2.5 Modified: maven/plugins/trunk/maven-acr-plugin/pom.xml maven/plugins/trunk/maven-assembly-plugin/pom.xml maven/plugins/trunk/maven-dependency-plugin/pom.xml maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/pom.xml maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/plugin/pom.xml maven/plugins/trunk/maven-ear-plugin/pom.xml maven/plugins/trunk/maven-eclipse-plugin/pom.xml maven/plugins/trunk/maven-ejb-plugin/pom.xml maven/plugins/trunk/maven-jar-plugin/pom.xml maven/plugins/trunk/maven-javadoc-plugin/pom.xml maven/plugins/trunk/maven-repository-plugin/pom.xml maven/plugins/trunk/maven-site-plugin/pom.xml maven/plugins/trunk/maven-source-plugin/pom.xml maven/plugins/trunk/maven-war-plugin/pom.xml Modified: maven/plugins/trunk/maven-acr-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-acr-plugin/pom.xml?rev=1626943r1=1626942r2=1626943view=diff == --- maven/plugins/trunk/maven-acr-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-acr-plugin/pom.xml Tue Sep 23 05:18:12 2014 @@ -110,7 +110,7 @@ under the License. dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-archiver/artifactId - version2.4.4/version + version2.5/version exclusions exclusion groupIdorg.codehaus.plexus/groupId Modified: maven/plugins/trunk/maven-assembly-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-assembly-plugin/pom.xml?rev=1626943r1=1626942r2=1626943view=diff == --- maven/plugins/trunk/maven-assembly-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-assembly-plugin/pom.xml Tue Sep 23 05:18:12 2014 @@ -125,7 +125,7 @@ under the License. dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-archiver/artifactId - version2.4.4/version + version2.5/version exclusions exclusion groupIdorg.codehaus.plexus/groupId Modified: maven/plugins/trunk/maven-dependency-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/pom.xml?rev=1626943r1=1626942r2=1626943view=diff == --- maven/plugins/trunk/maven-dependency-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-dependency-plugin/pom.xml Tue Sep 23 05:18:12 2014 @@ -155,7 +155,7 @@ under the License. dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-archiver/artifactId - version2.4.4/version + version2.5/version /dependency dependency groupIdorg.codehaus.plexus/groupId Modified: maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/pom.xml?rev=1626943r1=1626942r2=1626943view=diff == --- maven/plugins/trunk/maven-dependency-plugin/src/it/projects/setup-custom-ear-lifecycle/manager/pom.xml (original) +++ maven/plugins/trunk/maven
Re: [VOTE] Release Apache Maven Release Plugin version 2.5.1
)...? On 9/18/14 10:18 PM, Dan Tran wrote: Strange M2_HOME implicitly set at mvn.bat/mvn startup scripts. -D On Thu, Sep 18, 2014 at 1:14 PM, Benson Margulies bimargul...@gmail.com wrote: You need to set M2 HOME. I have no longer underscore on my phone. On Sep 18, 2014 3:48 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi Benson, Checksum Ok. Site looks ok. Just a question: Do i need a special setup to run tests etc. of the package cause i got the following: tried via mvn -Prun-its clean verify Environment: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: /usr/share/maven Java version: 1.7.0_21, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_ 21.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: mac os x, version: 10.8.5, arch: x86_64, family: mac Results : Tests in error: InvokerMavenExecutorTest.testEncryptSettings:132 » IllegalState Maven applicat... Tests run: 592, Failures: 0, Errors: 1, Skipped: 1 ? Kind regards Karl-Heinz Marbaise On 9/17/14 7:37 PM, Benson Margulies wrote: Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=11144version=20578 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=11144version=20578 Staging repo: https://repository.apache.org/content/repositories/maven-1062 http://repository.apache.org/content/repositories/maven- 1062/org/apache/maven/release/maven-release/2.5.1/maven- release-2.5.1-source-release.zip Source release checksum(s): maven-release-2.5.1-source-release.zip sha1: 894c26647abe1a0fef9929c2f7bfd662f2f240b9 Staging site: maven-release-archives/maven-release-LATEST Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Mit freundlichem Gruß Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - 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 Release Plugin version 2.5.1
Strange M2_HOME implicitly set at mvn.bat/mvn startup scripts. -D On Thu, Sep 18, 2014 at 1:14 PM, Benson Margulies bimargul...@gmail.com wrote: You need to set M2 HOME. I have no longer underscore on my phone. On Sep 18, 2014 3:48 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi Benson, Checksum Ok. Site looks ok. Just a question: Do i need a special setup to run tests etc. of the package cause i got the following: tried via mvn -Prun-its clean verify Environment: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: /usr/share/maven Java version: 1.7.0_21, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_ 21.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: mac os x, version: 10.8.5, arch: x86_64, family: mac Results : Tests in error: InvokerMavenExecutorTest.testEncryptSettings:132 » IllegalState Maven applicat... Tests run: 592, Failures: 0, Errors: 1, Skipped: 1 ? Kind regards Karl-Heinz Marbaise On 9/17/14 7:37 PM, Benson Margulies wrote: Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=11144version=20578 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=11144version=20578 Staging repo: https://repository.apache.org/content/repositories/maven-1062 http://repository.apache.org/content/repositories/maven- 1062/org/apache/maven/release/maven-release/2.5.1/maven- release-2.5.1-source-release.zip Source release checksum(s): maven-release-2.5.1-source-release.zip sha1: 894c26647abe1a0fef9929c2f7bfd662f2f240b9 Staging site: maven-release-archives/maven-release-LATEST Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Wagon 2.7 (take 2)
+1 tested http://jira.codehaus.org/browse/WAGON-407 using maven-3.1.x and maven-3.2.x Thank you for looking harder into the shading issue fix. -D On Sun, Sep 14, 2014 at 6:56 PM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Wagon 2.7 We fixed 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20560styleName=TextprojectId=10335Create=Create Since last vote, the shading has been fixed for Dan issue. Staging repository: https://repository.apache.org/content/repositories/maven-1060 Staging site: http://maven.apache.org/wagon-archives/wagon-LATEST/ Vote open for 72H [+1] [0] [-1] Cheers -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Wagon 2.7
tested by replace wagon*2.6 for wagon*2.6 under my maven-3.2.3/lib. It turns out maven 3.2.x now include jsoup, commons-io, and commons-lang under lib dir, so http://jira.codehaus.org/browse/WAGON-407 no longer needed unless maven dev remove thosed shaded file when ever wagon 2.7 got pushed into new maven release -Dan On Wed, Sep 10, 2014 at 10:29 PM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Wagon 2.7 We fixed 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20560styleName=TextprojectId=10335Create=Create Staging repository: https://repository.apache.org/content/repositories/maven-1054/ Staging site: http://maven.apache.org/wagon-archives/wagon-LATEST/ Vote open for 72H [+1] [0] [-1] Cheers -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Wagon 2.7
Further test shows that http://jira.codehaus.org/browse/WAGON-407 is NOT fixed so it is best to revert it, and mark as wont fix How it is tested under apache-maven-3.2.3/lib 1. Replace wagon*2.6* with wagon 2.7, I can use wagon-maven-plugin to download. This worls 2. Remove commons-io*.jar, the test fail, which means commons-io does not get pickup by wagon-http-2.7-shared.jar doen work ( even thou I do see commons-io got shaded) Thanks -D On Thu, Sep 11, 2014 at 1:42 PM, Dan Tran dant...@gmail.com wrote: tested by replace wagon*2.6 for wagon*2.6 under my maven-3.2.3/lib. It turns out maven 3.2.x now include jsoup, commons-io, and commons-lang under lib dir, so http://jira.codehaus.org/browse/WAGON-407 no longer needed unless maven dev remove thosed shaded file when ever wagon 2.7 got pushed into new maven release -Dan On Wed, Sep 10, 2014 at 10:29 PM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Wagon 2.7 We fixed 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20560styleName=TextprojectId=10335Create=Create Staging repository: https://repository.apache.org/content/repositories/maven-1054/ Staging site: http://maven.apache.org/wagon-archives/wagon-LATEST/ Vote open for 72H [+1] [0] [-1] Cheers -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Replacing plexus-archiver with commons-compress?
From today's maven hangout discussion Just want to let you know Kristian Rosenvold https://plus.google.com/u/0/112402174582006942652?prsrc=4 mentioned [1] he did some work on this area -D [1] http://maven.40175.n5.nabble.com/Use-native-tar-to-unpack-good-bad-idea-td5794712.html
Re: [VOTE] Apache Wagon 2.7
check out https://svn.codehaus.org/mojo/trunk/mojo/wagon-maven-plugin/src/it/http-download/ run mvn clean install -Dversion=1.0-beta-5 -D On Thu, Sep 11, 2014 at 2:24 PM, Olivier Lamy ol...@apache.org wrote: How did you test that? -- Olivier On Sep 12, 2014 7:13 AM, Dan Tran dant...@gmail.com wrote: Further test shows that http://jira.codehaus.org/browse/WAGON-407 is NOT fixed so it is best to revert it, and mark as wont fix How it is tested under apache-maven-3.2.3/lib 1. Replace wagon*2.6* with wagon 2.7, I can use wagon-maven-plugin to download. This worls 2. Remove commons-io*.jar, the test fail, which means commons-io does not get pickup by wagon-http-2.7-shared.jar doen work ( even thou I do see commons-io got shaded) Thanks -D On Thu, Sep 11, 2014 at 1:42 PM, Dan Tran dant...@gmail.com wrote: tested by replace wagon*2.6 for wagon*2.6 under my maven-3.2.3/lib. It turns out maven 3.2.x now include jsoup, commons-io, and commons-lang under lib dir, so http://jira.codehaus.org/browse/WAGON-407 no longer needed unless maven dev remove thosed shaded file when ever wagon 2.7 got pushed into new maven release -Dan On Wed, Sep 10, 2014 at 10:29 PM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Wagon 2.7 We fixed 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20560styleName=TextprojectId=10335Create=Create Staging repository: https://repository.apache.org/content/repositories/maven-1054/ Staging site: http://maven.apache.org/wagon-archives/wagon-LATEST/ Vote open for 72H [+1] [0] [-1] Cheers -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Wagon 2.7
that works because M2_HOME/lib has jsoup.jar, common-io.jar, commons-lang.jar ( those are NOT in 3.1.x) Try to remove commons-io.jar, it will fail since maven could not find a commons-io class. The question here why maven could not find the same class under wagon-http-2.7-shaded.jar -Dan On Thu, Sep 11, 2014 at 5:49 PM, Olivier Lamy ol...@apache.org wrote: So there is something here I don't understand or you have give me more details on how to test your problem. mb-olamy:http-download olamy$ mvn clean install -Dversion=1.0-beta-5 [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building wagon-maven-plugin testing [INFO] Downloading: https://archiva-repository.apache.org/archiva/repository/all-public/org/codehaus/mojo/wagon-maven-plugin/1.0-beta-5/wagon-maven-plugin-1.0-beta-5.pom Downloaded: https://archiva-repository.apache.org/archiva/repository/all-public/org/codehaus/mojo/wagon-maven-plugin/1.0-beta-5/wagon-maven-plugin-1.0-beta-5.pom (6 KB at 2.2 KB/sec) Downloading: https://archiva-repository.apache.org/archiva/repository/all-public/org/codehaus/mojo/wagon-maven-plugin/1.0-beta-5/wagon-maven-plugin-1.0-beta-5.jar Downloaded: https://archiva-repository.apache.org/archiva/repository/all-public/org/codehaus/mojo/wagon-maven-plugin/1.0-beta-5/wagon-maven-plugin-1.0-beta-5.jar (50 KB at 21.7 KB/sec) [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ wagon-maven-plugin --- [INFO] [INFO] --- wagon-maven-plugin:1.0-beta-5:list (http-list) @ wagon-maven-plugin --- [INFO] Scanning remote file system: http://repo1.maven.org/maven2/commons-dbutils/commons-dbutils ... [INFO] maven-metadata.xml [INFO] maven-metadata.xml.md5 [INFO] maven-metadata.xml.sha1 [INFO] [INFO] --- wagon-maven-plugin:1.0-beta-5:download-single (http-download-single) @ wagon-maven-plugin --- [INFO] Downloading: http://repo1.maven.org/maven2/commons-dbutils/commons-dbutils/1.1/commons-dbutils-1.1-sources.jar to /Users/olamy/dev/sources/open-sources/mojo/mojo-trunk/wagon-maven-plugin/src/it/http-download/target/it/http-download/commons-dbutils-1.1-sources.jar [INFO] AFICS no issue. Note: I build a core version with wagon 2.7 artifacts. So please explain how to reproduce your problem. On 12 September 2014 07:31, Dan Tran dant...@gmail.com wrote: check out https://svn.codehaus.org/mojo/trunk/mojo/wagon-maven-plugin/src/it/http-download/ run mvn clean install -Dversion=1.0-beta-5 -D On Thu, Sep 11, 2014 at 2:24 PM, Olivier Lamy ol...@apache.org wrote: How did you test that? -- Olivier On Sep 12, 2014 7:13 AM, Dan Tran dant...@gmail.com wrote: Further test shows that http://jira.codehaus.org/browse/WAGON-407 is NOT fixed so it is best to revert it, and mark as wont fix How it is tested under apache-maven-3.2.3/lib 1. Replace wagon*2.6* with wagon 2.7, I can use wagon-maven-plugin to download. This worls 2. Remove commons-io*.jar, the test fail, which means commons-io does not get pickup by wagon-http-2.7-shared.jar doen work ( even thou I do see commons-io got shaded) Thanks -D On Thu, Sep 11, 2014 at 1:42 PM, Dan Tran dant...@gmail.com wrote: tested by replace wagon*2.6 for wagon*2.6 under my maven-3.2.3/lib. It turns out maven 3.2.x now include jsoup, commons-io, and commons-lang under lib dir, so http://jira.codehaus.org/browse/WAGON-407 no longer needed unless maven dev remove thosed shaded file when ever wagon 2.7 got pushed into new maven release -Dan On Wed, Sep 10, 2014 at 10:29 PM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Wagon 2.7 We fixed 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20560styleName=TextprojectId=10335Create=Create Staging repository: https://repository.apache.org/content/repositories/maven-1054/ Staging site: http://maven.apache.org/wagon-archives/wagon-LATEST/ Vote open for 72H [+1] [0] [-1] Cheers -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Keeping Plexus component states persisted accross plugin executions
I am going back and forth on this topic and its reference, and still not able to get my singleton belonging to a jar to be shared across plugins. Dirk how are you doing at your side? Thanks -Dan On Fri, Aug 1, 2014 at 9:21 AM, Dan Tran dant...@gmail.com wrote: So far it looks to me it is as simple as setting extensionstrue/extensions to my project's build--plugins--plugin ( in this case maven-scm-plugin ). It not working. Perhaps I need to do some MANIFEST setup at my component? -D here the Herve' s response at mojo-dev you use either build/extensions/extension[1] or plugin/extensions[2] build/extensions is used in multiple mojo projects (just grep to find them) to add an extension to site plugin (which IMHO should not be done with such extension but just as m-site-p dependency) I couldn't find any exemple of plugin/extension, and the doc isn't clear. But since there is a Maven Core IT [3] for MNG-4381 [4] that explains exactly what you are trying to do (Test that extension plugins can contribute non- core components that can be accessed by other plugins in the same project and in projects with the same extension), this should contain a working example Regards, Hervé [1] http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_build [2] http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_plugin [3] http://jira.codehaus.org/browse/MNG-4381 [4] http://maven.apache.org/core-its/core-it-suite/xref-test/org/apache/maven/it/MavenITmng4381ExtensionSingletonComponentTest.html Le vendredi 1 août 2014 01:55:59 vous avez écrit : On Fri, Aug 1, 2014 at 2:24 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I replied on mojo (didn't see the cross-post) any help appreciated to improve the documentation :) Regards, Hervé Le vendredi 1 août 2014 11:05:43 dirk.mah...@buschmais.com a écrit : +1 from my side (see my questi. I tried using an extension for the question I asked some days ago ( http://mail-archives.apache.org/mod_mbox/maven-dev/201407.mbox/%3Ca2133e028 cf3c18c539eac4d6cf42ed9.squirrel%40webmail.buschmais.com%3E) but it seems not trivial - I ran into several classloading issues. Thus an example would be very helpful. Best regards and thanks in advance Dirk Ping On Thursday, July 31, 2014, Dan Tran dant...@gmail.com wrote: Hi my P4Maven - a Maven SCM providers - has plexus component singleton with states, and I would like to have the states to persist across multiple plugins executions ( maven-scm-plugin, maven-release-plugin, buildnumber-maven-plugin, etc) I think using maven extension is way to go, but not sure how to get this to work. Do you have a code sample somewhere? Huge thanks ahead -Dan - 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: Welcome Karl Heinz Marbaise to the Maven PMC
Congratulation Karl! you are my release guru :) -D On Tue, Aug 26, 2014 at 11:53 AM, Stephane Nicoll stephane.nic...@gmail.com wrote: Congrats Karl! On Tue, Aug 26, 2014 at 7:41 AM, Barrie Treloar baerr...@gmail.com wrote: I'm pleased to announce that the Maven PMC has voted to add Karl to the Maven PMC. Welcome, Karl.
Re: Q: plexus-container-default
any verdict on this? Thanks -D On Thu, Aug 14, 2014 at 10:58 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi Dan, I dont have an answer for this, but does it work without that artifact? I have tested with Maven 3.0.5...for example currently with Maven Shade Plugin... I have to check other plugins against Maven 2.2.1 ... I would get an answer just to be sure I would love to see that artifact disappear since it also pulls in junit at compile time Yes...;-(... Kind regards Karl-Heinz Marbaise
Re: Q: plexus-container-default
I dont have an answer for this, but does it work without that artifact? I would love to see that artifact disappear since it also pulls in junit at compile time Thanks -D On Thu, Aug 14, 2014 at 10:40 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi, i have a question concerning this kind of dependency for a plugin: dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-container-default/artifactId version1.0-alpha-9-stable-1/version /dependency As far as i understand this is a dependency of the plexus container which is used for Maven 2.0.X ? This means in my opinion that i can remove such a dependency from the plugins which should only be running with Maven 2.2.1 and Maven 3 Correct? Thanks in advance. 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: [VOTE] Maven 3.2.3 Release
+1 non binding. Tested with my Jenkins cluster with master on linux, slaves are on linux, solaris, and windows Thanks -D On Mon, Aug 11, 2014 at 5:09 PM, Mark Derricutt m...@talios.com wrote: +1 non binding - seems to work fine here on my various weird incarnations of clojure, scala, osgi. On 12 Aug 2014, at 11:53, Timothy Astle wrote: +1 (non-binding) Tested this in our environment where MNG-5663 was observed. This fixed the problem that I was seeing. Many thanks! Tim On 11/08/2014 6:19 PM, Jason van Zyl wrote: Hi, Time to release Maven 3.2.3! This release contains the important change of switching to HTTPS transport by default! Please test this release with your builds! Here is a link to Jira with 9 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500version=20443 Staging repo: https://repository.apache.org/content/repositories/maven-1046/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven- 1046/org/apache/maven/apache-maven/3.2.3/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven- 1046/org/apache/maven/apache-maven/3.2.3/apache-maven-3.2.3-bin.zip https://repository.apache.org/content/repositories/maven- 1046/org/apache/maven/apache-maven/3.2.3/apache-maven-3.2.3-bin.tar.gz https://repository.apache.org/content/repositories/maven- 1046/org/apache/maven/apache-maven/3.2.3/apache-maven-3.2.3-src.zip https://repository.apache.org/content/repositories/maven- 1046/org/apache/maven/apache-maven/3.2.3/apache-maven-3.2.3-src.tar.gz Source release checksum(s): apache-maven-3.2.3-src.zip sha1: 8607b9922d21078133f31ed8523eba e90a871d1f Staging site: http://people.apache.org/~jvanzyl/maven-3.2.3/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team -- Tim Astle Development Manager Web Technologies *CARIS* http://www.caris.com 115 Waggoners Lane Fredericton, New Brunswick CanadaE3B 2L4 Tel: +1.506.458.8533 Fax: +1.506.459.3849 www.caris.com http://www.caris.com *Connect with CARIS* Twitter http://www.twitter.com/CARIS_GIS | LinkedIn http://www.linkedin.com/groups?mostPopular=gid=3217878 | Facebook https://www.facebook.com/pages/CARIS-The-Marine-GIS- Experts/123907500987669?v=app_4949752878 | Google+ https://plus.google.com/b/114389770462919844434/ 114389770462919844434/posts | YouTube http://www.youtube.com/user/ CARISGIS Download your free copy of CARIS Easy View today! www.caris.com/easyview http://www.caris.com/easyview _ This email and any files transmitted with it are confidential and intended only for the addressee(s). If you are not the intended recipient(s) please notify us by email reply. You should not use, disclose, distribute or copy this communication if received in error. Any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of the company. No binding contract will result from this email until such time as a written document is signed on behalf of the company. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Changes of Maven Plugins to have 2.2.1 as minimum requirement
Hi I am seeing a number changes to core maven plugins to have Maven 2.2.1 as minimum requirement. Are we going to release them soon? Just curious Thank you for doing all that works -Dan
Re: Keeping Plexus component states persisted accross plugin executions
Ping On Thursday, July 31, 2014, Dan Tran dant...@gmail.com wrote: Hi my P4Maven - a Maven SCM providers - has plexus component singleton with states, and I would like to have the states to persist across multiple plugins executions ( maven-scm-plugin, maven-release-plugin, buildnumber-maven-plugin, etc) I think using maven extension is way to go, but not sure how to get this to work. Do you have a code sample somewhere? Huge thanks ahead -Dan
Re: Keeping Plexus component states persisted accross plugin executions
So far it looks to me it is as simple as setting extensionstrue/extensions to my project's build--plugins--plugin ( in this case maven-scm-plugin ). It not working. Perhaps I need to do some MANIFEST setup at my component? -D here the Herve' s response at mojo-dev you use either build/extensions/extension[1] or plugin/extensions[2] build/extensions is used in multiple mojo projects (just grep to find them) to add an extension to site plugin (which IMHO should not be done with such extension but just as m-site-p dependency) I couldn't find any exemple of plugin/extension, and the doc isn't clear. But since there is a Maven Core IT [3] for MNG-4381 [4] that explains exactly what you are trying to do (Test that extension plugins can contribute non- core components that can be accessed by other plugins in the same project and in projects with the same extension), this should contain a working example Regards, Hervé [1] http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_build [2] http://maven.apache.org/ref/3.2.2/maven-model/maven.html#class_plugin [3] http://jira.codehaus.org/browse/MNG-4381 [4] http://maven.apache.org/core-its/core-it-suite/xref-test/org/apache/maven/it/MavenITmng4381ExtensionSingletonComponentTest.html Le vendredi 1 août 2014 01:55:59 vous avez écrit : On Fri, Aug 1, 2014 at 2:24 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I replied on mojo (didn't see the cross-post) any help appreciated to improve the documentation :) Regards, Hervé Le vendredi 1 août 2014 11:05:43 dirk.mah...@buschmais.com a écrit : +1 from my side (see my questi. I tried using an extension for the question I asked some days ago ( http://mail-archives.apache.org/mod_mbox/maven-dev/201407.mbox/%3Ca2133e028 cf3c18c539eac4d6cf42ed9.squirrel%40webmail.buschmais.com%3E) but it seems not trivial - I ran into several classloading issues. Thus an example would be very helpful. Best regards and thanks in advance Dirk Ping On Thursday, July 31, 2014, Dan Tran dant...@gmail.com wrote: Hi my P4Maven - a Maven SCM providers - has plexus component singleton with states, and I would like to have the states to persist across multiple plugins executions ( maven-scm-plugin, maven-release-plugin, buildnumber-maven-plugin, etc) I think using maven extension is way to go, but not sure how to get this to work. Do you have a code sample somewhere? Huge thanks ahead -Dan - 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
Keeping Plexus component states persisted accross plugin executions
Hi my P4Maven - a Maven SCM providers - has plexus component singleton with states, and I would like to have the states to persist across multiple plugins executions ( maven-scm-plugin, maven-release-plugin, buildnumber-maven-plugin, etc) I think using maven extension is way to go, but not sure how to get this to work. Do you have a code sample somewhere? Huge thanks ahead -Dan
Re: Singleton component
http://maven.40175.n5.nabble.com/problem-Maven-creates-the-second-plugin-classloader-during-parallel-build-and-uses-two-classloader-hy-td5713793.html
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Class+Loading
May help
-d
On Tuesday, July 29, 2014, dirk.mah...@buschmais.com wrote:
Hi,
during the developing a Maven plugin (Maven project API version 3.0.5) for
the project jQAssistant (jqassistant.org) and I'm running into an issue
where I need some help:
The plugin mojo scans the artifacts generated by the build process
(classes, etc.) into an embedded instance of the graph database Neo4j to
provide the base for further analysis. As starting and shutting down the
database instance is quite expensive I would like to re-use a cached
instance for multi-module projects.
I'm trying to hold this instance in singleton class:
@org.codehaus.plexus.component.annotations.Component(role =
StoreProvider.class, instantiationStrategy = singleton)
public class StoreProvider implements Disposable {
...
}
and inject it into my Mojo using
@org.apache.maven.plugins.annotations.Component;
private StoreProvider storeProvider;
For several project structures I can see that multiple instances of the
singleton are created which breaks the contract I was hoping I could
establish (the database complains that there's already a running
instance).
It seems that this bevahior is related to the presence of some specific
plugins in the multi-module project to be scanned:
groupIdorg.codehaus.sonar/groupId
artifactIdsonar-packaging-maven-plugin/artifactId
version1.9/version
extensionstrue/extensions
How can I solve this problem?
Thanks in advance,
Dirk
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:;
For additional commands, e-mail: dev-h...@maven.apache.org javascript:;
Re: [VOTE] Apache Maven SCM Version 1.9.1
+1 - Tested with Perforce Maven SCM (P4Maven) provider at workshop.perforce.com - Built and run tck suits using the source tar ball on both windows and linux Thank for pushing this out. -Dan On Mon, Jul 21, 2014 at 2:51 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi, We solved 13 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10527version=19623 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D% 20SCM%20AND%20status%20%3D%20Open%20ORDER%20BY%20key% 20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1042 (As a representative): http://repository.apache.org/content/repositories/maven- 1042/org/apache/maven/plugins/maven-scm-plugin/1.9.1/maven- scm-plugin-1.9.1-sources.jar Source release checksum(s): maven-scm-plugin-1.9.1-sources.jar sha1: e35d9cedfa805ddc261199a8d17712 495171237a Staging site: http://maven.apache.org/scm-archives/scm-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 The Apache Maven Team Karl-Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Releasing maven-scm 1.10??
Need some help to release this component so that I can release Perforce provider using p4java at workshop.perforce.com. Very much appreciated. -D
Re: Releasing maven-scm 1.10??
Hi Karl, Yes it is http://maven.apache.org/scm Will you be able to cut it? Thanks -Dan On Wed, Jul 16, 2014 at 11:01 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi Dan, Need some help to release this component so that I can release Perforce provider using p4java at workshop.perforce.com. Very much appreciated. What in detail do you need? Are we talking about: http://maven.apache.org/scm/ http://jira.codehaus.org/browse/SCM 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: Releasing maven-scm 1.10??
I was hoping someone with much more experience releasing apache maven components to release it. Otherwise, I guest I have to roll my sleeves and go thru it ( it is my first time thou) Thanks -Dan On Wed, Jul 16, 2014 at 12:06 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi Dan, Hi Karl, Yes it is http://maven.apache.org/scm Will you be able to cut it? Are you not able to do so? 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: what is org.apache.maven:standalone-pom:pom:1,standalone-pom?
Thanks Stuart -D On Mon, Jul 14, 2014 at 7:55 AM, Stuart McCulloch mccu...@gmail.com wrote: It’s a stub pom.xml that’s used whenever a MavenExecutionRequest has no associated pom.xml file: https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/DefaultMaven.java#L644 https://github.com/apache/maven/blob/master/maven-core/src/main/resources/org/apache/maven/project/standalone.xml On 14 Jul 2014, at 06:39, Dan Tran dant...@gmail.com wrote: Hi I am playing with DependencyGraphBuilder and seeing the following artifact sneak into my list org.apache.maven:standalone-pom:pom:1,standalone-pom Any idea what it is? I am also seeing of of this from the build log, mine and from internet, but so far no-one seems to care Thanks -D
what is org.apache.maven:standalone-pom:pom:1,standalone-pom?
Hi I am playing with DependencyGraphBuilder and seeing the following artifact sneak into my list org.apache.maven:standalone-pom:pom:1,standalone-pom Any idea what it is? I am also seeing of of this from the build log, mine and from internet, but so far no-one seems to care Thanks -D
Re: Maven Developer Hangout
Removing Settings' mirror? we use it exclusively at work where we maintain a customize maven distribution with maven's conf/settings.xml has the mirror pointing to internal repository. I would be very much appreciated with Maven team can point me to a reference of this discussion that make Mirror as a bad practice? which hangout video was this mentioned? Thanks -D On Fri, Jul 4, 2014 at 10:08 AM, Jason van Zyl ja...@takari.io wrote: If you consider the identity of the artifact to be its SHA1, theoretically it doesn't matter where it comes from. This is not to say that's optimal to go looking everywhere for an artifact. How this is constrained in Nexus is through routing rules where Nexus knows only to look for given groupIds in a particular repository and this great optimizes lookup times. One might argue this type of logic can be moved back into Maven itself. As we discussed in the hangout, and I agree with Igor, that mirrors were an error and likely something we should eliminate in Maven 4.0.0 and work on a repository manager protocol like we discussed. On Jul 4, 2014, at 12:56 PM, Robert Scholte rfscho...@apache.org wrote: In addition to our hangout session: isn't it weird that for a dependency Maven can go over all the repositories, even though when an extra repository is added to the pom.xml, the developer knows exactly which dependencies should make use of that repository. To me it would make sense if you could add a reference to the repository per dependency, like dependency groupIdcom.acme/groupId artifactIdspecialtool/artifactId version1.0-alpha-1/version repositoryIdacme-store/repositoryId !-- only look in this repo, I know it's not in Central -- /dependency Robert Op Thu, 03 Jul 2014 00:37:17 +0200 schreef Mark Derricutt m...@talios.com: On 3 Jul 2014, at 6:25, Robert Scholte wrote: This is probably more than enough for tomorrow. A discussion on a merits and flaws of repositories (when combined with mirrors) is also warranted after some previous discussion on the list. Mark - 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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition
Need a new JIRA component for MAVEN SCM - TCK
Hi I have been enhancing maven-scm-test to my perforce provider using p4java work Could we a new component call 'TCK'?? I am currently using 'api', but it can be very confusion, since i am not changing the api Thanks -D
Re: Need a new JIRA component for MAVEN SCM - TCK
Thanks I will update the JIRAs -D On Wed, Jun 25, 2014 at 5:19 PM, Olivier Lamy ol...@apache.org wrote: done. maven-scm-tck On 26 June 2014 03:19, Dan Tran dant...@gmail.com wrote: Hi I have been enhancing maven-scm-test to my perforce provider using p4java work Could we a new component call 'TCK'?? I am currently using 'api', but it can be very confusion, since i am not changing the api Thanks -D -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-scm-provider-gitexe test failures
In another words, are you able to get maven-scm-provider-gitexe built and test passed? Thanks -D On Mon, Jun 23, 2014 at 5:57 PM, Dan Tran dant...@gmail.com wrote: Hi I am running into test failures Linux: ( git version 1.7.9.5) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:75-ScmTestCase.assertResult GitCheckInCommandTest.testCheckinAfterRename:113-ScmTestCase.assertResultIsSu windows ( cygwin gitt version 1.7.9) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:64-checkoutRepo:93-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. GitCheckInCommandTest.testCheckinAfterRename:123-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. GitExeCheckOutCommandNoBranchTest.testCheckoutNoBranch:65-checkoutRepo:89-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. GitExeCheckOutCommandNoBranchTest.testDoubleCheckoutNoBranch:77-checkoutRepo:89-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. Do I have the right setup? Thanks -D
Re: maven-scm-provider-gitexe test failures
Looks like the test fails on my change, but it not the same failures. I will looking into it, will need to upgrade my git -D On Tue, Jun 24, 2014 at 11:21 AM, Robert Scholte rfscho...@apache.org wrote: According to https://builds.apache.org/view/M-R/view/Maven/job/maven- scm/changes and #847 being stable they should succeed. IIRC you should at least use version 1.8, although I'm not sure. Robert Op Tue, 24 Jun 2014 10:20:31 +0200 schreef Dan Tran dant...@gmail.com: In another words, are you able to get maven-scm-provider-gitexe built and test passed? Thanks -D On Mon, Jun 23, 2014 at 5:57 PM, Dan Tran dant...@gmail.com wrote: Hi I am running into test failures Linux: ( git version 1.7.9.5) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:75- ScmTestCase.assertResult GitCheckInCommandTest.testCheckinAfterRename:113- ScmTestCase.assertResultIsSu windows ( cygwin gitt version 1.7.9) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:64- checkoutRepo:93-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. GitCheckInCommandTest.testCheckinAfterRename:123-ScmTestCase. assertResultIsSuccess:208 The check out result success flag was false. GitExeCheckOutCommandNoBranchTest.testCheckoutNoBranch:65- checkoutRepo:89-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. GitExeCheckOutCommandNoBranchTest.testDoubleCheckoutNoBranch:77- checkoutRepo:89-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. Do I have the right setup? Thanks -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-scm-provider-gitexe test failures
Hi Hervé *Thanks for the response, does your gitexe pass TCK test?* *-D* On Tue, Jun 24, 2014 at 1:46 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: no problem on my machine: Linux, git 1.9.1 Regards, Hervé Le mardi 24 juin 2014 01:20:31 Dan Tran a écrit : In another words, are you able to get maven-scm-provider-gitexe built and test passed? Thanks -D On Mon, Jun 23, 2014 at 5:57 PM, Dan Tran dant...@gmail.com wrote: Hi I am running into test failures Linux: ( git version 1.7.9.5) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:75-ScmTestCase.assertRe sult GitCheckInCommandTest.testCheckinAfterRename:113-ScmTestCase.assertResult IsSu windows ( cygwin gitt version 1.7.9) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:64-checkoutRepo:93-Scm TestCase.assertResultIsSuccess:208 The check out result success flag was false. GitCheckInCommandTest.testCheckinAfterRename:123-ScmTestCase.assertResult IsSuccess:208 The check out result success flag was false. GitExeCheckOutCommandNoBranchTest.testCheckoutNoBranch:65-checkoutRepo:89 -ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. GitExeCheckOutCommandNoBranchTest.testDoubleCheckoutNoBranch:77-checkoutR epo:89-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. Do I have the right setup? Thanks -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-scm-provider-gitexe test failures
Upgrade my git to 1.8.x fixes. TCK test failure probably to my change at maven-scm-test's StatusCommandTckTest. This only happen for gitexe, but not jgit looking... -D On Tue, Jun 24, 2014 at 1:54 PM, Dan Tran dant...@gmail.com wrote: Hi Hervé *Thanks for the response, does your gitexe pass TCK test?* *-D* On Tue, Jun 24, 2014 at 1:46 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: no problem on my machine: Linux, git 1.9.1 Regards, Hervé Le mardi 24 juin 2014 01:20:31 Dan Tran a écrit : In another words, are you able to get maven-scm-provider-gitexe built and test passed? Thanks -D On Mon, Jun 23, 2014 at 5:57 PM, Dan Tran dant...@gmail.com wrote: Hi I am running into test failures Linux: ( git version 1.7.9.5) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:75-ScmTestCase.assertRe sult GitCheckInCommandTest.testCheckinAfterRename:113-ScmTestCase.assertResult IsSu windows ( cygwin gitt version 1.7.9) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:64-checkoutRepo:93-Scm TestCase.assertResultIsSuccess:208 The check out result success flag was false. GitCheckInCommandTest.testCheckinAfterRename:123-ScmTestCase.assertResult IsSuccess:208 The check out result success flag was false. GitExeCheckOutCommandNoBranchTest.testCheckoutNoBranch:65-checkoutRepo:89 -ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. GitExeCheckOutCommandNoBranchTest.testDoubleCheckoutNoBranch:77-checkoutR epo:89-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. Do I have the right setup? Thanks -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven-scm-provider-gitexe test failures
Hi I am running into test failures Linux: ( git version 1.7.9.5) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:75-ScmTestCase.assertResult GitCheckInCommandTest.testCheckinAfterRename:113-ScmTestCase.assertResultIsSu windows ( cygwin gitt version 1.7.9) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:64-checkoutRepo:93-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. GitCheckInCommandTest.testCheckinAfterRename:123-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. GitExeCheckOutCommandNoBranchTest.testCheckoutNoBranch:65-checkoutRepo:89-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. GitExeCheckOutCommandNoBranchTest.testDoubleCheckoutNoBranch:77-checkoutRepo:89-ScmTestCase.assertResultIsSuccess:208 The check out result success flag was false. Do I have the right setup? Thanks -D
Re: how maven build plugins plugin use latest version
Setup your pom to use a verion properties with a default value ( your.plugin.versionsomedefault/your.plugin.version then you can override externally using -Dyour.plugin.version= that my be close to what you looking for -D On Tue, May 13, 2014 at 12:31 AM, Karl Heinz Marbaise khmarba...@gmx.dewrote: Hi, hi, all, I have developed a maven build plugin and I will upgrade it frequently. How to use the latest release version, not modify plugin version in pom.xml frequently? One idea is no version setting, but it will generate too much warnings. Setting LATEST, it won't work. Is there any good solution? Glad to hear it. The short answer is: Not possible. Just use the version in the pom file makes your build reproducible etc. If you update your plugin to new version it's a good idea to update the version in the pom file as well if you need to. The warnings which are being generated are a hint about not reproducible builds. 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: [FYI] maven-scm-plugin IT is failing since Feb 25
Yes, it is a better approach since the build is currently falling at ubuntu build at builds.apache.org -D On Tue, May 6, 2014 at 3:14 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I think Roberts' idea about svu upgradeing is good just need to revert locally and test, or we'll get the same problem in some time, when svn 1.9 is out Regards, Hervé Le mardi 6 mai 2014 15:00:58 Dan Tran a écrit : Thanks Hervé, it works on my local windows build with svn client 1.8.5 -D On Tue, May 6, 2014 at 2:30 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I updated content to svn 1.8: not really a long term solution, but at least give us time to find a better solution Regards, Hervé Le lundi 5 mai 2014 23:43:45 Dan Tran a écrit : perhaps, we need to disable this specific test for now? -D On Mon, May 5, 2014 at 9:18 PM, Dan Tran dant...@gmail.com wrote: Looks like we stuck without a new snapshot until this is fixed!! -D On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY herve.bout...@free.frwrote: seems related to SCM-741: the IT added contains a copy of .svn content taken from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has a different one (format 31) don't know how wa can improve the IT to be more tolerant to svn version updates Regards, Hervé Le lundi 5 mai 2014 09:03:37 Dan Tran a écrit : change list https://builds.apache.org/job/maven-scm/changes -D On Mon, May 5, 2014 at 9:01 AM, Dan Tran dant...@gmail.com wrote: https://builds.apache.org/job/maven-scm/ Thanks -D - 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: [FYI] maven-scm-plugin IT is failing since Feb 25
This issue is very stubborn -) I saw Hervé make a few changes, but builds.apache.org also have not triggered a new build? what is the schedule for this job? -Dan On Thu, May 8, 2014 at 9:25 AM, Robert Scholte rfscho...@apache.org wrote: it's probably something like .execute( null, basedir ) to ensure the right working directory is used. Robert http://groovy.codehaus.org/groovy-jdk/java/lang/String. html#execute%28java.util.List,%20java.io.File%29 Op Wed, 07 May 2014 00:14:07 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: I think Roberts' idea about svu upgradeing is good just need to revert locally and test, or we'll get the same problem in some time, when svn 1.9 is out Regards, Hervé Le mardi 6 mai 2014 15:00:58 Dan Tran a écrit : Thanks Hervé, it works on my local windows build with svn client 1.8.5 -D On Tue, May 6, 2014 at 2:30 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I updated content to svn 1.8: not really a long term solution, but at least give us time to find a better solution Regards, Hervé Le lundi 5 mai 2014 23:43:45 Dan Tran a écrit : perhaps, we need to disable this specific test for now? -D On Mon, May 5, 2014 at 9:18 PM, Dan Tran dant...@gmail.com wrote: Looks like we stuck without a new snapshot until this is fixed!! -D On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY herve.bout...@free.frwrote: seems related to SCM-741: the IT added contains a copy of .svn content taken from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has a different one (format 31) don't know how wa can improve the IT to be more tolerant to svn version updates Regards, Hervé Le lundi 5 mai 2014 09:03:37 Dan Tran a écrit : change list https://builds.apache.org/job/maven-scm/changes -D On Mon, May 5, 2014 at 9:01 AM, Dan Tran dant...@gmail.com wrote: https://builds.apache.org/job/maven-scm/ Thanks -D - 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: [FYI] maven-scm-plugin IT is failing since Feb 25
perhaps, we need to disable this specific test for now? -D On Mon, May 5, 2014 at 9:18 PM, Dan Tran dant...@gmail.com wrote: Looks like we stuck without a new snapshot until this is fixed!! -D On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY herve.bout...@free.frwrote: seems related to SCM-741: the IT added contains a copy of .svn content taken from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has a different one (format 31) don't know how wa can improve the IT to be more tolerant to svn version updates Regards, Hervé Le lundi 5 mai 2014 09:03:37 Dan Tran a écrit : change list https://builds.apache.org/job/maven-scm/changes -D On Mon, May 5, 2014 at 9:01 AM, Dan Tran dant...@gmail.com wrote: https://builds.apache.org/job/maven-scm/ Thanks -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [FYI] maven-scm-plugin IT is failing since Feb 25
Just tried it and still failing ( but not known why yet)
[INFO] --- maven-invoker-plugin:1.8:run (integration-test) @
maven-scm-plugin ---
[INFO] Building: scm-741-validate-scm-url-matches-working-copy\pom.xml
[INFO] run script prepare.groovy
[INFO] ..FAILED (6.6 s)
[INFO] The build exited with code 0. See
C:\Users\trand8\dev\apache\maven\maven-scm\maven-scm-plugin\target\it\scm-741-validate-scm-url-matches-working-copy\build.log
for details.
[INFO] -
[INFO] Build Summary:
[INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
[INFO] -
[ERROR] The following builds failed:
[ERROR] * scm-741-validate-scm-url-matches-working-copy\pom.xml
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 21.802 s
[INFO] Finished at: 2014-05-06T14:51:27-08:00
[INFO] Final Memory: 43M/712M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
project maven-scm-plugin: 1 build failed. See console output above for
details. - [Help 1]
Still looking...
-D
On Tue, May 6, 2014 at 1:11 PM, Robert Scholte rfscho...@apache.org wrote:
Would it help if this was added to the prepare.groovy?
try
{
svn upgrade.execute()
}
catch( Exception e )
{
// noop, no need to upgrade
}
return true
I seem to have a matching client version, so the IT works on my system.
Could someone verify the code above?
thanks,
Robert
Op Tue, 06 May 2014 08:43:45 +0200 schreef Dan Tran dant...@gmail.com:
perhaps, we need to disable this specific test for now?
-D
On Mon, May 5, 2014 at 9:18 PM, Dan Tran dant...@gmail.com wrote:
Looks like we stuck without a new snapshot until this is fixed!!
-D
On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
seems related to SCM-741: the IT added contains a copy of .svn content
taken
from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has a
different one (format 31)
don't know how wa can improve the IT to be more tolerant to svn version
updates
Regards,
Hervé
Le lundi 5 mai 2014 09:03:37 Dan Tran a écrit :
change list https://builds.apache.org/job/maven-scm/changes
-D
On Mon, May 5, 2014 at 9:01 AM, Dan Tran dant...@gmail.com wrote:
https://builds.apache.org/job/maven-scm/
Thanks
-D
-
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: [FYI] maven-scm-plugin IT is failing since Feb 25
Thanks Hervé, it works on my local windows build with svn client 1.8.5 -D On Tue, May 6, 2014 at 2:30 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I updated content to svn 1.8: not really a long term solution, but at least give us time to find a better solution Regards, Hervé Le lundi 5 mai 2014 23:43:45 Dan Tran a écrit : perhaps, we need to disable this specific test for now? -D On Mon, May 5, 2014 at 9:18 PM, Dan Tran dant...@gmail.com wrote: Looks like we stuck without a new snapshot until this is fixed!! -D On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY herve.bout...@free.frwrote: seems related to SCM-741: the IT added contains a copy of .svn content taken from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has a different one (format 31) don't know how wa can improve the IT to be more tolerant to svn version updates Regards, Hervé Le lundi 5 mai 2014 09:03:37 Dan Tran a écrit : change list https://builds.apache.org/job/maven-scm/changes -D On Mon, May 5, 2014 at 9:01 AM, Dan Tran dant...@gmail.com wrote: https://builds.apache.org/job/maven-scm/ Thanks -D - 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
[FYI] maven-scm-plugin IT is failing since Feb 25
https://builds.apache.org/job/maven-scm/ Thanks -D
Re: [FYI] maven-scm-plugin IT is failing since Feb 25
change list https://builds.apache.org/job/maven-scm/changes -D On Mon, May 5, 2014 at 9:01 AM, Dan Tran dant...@gmail.com wrote: https://builds.apache.org/job/maven-scm/ Thanks -D
Re: [FYI] maven-scm-plugin IT is failing since Feb 25
Looks like we stuck without a new snapshot until this is fixed!! -D On Mon, May 5, 2014 at 6:49 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: seems related to SCM-741: the IT added contains a copy of .svn content taken from svn 1.7 (format 29), and I suppose Jenkins uses svn 1.8 which has a different one (format 31) don't know how wa can improve the IT to be more tolerant to svn version updates Regards, Hervé Le lundi 5 mai 2014 09:03:37 Dan Tran a écrit : change list https://builds.apache.org/job/maven-scm/changes -D On Mon, May 5, 2014 at 9:01 AM, Dan Tran dant...@gmail.com wrote: https://builds.apache.org/job/maven-scm/ Thanks -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-stage-plugin / maven-repository-plugin
I think both of your issues should be fixed at wagon itself. btw, what is wrong with https? as an input? certificate/connection related? -Dan On Fri, Feb 28, 2014 at 2:02 AM, Karl Heinz Marbaise khmarba...@gmx.dewrote: Hi Dan, wagon-maven-plugin and vfs-maven-plugin do this. vfs was introduce since wagon-m-p is heavily depends on maven runtime. ( wagon-maven-plugin currently not wokring with mvn 3.1 out of box due to missing jars at maven/lib directory) But the docs expresses that they do not support http(s) which is exatly what i'm searching for... Apart from that i don't want to manually change my Maven installation to get a working plugin in particular if i have a CI solution... Kind regards Karl Heinz Marbaise -D On Wed, Feb 26, 2014 at 12:51 PM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I worked on the maven-stage-plugin some while ago. My plan was to move it to codehaus, as there seemed no real interest in improving this. I forked it to github (https://github.com/mfriedenhagen/stage2-maven-plugin) as I may not live without an SCM :-). Back then I thought I could use this to implement a simple staging mechanism without buying Nexus professional. Being on my own I decided I did not have the time and energy to bring this to an end and introduced Artifactory Pro in our company, which was much cheaper and did allow staging/promotion in a way I liked better. Regards Mirko Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Feb 25, 2014 at 11:38 AM, Dominik Bartholdi d...@fortysix.ch wrote: There is also a clean-local-repository-plugin: https://github.com/Finaxys/clean-local-repository-maven-plugin The user once requested to host/integrate it into an existing official apache plugin, but I have no idea what happened to this idea… Domi On 24.02.2014, at 20:12, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi, i would like to know if there are any update/enhancement plans/ideas for those two plugins maven-stage-plugin: In JIRA for the maven-stage-plugin there are several issue open which sound very interesting and would help me as well Based on my testing it currently seemed to be working only with scp in target repository but not with http ? etc. (may be i made a mistake ...). maven-repository-plugin: I would expect a goal like purge-local-repository of the maven-dependency-plugin more in this plugin? What about a goal like remove-local-snapshots (which can be done by maven-dependency-plugin:purge-local-repository via parameter)... 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: [VOTE] Release Maven Release version 2.5
how are we with this vote? -D On Sun, Feb 23, 2014 at 12:37 PM, Mark Derricutt m...@talios.com wrote: On 24 Feb 2014, at 5:12, Benson Margulies wrote: Maven scm 1.9 does not necessarily correspond to git 1.9. You would need to look at those release notes. Git 1.8.x changed the output of the human readable 'git status', scm 1.9 ( and quite a few versions earlier ) switched to using the git porcelain output. I've been using 1.9 and done some releases with a manually configured scm 1.9 without issue. Tho I've not yet tested this staged release plugin.
Re: maven-stage-plugin / maven-repository-plugin
wagon-maven-plugin and vfs-maven-plugin do this. vfs was introduce since wagon-m-p is heavily depends on maven runtime. ( wagon-maven-plugin currently not wokring with mvn 3.1 out of box due to missing jars at maven/lib directory) -D On Wed, Feb 26, 2014 at 12:51 PM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I worked on the maven-stage-plugin some while ago. My plan was to move it to codehaus, as there seemed no real interest in improving this. I forked it to github (https://github.com/mfriedenhagen/stage2-maven-plugin) as I may not live without an SCM :-). Back then I thought I could use this to implement a simple staging mechanism without buying Nexus professional. Being on my own I decided I did not have the time and energy to bring this to an end and introduced Artifactory Pro in our company, which was much cheaper and did allow staging/promotion in a way I liked better. Regards Mirko Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Feb 25, 2014 at 11:38 AM, Dominik Bartholdi d...@fortysix.ch wrote: There is also a clean-local-repository-plugin: https://github.com/Finaxys/clean-local-repository-maven-plugin The user once requested to host/integrate it into an existing official apache plugin, but I have no idea what happened to this idea… Domi On 24.02.2014, at 20:12, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi, i would like to know if there are any update/enhancement plans/ideas for those two plugins maven-stage-plugin: In JIRA for the maven-stage-plugin there are several issue open which sound very interesting and would help me as well Based on my testing it currently seemed to be working only with scp in target repository but not with http ? etc. (may be i made a mistake ...). maven-repository-plugin: I would expect a goal like purge-local-repository of the maven-dependency-plugin more in this plugin? What about a goal like remove-local-snapshots (which can be done by maven-dependency-plugin:purge-local-repository via parameter)... Kind regards Karl-Heinz Marbaise - 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][CANCELLED] Release Maven 3.2.0
Thanks Stuart for this confirmation, I am seeing this exact issue happen on both 3.1.x and 3.2. My build uses truezip-maven-plugin [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 19.347s [INFO] Finished at: Tue Feb 11 15:24:26 PST 2014 [INFO] Final Memory: 33M/698M [INFO] java.lang.NoClassDefFoundError: de/schlichtherle/truezip/fs/FsSyncOptions at de.schlichtherle.truezip.fs.FsSyncShutdownHook$Hook.run(FsSyncShutdownHook.java:93) Caused by: java.lang.ClassNotFoundException: de.schlichtherle.truezip.fs.FsSyncOptions at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.ja va:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java: 259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) ... 1 more On Tue, Feb 11, 2014 at 3:20 PM, Stuart McCulloch mccu...@gmail.com wrote: On 11 February 2014 22:15, Olivier Lamy ol...@apache.org wrote: Noticed this non blocking issue when using activemq plugin to start an activemq instance: [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 17.840s [INFO] Finished at: Wed Feb 12 09:12:23 EST 2014 [INFO] Final Memory: 33M/733M [INFO] [INFO] Apache ActiveMQ 5.9.0 (localhost, ID:mb-olamy.local-49682-1392156741632-0:1) is shutting down [INFO] Connector tcp://localhost:49681 stopped Exception in thread ActiveMQ ShutdownHook java.lang.NoClassDefFoundError: org/apache/activemq/transport/vm/VMTransportFactory I suspect this is related to the change in Classworlds 2.4.1+ to use the new ClassLoader.close() method available in Java7 to forcibly close plugin ClassLoaders when the plugin/container realm is disposed. This happens after the Maven build is finished, but before JVM shutdown hooks run. Any plugin that registers a JVM shutdown hook which tries to load classes/resources from the original plugin realm will throw a NCDFE - you'll probably see similar issues if a plugin forks threads that are still running after the plugin/container realm has been disposed and subsequently try to load classes. ( note that the same error will likely occur with Maven 3.1.1 since it uses the same version of Classworlds ) at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:733) at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:2348) at org.apache.activemq.broker.BrokerService$6.run(BrokerService.java:2315) Caused by: java.lang.ClassNotFoundException: org.apache.activemq.transport.vm.VMTransportFactory at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) ... 3 more Not blocker as it work as expected but just a bit annoying On 12 February 2014 07:37, Jason van Zyl ja...@takari.io wrote: Couple issues cropped up so I'm canceling the vote. On Feb 10, 2014, at 9:18 PM, Jason van Zyl ja...@takari.io wrote: Hi, Time to release Maven 3.2.0! Here is a link to Jira with 33 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=15565 Staging repo: https://repository.apache.org/content/repositories/maven-1005/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-bin.tar.gz https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.zip https://repository.apache.org/content/repositories/maven-1005/org/apache/maven/apache-maven/3.2.0/apache-maven-3.2.0-src.tar.gz Source release checksum(s): apache-maven-3.2.0-src.zip sha1: 4bc1ad352c07eef6e6b92c4923d1578d813bc57b Staging site: http://people.apache.org/~jvanzyl/maven-3.2.0/
Re: [VOTE] formally end support for Maven 1
+1 (nb). Must say thank you to this Maven1, it is the start of my career. -D On Sat, Mar 2, 2013 at 1:50 PM, Baptiste MATHUS m...@batmat.net wrote: +1 (non binding) Le 2 mars 2013 20:47, Mirko Friedenhagen mfriedenha...@gmail.com a écrit : +1 non-binding Regards Mirko -- Sent from my mobile - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Logback in Maven Core
+1 on for logback. However, is it possible to switch to Log4j2 by manually repackage maven distribution? Thanks -D On Tue, Dec 11, 2012 at 10:57 AM, Anders Hammar and...@hammar.net wrote: I'm +1 for logback as the slf4j impl. /Anders On Tue, Dec 11, 2012 at 3:32 AM, Jason van Zyl ja...@tesla.io wrote: Hi, I looked around a bit more today and I don't think SLF4J Simple is viable long term, I don't want to patch it anymore as I would have to do a day's work to make changes that keep the performance levels up, get it reviewed and released, and I honestly don't think it's worth it anymore. I would rather spend my time building out the plugin test cases and help to finish the classloader blocking of SLF4J. I don't mind spending time getting it all working but I don't want to waste my time on an implementation we're going to toss. After a conversation with the PMC it will require a vote to accept Logback which is EPL but I wanted to ask committers and interested users about using Logback. I believe Logback is the best choice as it's the most mature and battle tested implementation because once it goes in it's likely not ever to come out. Many of us are users and have integration experience with Logback and it's what I use everyday for logging in all my other projects and I've been a happy user for years. I see Logback as best of breed and widely adopted including 8 projects at Apache. There's no point in asking the PMC to vote on the acceptance of Logback if it's not acceptable by the community. If there are interested users I would really like to hear what you think because you're the ones who will have to live with the choice that is made. Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
doxia-eclipse-ide build issue
It seems the build is not stuck waiting for a 'ubuntu' instance https://builds.apache.org/view/M-R/view/Maven/job/doxia-eclipse-editor/ Can someone help? Thanks -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: doxia-eclipse-ide build issue
Thanks -D On Sun, Nov 18, 2012 at 4:13 PM, Olivier Lamy ol...@apache.org wrote: fixed and build passed. 2012/11/18 Dan Tran dant...@gmail.com: It seems the build is not stuck waiting for a 'ubuntu' instance https://builds.apache.org/view/M-R/view/Maven/job/doxia-eclipse-editor/ Can someone help? Thanks -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - 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: Need a build for Eclipse Doxia Editor
ping The FML editor is great, but we need the update Thanks -D On Mon, Sep 3, 2012 at 2:40 PM, Dan Tran dant...@gmail.com wrote: Thanks, Looks like the update site did not get built, need some help doxia team https://builds.apache.org/view/M-R/view/Maven/job/doxia-eclipse-editor/ws/doxia-ide-eclipse/eclipse-plugins/features/org.apache.maven.doxia.ide.eclipse.feature/target/site still not available Thanks -D On Mon, Sep 3, 2012 at 2:33 PM, Olivier Lamy ol...@apache.org wrote: done 2012/9/3 Dan Tran dant...@gmail.com: Hi the current Eclipse Doxia Editor build's workspace is not available and there for its advertised update site https://builds.apache.org/view/M-R/view/Maven/job/doxia-eclipse-editor/ws/doxia-ide-eclipse/eclipse-plugins/features/org.apache.maven.doxia.ide.eclipse.feature/target/site become not found. Can someone trigger a build?? Very much appreciated -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - 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
How to get a plugin execution to download a maven artifact using a provided maven coordinate to an alternative maven local repo ( not under the default .m2/repository )
Hello all, this is related to http://jira.codehaus.org/browse/MDEP-313 where i can use mvn2 to download both release and snapshot. Staring with maven3 its stops working for SNAPSHOT since maven2, for some reason, cant translate SNAPSHOT into timestamp available at remote repo. I am guessing is due to new maven 3 artifact handling ( Aether ). Can someone point me a snippet for this fix? ( due to this issue, I have to use maven2, and not able to fully migrate to maven 3. This has become a real pain ) Big thanks a ahead for any suggestions -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: How to get a plugin execution to download a maven artifact using a provided maven coordinate to an alternative maven local repo ( not under the default .m2/repository )
sorry about the noise I found plenty of example from here https://docs.sonatype.org/display/AETHER/Home -D On Sat, Sep 22, 2012 at 11:37 AM, Dan Tran dant...@gmail.com wrote: Hello all, this is related to http://jira.codehaus.org/browse/MDEP-313 where i can use mvn2 to download both release and snapshot. Staring with maven3 its stops working for SNAPSHOT since maven2, for some reason, cant translate SNAPSHOT into timestamp available at remote repo. I am guessing is due to new maven 3 artifact handling ( Aether ). Can someone point me a snippet for this fix? ( due to this issue, I have to use maven2, and not able to fully migrate to maven 3. This has become a real pain ) Big thanks a ahead for any suggestions -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Need a build for Eclipse Doxia Editor
Hi the current Eclipse Doxia Editor build's workspace is not available and there for its advertised update site https://builds.apache.org/view/M-R/view/Maven/job/doxia-eclipse-editor/ws/doxia-ide-eclipse/eclipse-plugins/features/org.apache.maven.doxia.ide.eclipse.feature/target/site become not found. Can someone trigger a build?? Very much appreciated -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Need a build for Eclipse Doxia Editor
Thanks, Looks like the update site did not get built, need some help doxia team https://builds.apache.org/view/M-R/view/Maven/job/doxia-eclipse-editor/ws/doxia-ide-eclipse/eclipse-plugins/features/org.apache.maven.doxia.ide.eclipse.feature/target/site still not available Thanks -D On Mon, Sep 3, 2012 at 2:33 PM, Olivier Lamy ol...@apache.org wrote: done 2012/9/3 Dan Tran dant...@gmail.com: Hi the current Eclipse Doxia Editor build's workspace is not available and there for its advertised update site https://builds.apache.org/view/M-R/view/Maven/job/doxia-eclipse-editor/ws/doxia-ide-eclipse/eclipse-plugins/features/org.apache.maven.doxia.ide.eclipse.feature/target/site become not found. Can someone trigger a build?? Very much appreciated -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - 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
thought on truezip-maven-plugin no longer works with maven 2
Hello starting with truezip.m.p 1.1, I have enhanced the shared component to use slf4j and bridge it ( via jcabi-maven-slf4j ) to use maven logger at plugin time. This may result in ''org.codehaus.plexus.component.configurator.BasicComponentConfigurator cannot be cast to org.codehaus.plexus.component.configurator.ComponentConfigurator' when invoke the plugin with maven 2 Does any one know how i can fix this? or Would it possible to doc this as maven 3 only? ( since i really need to have slf4j functionality in the shared component ) Thanks -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CALL FOR TEST] Apache Maven 3.0.4-RC3 staged
Look good to me, the issue reported by me for RC2 is fixed -Dan On Mon, Dec 5, 2011 at 6:28 AM, Olivier Lamy ol...@apache.org wrote: Hello, Apache Maven 3.0.4-RC3 has been staged for testing purpose (this is a preview of the coming 3.0.4 official release) The repository is available here: https://repository.apache.org/content/repositories/maven-292 For convenience, binaries have been copied here: http://people.apache.org/~olamy/maven/3.0.4-RC3/ This test phase will be for one week (until http://s.apache.org/MVN-3.0.4-RC3 ) Changes are available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17215styleName=TextprojectId=10500Create=Create . Feel free to report any regressions in http://jira.codehaus.org/browse/MNG Have Fun, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - 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] Apache Maven 3.0.4 (take 2)
here is sample pom.xml to reproduce the issue. 3.0.3 generate the correct lib dir, and script, but not 3.0.4 project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdmy.groupId/groupId artifactIdmyArtifactId/artifactId version1-SNAPSHOT/version packagingjar/packaging dependencies dependency groupIdcommons-cli/groupId artifactIdcommons-cli/artifactId version1.3-SNAPSHOT/version /dependency /dependencies build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdappassembler-maven-plugin/artifactId version1.1.1/version executions execution idgenerate-setup-scripts/id phaseprepare-package/phase goals goalassemble/goal /goals configuration repositoryLayoutflat/repositoryLayout generateRepositorytrue/generateRepository repositoryNamelib/repositoryName programs program mainClassfake.Main/mainClass namesetup/name /program /programs platforms platformunix/platform /platforms /configuration /execution /executions /plugin /plugins /build /project On Sat, Dec 3, 2011 at 8:42 AM, Brian Fox bri...@infinity.nu wrote: The RCs were started for a very specific reason, to improve the quality of our releases. Just breezing through this thread, there are clearly issues with memory and some other stuff here that may be bigger than we understand in this small testing surface. An RC build will get more eyes and either confirm these aren't a big deal, or they are. Reminder of where we were with 2.0.7, 2.0.8 and why we do RCs: http://www.sonatype.com/people/2008/04/quality-is-not-accidental/ I'm -1 on a release without some RCs. On Thu, Dec 1, 2011 at 3:17 PM, John Casey jdca...@commonjava.org wrote: On 12/1/11 10:27 AM, Olivier Lamy wrote: 2011/12/1 Jörg Schaiblejoerg.schai...@scalaris.com: Benjamin Bentmann wrote: Olivier Lamy wrote: I'd like to release Apache Maven 3.0.4 (take 2). [...] Note the difference with first vote is an upgrade of aether to 1.13.1 What about the memory issue that Jörg brought up? Shouldn't we at least understand the cause and potential impact on other users before continuing the release? Continue, I'll report later, but it seems that there's no regression in 304 vs 303. Thanks! @Benjamin: I tend to say we must release it (maybe the famous early and often' :-) ). Early-and-often is great, but it's not an excuse to be lax on quality standards. Hudson had some famously horrible releases early on, and I suspect they had to do with sacrificing concerns about quality on the altar of early-and-often. An RC would take less than a week more if the code really is ready to go. If it's not, then we don't want to release it, do we? My goal is to provide a release point (stable tagged build) to get feedbacks. Trying to reach/wait the perfect release without those feedbacks is IMHO impossible. Actually it's not; the feedback comes by way of RCs. This is why it's so important to do RCs for Maven core. Maybe we can skip the RC process on plugins (I tend to think a single, quick RC is still a good idea there), but the core is far, far more complex. Even with a huge IT set we cannot hope to cover all use cases there, so it's simply not enough. If Jörg's issue doesn't pop up in this staged release, then I'd say let's just learn that lesson for next time. It takes a little longer using RCs, but it's the ONLY way we've been able to produce releases that weren't riddled with regressions in the past. Even with a strong IT suite, it's still good practice. As an aside, we might as well call this staging of 3.0.4 a RC and discuss it here as if it was. The main difference is procedural IMO, in that this is a [VOTE] thread, not a [DISCUSS] thread about whether the staged RC is ready to go. IMO that's an important distinction, since the 72h time limit is lurking nearby, but we'd still want to time-box the review of any RC The previous issue for ngnix users was blocker as some oss forge use it. So I cancel it and restart one (and thanks for the fast aether change). But for such memory issue at least users can change MAVEN_OPTS. My email [1] to Jörg describe various things to test on his private company build (I hope he will have time to provide such feedbacks with a stable maven build) Cheers, Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:
Re: [VOTE] Apache Maven 3.0.4 (take 2)
Thanks for looking into this issue. consider it is a blocking regression since there is no work around for me to use 3.0.4 \-D On Sat, Dec 3, 2011 at 1:47 PM, Olivier Lamy ol...@apache.org wrote: Thanks! It looks an erroneous file is picked when it has been download from a remote repo and when it's reinstall locally (use case of appassembler which reinstall file locally) investigating... 2011/12/3 Dan Tran dant...@gmail.com: here is sample pom.xml to reproduce the issue. 3.0.3 generate the correct lib dir, and script, but not 3.0.4 project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdmy.groupId/groupId artifactIdmyArtifactId/artifactId version1-SNAPSHOT/version packagingjar/packaging dependencies dependency groupIdcommons-cli/groupId artifactIdcommons-cli/artifactId version1.3-SNAPSHOT/version /dependency /dependencies build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdappassembler-maven-plugin/artifactId version1.1.1/version executions execution idgenerate-setup-scripts/id phaseprepare-package/phase goals goalassemble/goal /goals configuration repositoryLayoutflat/repositoryLayout generateRepositorytrue/generateRepository repositoryNamelib/repositoryName programs program mainClassfake.Main/mainClass namesetup/name /program /programs platforms platformunix/platform /platforms /configuration /execution /executions /plugin /plugins /build /project On Sat, Dec 3, 2011 at 8:42 AM, Brian Fox bri...@infinity.nu wrote: The RCs were started for a very specific reason, to improve the quality of our releases. Just breezing through this thread, there are clearly issues with memory and some other stuff here that may be bigger than we understand in this small testing surface. An RC build will get more eyes and either confirm these aren't a big deal, or they are. Reminder of where we were with 2.0.7, 2.0.8 and why we do RCs: http://www.sonatype.com/people/2008/04/quality-is-not-accidental/ I'm -1 on a release without some RCs. On Thu, Dec 1, 2011 at 3:17 PM, John Casey jdca...@commonjava.org wrote: On 12/1/11 10:27 AM, Olivier Lamy wrote: 2011/12/1 Jörg Schaiblejoerg.schai...@scalaris.com: Benjamin Bentmann wrote: Olivier Lamy wrote: I'd like to release Apache Maven 3.0.4 (take 2). [...] Note the difference with first vote is an upgrade of aether to 1.13.1 What about the memory issue that Jörg brought up? Shouldn't we at least understand the cause and potential impact on other users before continuing the release? Continue, I'll report later, but it seems that there's no regression in 304 vs 303. Thanks! @Benjamin: I tend to say we must release it (maybe the famous early and often' :-) ). Early-and-often is great, but it's not an excuse to be lax on quality standards. Hudson had some famously horrible releases early on, and I suspect they had to do with sacrificing concerns about quality on the altar of early-and-often. An RC would take less than a week more if the code really is ready to go. If it's not, then we don't want to release it, do we? My goal is to provide a release point (stable tagged build) to get feedbacks. Trying to reach/wait the perfect release without those feedbacks is IMHO impossible. Actually it's not; the feedback comes by way of RCs. This is why it's so important to do RCs for Maven core. Maybe we can skip the RC process on plugins (I tend to think a single, quick RC is still a good idea there), but the core is far, far more complex. Even with a huge IT set we cannot hope to cover all use cases there, so it's simply not enough. If Jörg's issue doesn't pop up in this staged release, then I'd say let's just learn that lesson for next time. It takes a little longer using RCs, but it's the ONLY way we've been able to produce releases that weren't riddled with regressions in the past. Even with a strong IT suite, it's still good practice. As an aside, we might as well call this staging of 3.0.4 a RC and discuss it here as if it was. The main difference is procedural IMO, in that this is a [VOTE] thread, not a [DISCUSS] thread about whether the staged RC is ready to go. IMO that's an important distinction, since the 72h time limit is lurking nearby, but we'd still want to time-box the review of any RC The previous issue for ngnix users was blocker as some oss forge use it. So I cancel it and restart
Re: [VOTE] Apache Maven 3.0.4 (take 2)
When using 3.0.4 with appassemble-maven-plugin to generate java wrapper scripts which use snapshot dependency. The plugin places the dependencies to its lib/repo directory using timestamp snapshots picked up from maven repo, but generated scripts using '-SNAPSHOT' for its classpath. this breaks my runtime. There is no issue with 3.0.3. Do others see the same issue? Thanks -D On Fri, Dec 2, 2011 at 12:39 PM, John Casey jdca...@commonjava.org wrote: I've done several medium sized builds and everything looks okay here. +1 On 12/1/11 4:20 AM, Olivier Lamy wrote: Hello, I'd like to release Apache Maven 3.0.4 (take 2). We fixed 31 issues. See release notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=17215 Note the difference with first vote is an upgrade of aether to 1.13.1 (to prevent chuncked transfer encoding when deploying md5/sha1 files http(s): mode which is not supported by ngnix). And ref site (http://maven.apache.org/ref/3.0.4/) which now use the new fluido skin (wait sync). The staged repo is available here: https://repository.apache.org/content/repositories/maven-283/ The staged distributions are available here: http://people.apache.org/builds/maven/3.0.4/ As we are near the week end, the vote will be a 5 days vote. [+1] [0] [-1] Here my +1 Thanks, -- John Casey Developer, PMC Chair - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - 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: Best Practices for Proxy and Mojos
you may want to look at this link as sample code on how to deal with proxy http://mojo.codehaus.org/wagon-maven-plugin/xref/org/codehaus/mojo/wagon/shared/WagonUtils.html I did not write that code thou -D On Fri, Sep 23, 2011 at 3:45 PM, Aldrin Leal ald...@leal.eng.br wrote: Folks, Just a question: How do you deal with HTTP Proxies into your mojos. Is there an standard or sample source to point me to? Thank you -- -- Aldrin Leal, ald...@leal.eng.br / http://meadiciona.com/aldrinleal - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Eclipse Doxia Editor to trunk
I installed the plugin via update site, loading fml file crashes. but let's start this discussion on another topic. -D On Tue, Sep 13, 2011 at 7:20 AM, Vincent Siveton vsive...@apache.org wrote: did you try open with from menu? Vincent 2011/9/11 Dan Tran dant...@gmail.com: Thank you for putting hard work on this feature. looking forward to be able to view .fml file inside eclipse ide. -D 2011/9/11 Arnaud Héritier aherit...@gmail.com: +1 Arnaud On Sun, Sep 11, 2011 at 6:09 PM, Olivier Lamy ol...@apache.org wrote: +1 -- Olivier Le 11 sept. 2011 15:18, Vincent Siveton vsive...@apache.org a écrit : Hi, I like to move the Eclipse Doxia Editor to the trunk ie http://svn.apache.org/repos/asf/maven/sandbox/trunk/doxia/doxia-ide/eclipse/ to http://svn.apache.org/repos/asf/maven/doxia/doxia-ide/eclipse/ Here is a preview of the documentation: http://people.apache.org/~vsiveton/apache-doxia-eclipse-plugin-1.0-SNAPSHOT/ Also, we need a specific JIRA tracker for this instead of http://jira.codehaus.org/browse/DOXIATOOLS/component/14861 Someone? Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Vincent - 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: [VOTE] Move Eclipse Doxia Editor to trunk
Thank you for putting hard work on this feature. looking forward to be able to view .fml file inside eclipse ide. -D 2011/9/11 Arnaud Héritier aherit...@gmail.com: +1 Arnaud On Sun, Sep 11, 2011 at 6:09 PM, Olivier Lamy ol...@apache.org wrote: +1 -- Olivier Le 11 sept. 2011 15:18, Vincent Siveton vsive...@apache.org a écrit : Hi, I like to move the Eclipse Doxia Editor to the trunk ie http://svn.apache.org/repos/asf/maven/sandbox/trunk/doxia/doxia-ide/eclipse/ to http://svn.apache.org/repos/asf/maven/doxia/doxia-ide/eclipse/ Here is a preview of the documentation: http://people.apache.org/~vsiveton/apache-doxia-eclipse-plugin-1.0-SNAPSHOT/ Also, we need a specific JIRA tracker for this instead of http://jira.codehaus.org/browse/DOXIATOOLS/component/14861 Someone? Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Vincent - 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
Request to release maven-release-plugin 2.2
Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Request to release maven-release-plugin 2.2
Why not just cut with what we currently have? :-) I will do my best to review -D On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: hervé has been making some tweak today (as have i) if nobody steps up, i should be able to kick off a release on Monday. won't have the bandwidth before then, and there are a couple of critical issues in jira... be good to do a bug scrub first. Dan, if you can review the open critical issues and feed back your feeling on which can be downgraded i'll drive the release. Deal? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 24 Jun 2011 16:42, Dan Tran dant...@gmail.com wrote: Hi Can we have a new release for this plugin? I am anxious to pick up http://jira.codehaus.org/browse/MRELEASE-648 -D - 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
Alternate Local repository during dependency:copy is not working for maven 3
Hello, maven dev, A while a go, I introduced alternate local repo at dependency:copy/unpack time. It is now not working for maven 3, any help/advice on how to fix this issue is greatly appreciated http://jira.codehaus.org/browse/MDEP-313 Thanks -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1125604 - /maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.java
good catch Anders, wonder what is the original intention of that code :-)
-Dan
On Sat, May 21, 2011 at 10:28 AM, Anders Hammar and...@hammar.net wrote:
But the groupId of Apache Maven plugins is org.apache.maven.plugins. The
code checks against org.apache.maven.plugin...
/Anders
On Sat, May 21, 2011 at 10:26, Dennis Lundberg denn...@apache.org wrote:
Excellent stuff Stephen, thanks.
We should try to get this into a release as soon as possible.
On 2011-05-21 02:21, steph...@apache.org wrote:
Author: stephenc
Date: Sat May 21 00:21:26 2011
New Revision: 1125604
URL: http://svn.apache.org/viewvc?rev=1125604view=rev
Log:
No point sitting on this change any longer.
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.java
Modified:
maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.java
URL:
http://svn.apache.org/viewvc/maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.java?rev=1125604r1=1125603r2=1125604view=diff
==
---
maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.java
(original)
+++
maven/plugin-tools/trunk/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.java
Sat May 21 00:21:26 2011
@@ -125,6 +125,16 @@ public abstract class AbstractGeneratorM
return;
}
+ if ( project.getArtifactId().toLowerCase().startsWith( maven-
)
+ project.getArtifactId().toLowerCase().endsWith( -plugin
)
+ !org.apache.maven.plugin.equals( project.getGroupId() )
)
+ {
+ getLog().error( \n\nArtifact Ids of the format
maven-___-plugin are reserved for \n
+ + plugins in the Group Id
org.apache.maven.plugins\n
+ + Please change your artifactId to the
format ___-maven-plugin\n
+ + In the future this error will break
the build.\n\n );
+ }
+
String defaultGoalPrefix =
PluginDescriptor.getGoalPrefixFromArtifactId( project.getArtifactId() );
if ( goalPrefix == null )
{
--
Dennis Lundberg
-
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 Maven SCM 1.5
The release notes on navigation is empty. Also I am interested on how to configure username/password in settings.xml, but not able to find instructions -Dan On Mon, Mar 28, 2011 at 3:30 PM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Maven SCM 1.5. We solved 32 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527version=16688 Staging repo: https://repository.apache.org/content/repositories/maven-051/ Staging sites : Scm : http://maven.apache.org/scm-1.5 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - 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 Maven SCM 1.5
never mind, I found suggestion at http://stackoverflow.com/questions/1255593/externalising-scm-credentials-with-maven I am sure we do doc it some where at maven scm site -D On Mon, Mar 28, 2011 at 7:49 PM, Dan Tran dant...@gmail.com wrote: The release notes on navigation is empty. Also I am interested on how to configure username/password in settings.xml, but not able to find instructions -Dan On Mon, Mar 28, 2011 at 3:30 PM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Maven SCM 1.5. We solved 32 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527version=16688 Staging repo: https://repository.apache.org/content/repositories/maven-051/ Staging sites : Scm : http://maven.apache.org/scm-1.5 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - 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: Julia Antonova/Tumlare is out of office.
I keep seeing 'Wiki updated.' . What is it about? -D On Tue, Feb 22, 2011 at 11:30 AM, Stephane Nicoll stephane.nic...@gmail.com wrote: ah ah :) 2011/2/22 Tamás Cservenák ta...@cservenak.net: Wiki updated. On Tue, Feb 22, 2011 at 8:07 PM, Julia Antonova juli...@tumlare.com wrote: I will be out of the office starting 22.02.2011 and will not return until 24.02.2011. I have no acces to my mailbox, I will reply to your message upon return. Thank you! - 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 maven dependency analyzer
+1 tested together with maven-dependency-plugin at another stage against my comp build. -Dan On Tue, Feb 15, 2011 at 3:13 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Brian Fox wrote: Staging repo: https://repository.apache.org/content/repositories/maven-055/ +1 Benjamin - 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] maven-dependency-plugin 2.2
+1 tested together with maven-dependency-analyzer at another stage against my comp build. -D On Tue, Feb 15, 2011 at 12:32 PM, Brian Fox bri...@infinity.nu wrote: Plugin is staged at: https://repository.apache.org/content/repositories/maven-009 This release is dependent upon the maven-dependency-analyzer vote and staged artifacts. We fixed a boat load of issues: Release Notes - Maven 2.x Dependency Plugin - Version 2.2 ** Bug * [MDEP-138] - unpack of tar files fail with ArchiverException: chmod exit code was: 1 * [MDEP-142] - Path with space makes the dependency:unpack goal fail * [MDEP-143] - incomplete literal/length tree when analyzing * [MDEP-149] - Field accesses and method invocations cause bogus dependencies * [MDEP-155] - writing classpath into a file doesn't work anymore * [MDEP-161] - dependy:resolve-plugins doesn't output to file when using outputFile parameter * [MDEP-164] - dependency:copy-dependencies does not honour 'copyPom' * [MDEP-165] - dependency:copy-dependencies does not copy sources, and downloads them every time * [MDEP-171] - link to Unpacking the Project Dependencies is broken - website * [MDEP-175] - includeArtifactIds should trim whitespace * [MDEP-192] - generated classpath should match what maven produces * [MDEP-193] - NullPointerException inside org.apache.maven.shared.artifact.filter.collection.AbstractArtifactFeatureFilter * [MDEP-203] - Severe Errors are only logged as debug * [MDEP-208] - finalName of artifacts not in the reactor is not taken into account. * [MDEP-219] - mvn dependency:analyze -DoutputXML=true does not include classifier in XML output * [MDEP-225] - Dependency plugin seems to unpack archive even, if it is already unpacked * [MDEP-235] - includeArtifactIds fails to handle internal spaces * [MDEP-238] - Wrong links on the web site * [MDEP-260] - fileSeparator\/fileSeparator causes an exception * [MDEP-263] - filtering by classifier don't work * [MDEP-264] - Dependency is copied from original source directory instead of .m2 using maven 3 ** Improvement * [MDEP-127] - Take advantage of PLXCOMP-76 * [MDEP-211] - Possibility to prepend groupId to dependencies * [MDEP-212] - copy goal example should use install phase instead of package phase * [MDEP-240] - ignoreNonCompile not available for analyze-report * [MDEP-248] - Add Swedish translation * [MDEP-250] - Add a skip paramater to dependency:unpack * [MDEP-262] - Add support for custom ProjectDependencyAnalyzer implementations * [MDEP-292] - When selecting groupId fuzziness, exclude all artifacts based on groupId. ** New Feature * [MDEP-179] - Ability to use an alternate repository at copy and unpack mojo's execution time * [MDEP-206] - Add new Mojo to find duplicate dependency declared * [MDEP-215] - copy-dependencies -- useSubDirectoryPerScope [patch] * [MDEP-296] - Goal to resolve dependencies and set properties for artifact paths ** Task * [MDEP-228] - Review the Doxia Sink calls ** Wish * [MDEP-226] - Improve documentation for dependency:copy artifactItem element * [MDEP-281] - An option to append outputs at the end of output file Vote is open for 72 hrs - 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 maven dependency analyzer
Brian, Do you still plan to publish the staging repo for maven-dependency-plugin? -Dan On Fri, Feb 11, 2011 at 2:41 PM, Lukas Theussl ltheu...@apache.org wrote: +1 -Lukas Brian Fox wrote: Staging repo: https://repository.apache.org/content/repositories/maven-055/ This release fixes MDEP-143, MDEP-149, MDEP-262 and is required by the Maven Dependency Plugin 2.2 Vote is open for 72 hours - 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 maven dependency analyzer
Perhaps, you can stage both of them together. It is easier to test that way. -Dan On Thu, Feb 10, 2011 at 5:08 PM, Brian Fox bri...@infinity.nu wrote: Staging repo: https://repository.apache.org/content/repositories/maven-055/ This release fixes MDEP-143, MDEP-149, MDEP-262 and is required by the Maven Dependency Plugin 2.2 Vote is open for 72 hours - 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 maven dependency analyzer
oops sorry, You already did that -Dan On Thu, Feb 10, 2011 at 5:57 PM, Dan Tran dant...@gmail.com wrote: Perhaps, you can stage both of them together. It is easier to test that way. -Dan On Thu, Feb 10, 2011 at 5:08 PM, Brian Fox bri...@infinity.nu wrote: Staging repo: https://repository.apache.org/content/repositories/maven-055/ This release fixes MDEP-143, MDEP-149, MDEP-262 and is required by the Maven Dependency Plugin 2.2 Vote is open for 72 hours - 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: Culling the maven-stage-plugin
On Mon, Nov 1, 2010 at 2:15 PM, Jason van Zyl ja...@maven.org wrote: On Nov 1, 2010, at 10:12 PM, Dennis Lundberg wrote: On 2010-11-01 18:54, Jason van Zyl wrote: Doesn't change the fact it's a hack, generally not useful and is generally not going to get used. It actually is being used. Dennis, are you committed to supporting it? My plan is to close as many issues as I can and release a 1.0, to get rid of one of the last beta-version-plugins :) After that I'm done with it. I do think that this is a useful plugin for those that do not, for whatever reason, have a repository manager, despite its warts. Perhaps a plugin that could move to the Mojo project? There is no need to move stage plugin to MOJO since wagon-maven-plugin covers that feature. That seems most sensible given the guy you applied the patch for could have done it himself at Mojo. If so, that's fine, but it's a dead end plugin as far as I'm concerned. Who's going to use it when all the repository managers have some form of staging? On Nov 1, 2010, at 6:47 PM, Brett Porter wrote: Dennis committed to it just yesterday, so I think calling it unsupported is premature. On 01/11/2010, at 8:39 AM, Jason van Zyl wrote: This was a hack, and has now been replaced with Nexus staging here at Apache (and most other forges). I believe this plugin can be archived now. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - We all have problems. How we deal with them is a measure of our worth. -- Unknown -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Culling the maven-stage-plugin
On Mon, Nov 1, 2010 at 3:46 PM, Jason van Zyl ja...@maven.org wrote: On Nov 1, 2010, at 11:24 PM, Dan Tran wrote: On Mon, Nov 1, 2010 at 2:15 PM, Jason van Zyl ja...@maven.org wrote: On Nov 1, 2010, at 10:12 PM, Dennis Lundberg wrote: On 2010-11-01 18:54, Jason van Zyl wrote: Doesn't change the fact it's a hack, generally not useful and is generally not going to get used. It actually is being used. Dennis, are you committed to supporting it? My plan is to close as many issues as I can and release a 1.0, to get rid of one of the last beta-version-plugins :) After that I'm done with it. I do think that this is a useful plugin for those that do not, for whatever reason, have a repository manager, despite its warts. Perhaps a plugin that could move to the Mojo project? There is no need to move stage plugin to MOJO since wagon-maven-plugin covers that feature. So you're saying Dennis applied your patch and you're using the wagon-maven-plugin? My apology, should had withdrawn the request for this fix a long time ago. That seems most sensible given the guy you applied the patch for could have done it himself at Mojo. If so, that's fine, but it's a dead end plugin as far as I'm concerned. Who's going to use it when all the repository managers have some form of staging? On Nov 1, 2010, at 6:47 PM, Brett Porter wrote: Dennis committed to it just yesterday, so I think calling it unsupported is premature. On 01/11/2010, at 8:39 AM, Jason van Zyl wrote: This was a hack, and has now been replaced with Nexus staging here at Apache (and most other forges). I believe this plugin can be archived now. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - We all have problems. How we deal with them is a measure of our worth. -- Unknown -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Culling the maven-stage-plugin
On Mon, Nov 1, 2010 at 5:59 PM, Jason van Zyl ja...@maven.org wrote: On Nov 2, 2010, at 1:40 AM, Dan Tran wrote: On Mon, Nov 1, 2010 at 3:46 PM, Jason van Zyl ja...@maven.org wrote: On Nov 1, 2010, at 11:24 PM, Dan Tran wrote: On Mon, Nov 1, 2010 at 2:15 PM, Jason van Zyl ja...@maven.org wrote: On Nov 1, 2010, at 10:12 PM, Dennis Lundberg wrote: On 2010-11-01 18:54, Jason van Zyl wrote: Doesn't change the fact it's a hack, generally not useful and is generally not going to get used. It actually is being used. Dennis, are you committed to supporting it? My plan is to close as many issues as I can and release a 1.0, to get rid of one of the last beta-version-plugins :) After that I'm done with it. I do think that this is a useful plugin for those that do not, for whatever reason, have a repository manager, despite its warts. Perhaps a plugin that could move to the Mojo project? There is no need to move stage plugin to MOJO since wagon-maven-plugin covers that feature. So you're saying Dennis applied your patch and you're using the wagon-maven-plugin? My apology, should had withdrawn the request for this fix a long time ago. No, no. I just didn't know they served the same purpose and just wanted to know. If the maven-wagon-plugin is more flexible (I assume it handles all supported transports, not just what I originally hard-coded for Apache stuff a long time ago) then the maven-stage-plugin can probably be retired. Yes, wagon-maven-plugin supports staging and more flexible. So it is safe to retire stage-maven-plugin. That seems most sensible given the guy you applied the patch for could have done it himself at Mojo. If so, that's fine, but it's a dead end plugin as far as I'm concerned. Who's going to use it when all the repository managers have some form of staging? On Nov 1, 2010, at 6:47 PM, Brett Porter wrote: Dennis committed to it just yesterday, so I think calling it unsupported is premature. On 01/11/2010, at 8:39 AM, Jason van Zyl wrote: This was a hack, and has now been replaced with Nexus staging here at Apache (and most other forges). I believe this plugin can be archived now. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - We all have problems. How we deal with them is a measure of our worth. -- Unknown -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason
Re: Setting goals for upcoming releases
What I meant was to release maven 3.0, the dev needs to iron up most of to backward compatibility blocking bugs. ( no work around ) The bug I mentioned sound like a feature that is accidentally take out of maven core which supports flat repository structure. -Dan On Fri, Sep 3, 2010 at 6:28 AM, Jason van Zyl ja...@sonatype.com wrote: I write up a blog entry with the schedule and goals. i'll mention the construction if ITs and point to some examples. On Sep 3, 2010, at 9:10 AM, Brian Fox wrote: On Thu, Sep 2, 2010 at 8:44 PM, Jason van Zyl ja...@sonatype.com wrote: I think trying to release 3.0 sooner, and then sticking to 6 week release cycles would be a better use of time. We're going to fix anything that arises but I don't believe there will be widespread testing until 3.0 is released, and I don't believe many will pick up 3.x in large-scale production environments until 3.1. I think the faster we get 3.0 out the better. Shoot for October 1st, and then have the 3.0.1 release with fixes for the first wave of issues raised in mid-November. Fine with me. Then lets announce that intention to the user list now and get the page updated to make it easy for people to find the betas. On Sep 2, 2010, at 7:34 PM, Brian Fox wrote: Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty safely call it feature complete. I'd like to propose a few goals to get some things done. We have ApacheCon coming up the first week of November, and it would be great to set that as a target to get Maven 3.0 out the door. So far the feedback on the betas has been good but fairly limited. I think that without a clear plan, and our history with this mammoth release, people are probably reluctant to spend a lot of time testing each beta. In the past we've been successful pushing out release candidate builds and involving the user list. If we start that soonish, there should be plenty of time to uncover and fix regressions, especially if everyone pitches in. There's even time to cut another beta before we launch into the RCs if it's needed. So first of all, Benjamin, Herve, Kristian you've collectively done the majority of the work in M3 recently. Do you think the above is achievable and desirable? What does everyone else think? Secondly, For me personally, I'm going to commit to get the Maven Index code committed and to push updated releases of the dependency and enforcer plugins before ApacheCon. Anyone else want to ante up for some chunk of work and get things rolling? Thanks, Brian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - We all have problems. How we deal with them is a measure of our worth. -- Unknown - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Setting goals for upcoming releases
I think i agree with Jason on shooting maven 3.0 out to public as soon as you can, however the dev team might want fix up blocking bugs which prevent user like me from using maven 3 one of the blocking bug for me is http://jira.codehaus.org/browse/MNG-4788 Thanks -Dan On Thu, Sep 2, 2010 at 6:12 PM, Mark Derricutt m...@talios.com wrote: Personally I'd still like to see some resolution to the problems introduced by the version range resolution change ( no more -SNAPSHOT resolution except for on the bounds ). On one hand I applaud the change from a release standpoint, but it currently causes issues for our integration build processes. Two options come to mind: 1) Explicit GAV patterns for -SNAPSHOT resolution get defined somewhere 2) If a GAV is a particpant in a reactor build, it's -SNAPSHOT should be considered kosher for resolution Option 1 would probably require some form of POM change as I don't think the resolution part of a configurable plugin, so most likely can't be done. Option 2 should be fine, as when releasing an individual artifact, nothing external would be in the reactor, unless it was part of the build chain, so no extraneous -SNAPSHOTs would be considered. This should give a fairly good compromise between fixing ranges for release and not breaking existing builds. Each time I've brought the subject up I don't seem to see any traction or replies/discussion come along, is there room to address this somehow? -- Pull me down under... On Fri, Sep 3, 2010 at 11:34 AM, Brian Fox bri...@infinity.nu wrote: Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty safely call it feature complete. I'd like to propose a few goals to get some things done. We have ApacheCon coming up the first week of November, and it would be great to set that as a target to get Maven 3.0 out the door. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r948951 - in /maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg: AbstractGpgMojo.java GpgSigner.java
isn't it better to use File rather than String as argument type for
'executable'?
-D
On Thu, May 27, 2010 at 12:01 PM, bentm...@apache.org wrote:
Author: bentmann
Date: Thu May 27 19:01:26 2010
New Revision: 948951
URL: http://svn.apache.org/viewvc?rev=948951view=rev
Log:
[MGPG-23] Allow gpg executable name and path to be specified
Modified:
maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/AbstractGpgMojo.java
maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/GpgSigner.java
Modified:
maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/AbstractGpgMojo.java
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/AbstractGpgMojo.java?rev=948951r1=948950r2=948951view=diff
==
---
maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/AbstractGpgMojo.java
(original)
+++
maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/AbstractGpgMojo.java
Thu May 27 19:01:26 2010
@@ -72,11 +72,21 @@ public abstract class AbstractGpgMojo
*/
private boolean interactive;
+ /**
+ * The path to the GnuPG executable to use for artifact signing.
Defaults to either gpg or gpg.exe depending on
+ * the operating system.
+ *
+ * @parameter expression=${gpg.executable}
+ * @since 1.1
+ */
+ private String executable;
+
GpgSigner newSigner( MavenProject project )
throws MojoExecutionException, MojoFailureException
{
GpgSigner signer = new GpgSigner();
+ signer.setExecutable( executable );
signer.setInteractive( interactive );
signer.setKeyName( keyname );
signer.setUseAgent( useAgent );
Modified:
maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/GpgSigner.java
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/GpgSigner.java?rev=948951r1=948950r2=948951view=diff
==
---
maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/GpgSigner.java
(original)
+++
maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/GpgSigner.java
Thu May 27 19:01:26 2010
@@ -29,6 +29,7 @@ import java.io.InputStreamReader;
import org.apache.maven.plugin.MojoExecutionException;
import org.apache.maven.project.MavenProject;
import org.codehaus.plexus.util.Os;
+import org.codehaus.plexus.util.StringUtils;
import org.codehaus.plexus.util.cli.CommandLineException;
import org.codehaus.plexus.util.cli.CommandLineUtils;
import org.codehaus.plexus.util.cli.Commandline;
@@ -39,6 +40,8 @@ public class GpgSigner
public static final String SIGNATURE_EXTENSION = .asc;
+ private String executable;
+
private boolean useAgent;
private boolean isInteractive = true;
@@ -55,6 +58,11 @@ public class GpgSigner
private File homeDir;
+ public void setExecutable( String executable )
+ {
+ this.executable = executable;
+ }
+
public void setInteractive( boolean b )
{
isInteractive = b;
@@ -140,7 +148,14 @@ public class GpgSigner
Commandline cmd = new Commandline();
- cmd.setExecutable( gpg + ( Os.isFamily( Os.FAMILY_WINDOWS ) ?
.exe : ) );
+ if ( StringUtils.isNotEmpty( executable ) )
+ {
+ cmd.setExecutable( executable );
+ }
+ else
+ {
+ cmd.setExecutable( gpg + ( Os.isFamily( Os.FAMILY_WINDOWS ) ?
.exe : ) );
+ }
if ( homeDir != null )
{
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: How often Codehaus' repo is sync with MavenCentral?
thanks -D On Sun, May 23, 2010 at 2:16 PM, Brian Fox bri...@infinity.nu wrote: I moved codehaus over to the more frequent sync but had a typo in there. It's running every 4 hours now in conjunction with Apache. On Sun, May 23, 2010 at 4:19 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The sync seems not to have happened since at least 1am GMT+1h Saturday ... shoud see v-m-p version 1.2 in http://repo1.maven.org/maven2/org/codehaus/mojo/versions-maven-plugin/ when the sync runs On 23 May 2010 06:00, Dan Tran dant...@gmail.com wrote: My bad, I was looking at codehaus repo!! intead of maven-central. so the sync has not happened yet -D On Sat, May 22, 2010 at 9:27 PM, Dan Tran dant...@gmail.com wrote: Magic happens :-) I just found it shown up at Maven Central Thanks -Dan On Sat, May 22, 2010 at 8:28 PM, Dan Tran dant...@gmail.com wrote: Hello, I cut a new release of native-maven-plugin at MOJO but after 24 hours I dont see it show up at Maven Central yet? Could someone take a look? Thanks -Dan - 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
How often Codehaus' repo is sync with MavenCentral?
Hello, I cut a new release of native-maven-plugin at MOJO but after 24 hours I dont see it show up at Maven Central yet? Could someone take a look? Thanks -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: How often Codehaus' repo is sync with MavenCentral?
Magic happens :-) I just found it shown up at Maven Central Thanks -Dan On Sat, May 22, 2010 at 8:28 PM, Dan Tran dant...@gmail.com wrote: Hello, I cut a new release of native-maven-plugin at MOJO but after 24 hours I dont see it show up at Maven Central yet? Could someone take a look? Thanks -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: How often Codehaus' repo is sync with MavenCentral?
My bad, I was looking at codehaus repo!! intead of maven-central. so the sync has not happened yet -D On Sat, May 22, 2010 at 9:27 PM, Dan Tran dant...@gmail.com wrote: Magic happens :-) I just found it shown up at Maven Central Thanks -Dan On Sat, May 22, 2010 at 8:28 PM, Dan Tran dant...@gmail.com wrote: Hello, I cut a new release of native-maven-plugin at MOJO but after 24 hours I dont see it show up at Maven Central yet? Could someone take a look? Thanks -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: State of checksums?
I bet there are still lots of checksum issues with maven central, I would suggest to strongly encourage ppl to file issues with MEV and actively fix them -D On Fri, Apr 30, 2010 at 10:19 AM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hi, considering the recent fixes to checksums for stuff in central, I was wondering what's the overall state of (existing) checksums on central these days? Assuming checksums are correct where present, this should put us in a good position to introduce a new checksum policy fail-if-present or just strict some day. The difference to the existing fail policy would be to only fail the build if at least one checksum file to verify is actually present. Making this policy the default for central would reduce the grief caused by Maven happily downloading HTTP status pages and trying to build class paths from HTML files... Benjamin - 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: [RESULT] [VOTE] Release Maven Compiler Plugin 2.2
I think the cause of bad checksum is from using wagon's httpclient alternative see http://maven.apache.org/guides/mini/guide-wagon-providers.html I attempted to use it to deploy large artifact as a work around for OOM issue and saw this problem, but could not confirm if my setup is the problem. However, today i tried it again and able to reproduce the issue. -D On Wed, Apr 21, 2010 at 3:34 AM, Markku Saarela markku.saar...@iki.fi wrote: HHi, This could cause wrong checsums: Quote from Kevan: Maven 2.2 was used in creating the xbean 3.6 release. Evidently 2.2 had an issue uploading files to Nexus twice and calculating checksums on the doubled files. http://old.nabble.com/Maven-central-has-corrupted-artifact-org.apache.xbean%3Axbean-finder-shaded%3Ajar%3A3.6-ts27340027.html#a27340027 rgds, Markku On 21.4.2010 10:14, Milos Kleint wrote: On Wed, Apr 21, 2010 at 8:41 AM, Brett Porterbr...@apache.org wrote: On 21/04/2010, at 3:40 PM, Milos Kleint wrote: hmm... I did the plexus compiler release indeed. No idea how the checksums became broken. I've done the regular release:prepare, release:perform combo. I can't recall any problems with the process. I specifically double checked that there are gpg signatures, but assumed checksums are correct. They never been broken for me before. Did you use Maven 2.1.0, Maven 2.2.0, or the httpclient wagon perhaps? Not sure, I would say 2.2.x. I don't have the computer anymore where I did the release. What do we do now? If the signatures are intact, then we can say the artifacts are and you could upload corrected checksums. Let me know if you need any help. gpg --verify plexus-compiler-javac-1.8.jar.asc gpg --verify plexus-compiler-javac-1.8.pom.asc both say gpg: Signature made Tue Mar 30 00:28:04 2010 CEST using RSA key ID B0874707 gpg: Good signature from Milos Kleintmkle...@apache.org How do I recreate and reupload the correct checksums? thanks. Milos - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - 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: Implementing http://jira.codehaus.org/browse/SCM-526
looks like there is no objection for me to add this missing feature at MOJO level. I will go ahead with that. Thanks -Dan On Wed, Mar 24, 2010 at 10:00 PM, Dan Tran dant...@gmail.com wrote: Hi all, I am thinking of implementing excludes/includes configuration for scm:checkout and scm:export at plugin level ( after scm action execution) It looks easier from that perspective rather than at API level. Any objection? -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Implementing http://jira.codehaus.org/browse/SCM-526
Hi all, I am thinking of implementing excludes/includes configuration for scm:checkout and scm:export at plugin level ( after scm action execution) It looks easier from that perspective rather than at API level. Any objection? -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Have maven goal running in background mode
No, You need to create 2 goals: start and stop with option not to call stop where start thread dies when maven terminates. Is this clear enough? Did you take a look at seleninum plugin I have suggested yesterday? -D On Fri, Mar 19, 2010 at 8:18 PM, Phuong Nguyen phuongn...@gmail.com wrote: Hi: Is there any way to prevent my maven goal from being terminated by maven? For example, I have a goal named RunGoal. In the RunGoal.execute method, I want to instantiate another background-thread and have RunGoal.execute returned. The background-thread should be continued to run while Maven execute another goal. The background-thread is only terminated later (maybe when maven exit or another goal is called). Thanks, Phuong. - 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: Execute a maven goal in the middle of another maven goal
take a look at selenium-maven-plugin, It starts selenium server in the background, run selenium sure fire test, and finally shutdown selenium server good luck -D On Thu, Mar 18, 2010 at 9:55 PM, Phuong Nguyen phuongn...@gmail.com wrote: Hi: Is there anyway to execute a maven goal while another maven goal sleeping? For example, I want to execute a gaeForTest:test goal. This goal will first start Google App Engine Dev Server. After that, I want to start surefire plugin to execute a set of integration tests. When surefire plugin finishes these tests, I will terminate the server. Thanks, Phuong. - 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
Latest maven-scm-plugin 1.4-SNAPSHOT broken
Hello,
My experimental build just pull down latest maven scm and see this
error. Did we break this or it is just a bad jar??
i am using maven 2.2.1 and java 6
[INFO] [scm:checkout {execution: checkout-webservices}]
[FATAL ERROR] org.apache.maven.scm.plugin.CheckoutMojo#execute()
caused a linkage error (java.lang.NoSuchMethodError) and may be
out-of-date. Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.maven.plugins:maven-scm-plugin:1.4-SNAPSHOT]
urls[0] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/plugins/maven-scm-plugin/1.4-SNAPSHOT/maven-scm-plugin-1.4-SNAPSHOT.jar
urls[1] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar
urls[2] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-manager-plexus/1.4-SNAPSHOT/maven-scm-manager-plexus-1.4-SNAPSHOT.jar
urls[3] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-api/1.4-SNAPSHOT/maven-scm-api-1.4-SNAPSHOT.jar
urls[4] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-providers-standard/1.4-SNAPSHOT/maven-scm-providers-standard-1.4-SNAPSHOT.pom
urls[5] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-accurev/1.4-SNAPSHOT/maven-scm-provider-accurev-1.4-SNAPSHOT.jar
urls[6] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-bazaar/1.4-SNAPSHOT/maven-scm-provider-bazaar-1.4-SNAPSHOT.jar
urls[7] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/regexp/regexp/1.3/regexp-1.3.jar
urls[8] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-clearcase/1.4-SNAPSHOT/maven-scm-provider-clearcase-1.4-SNAPSHOT.jar
urls[9] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-cvsexe/1.4-SNAPSHOT/maven-scm-provider-cvsexe-1.4-SNAPSHOT.jar
urls[10] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.4-SNAPSHOT/maven-scm-provider-cvs-commons-1.4-SNAPSHOT.jar
urls[11] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-cvsjava/1.4-SNAPSHOT/maven-scm-provider-cvsjava-1.4-SNAPSHOT.jar
urls[12] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.jar
urls[13] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.jar
urls[14] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-gitexe/1.4-SNAPSHOT/maven-scm-provider-gitexe-1.4-SNAPSHOT.jar
urls[15] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-git-commons/1.4-SNAPSHOT/maven-scm-provider-git-commons-1.4-SNAPSHOT.jar
urls[16] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-hg/1.4-SNAPSHOT/maven-scm-provider-hg-1.4-SNAPSHOT.jar
urls[17] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-perforce/1.4-SNAPSHOT/maven-scm-provider-perforce-1.4-SNAPSHOT.jar
urls[18] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-starteam/1.4-SNAPSHOT/maven-scm-provider-starteam-1.4-SNAPSHOT.jar
urls[19] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-svnexe/1.4-SNAPSHOT/maven-scm-provider-svnexe-1.4-SNAPSHOT.jar
urls[20] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-svn-commons/1.4-SNAPSHOT/maven-scm-provider-svn-commons-1.4-SNAPSHOT.jar
urls[21] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-synergy/1.4-SNAPSHOT/maven-scm-provider-synergy-1.4-SNAPSHOT.jar
urls[22] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-vss/1.4-SNAPSHOT/maven-scm-provider-vss-1.4-SNAPSHOT.jar
urls[23] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-tfs/1.4-SNAPSHOT/maven-scm-provider-tfs-1.4-SNAPSHOT.jar
urls[24] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-local/1.4-SNAPSHOT/maven-scm-provider-local-1.4-SNAPSHOT.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/var/build/tools/maven/lib/maven-2.2.1-uber.jar
[INFO]
[ERROR]
Re: Latest maven-scm-plugin 1.4-SNAPSHOT broken
I am using subversion
where I call scm:checkout in my pom
-Dan
On Fri, Mar 12, 2010 at 1:35 PM, Olivier Lamy ol...@apache.org wrote:
Hi,
How can I reproduce this ?
Which scm are you using ?
2010/3/12 Dan Tran dant...@gmail.com:
Hello,
My experimental build just pull down latest maven scm and see this
error. Did we break this or it is just a bad jar??
i am using maven 2.2.1 and java 6
[INFO] [scm:checkout {execution: checkout-webservices}]
[FATAL ERROR] org.apache.maven.scm.plugin.CheckoutMojo#execute()
caused a linkage error (java.lang.NoSuchMethodError) and may be
out-of-date. Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.maven.plugins:maven-scm-plugin:1.4-SNAPSHOT]
urls[0] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/plugins/maven-scm-plugin/1.4-SNAPSHOT/maven-scm-plugin-1.4-SNAPSHOT.jar
urls[1] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar
urls[2] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-manager-plexus/1.4-SNAPSHOT/maven-scm-manager-plexus-1.4-SNAPSHOT.jar
urls[3] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-api/1.4-SNAPSHOT/maven-scm-api-1.4-SNAPSHOT.jar
urls[4] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-providers-standard/1.4-SNAPSHOT/maven-scm-providers-standard-1.4-SNAPSHOT.pom
urls[5] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-accurev/1.4-SNAPSHOT/maven-scm-provider-accurev-1.4-SNAPSHOT.jar
urls[6] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-bazaar/1.4-SNAPSHOT/maven-scm-provider-bazaar-1.4-SNAPSHOT.jar
urls[7] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/regexp/regexp/1.3/regexp-1.3.jar
urls[8] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-clearcase/1.4-SNAPSHOT/maven-scm-provider-clearcase-1.4-SNAPSHOT.jar
urls[9] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-cvsexe/1.4-SNAPSHOT/maven-scm-provider-cvsexe-1.4-SNAPSHOT.jar
urls[10] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.4-SNAPSHOT/maven-scm-provider-cvs-commons-1.4-SNAPSHOT.jar
urls[11] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-cvsjava/1.4-SNAPSHOT/maven-scm-provider-cvsjava-1.4-SNAPSHOT.jar
urls[12] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.jar
urls[13] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.jar
urls[14] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-gitexe/1.4-SNAPSHOT/maven-scm-provider-gitexe-1.4-SNAPSHOT.jar
urls[15] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-git-commons/1.4-SNAPSHOT/maven-scm-provider-git-commons-1.4-SNAPSHOT.jar
urls[16] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-hg/1.4-SNAPSHOT/maven-scm-provider-hg-1.4-SNAPSHOT.jar
urls[17] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-perforce/1.4-SNAPSHOT/maven-scm-provider-perforce-1.4-SNAPSHOT.jar
urls[18] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-starteam/1.4-SNAPSHOT/maven-scm-provider-starteam-1.4-SNAPSHOT.jar
urls[19] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-svnexe/1.4-SNAPSHOT/maven-scm-provider-svnexe-1.4-SNAPSHOT.jar
urls[20] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-svn-commons/1.4-SNAPSHOT/maven-scm-provider-svn-commons-1.4-SNAPSHOT.jar
urls[21] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-synergy/1.4-SNAPSHOT/maven-scm-provider-synergy-1.4-SNAPSHOT.jar
urls[22] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-vss/1.4-SNAPSHOT/maven-scm-provider-vss-1.4-SNAPSHOT.jar
urls[23] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository/org/apache/maven/scm/maven-scm-provider-tfs/1.4-SNAPSHOT/maven-scm-provider-tfs-1.4-SNAPSHOT.jar
urls[24] =
file:/var/hudson/workspace/logapp-java-5.0-pure-maven/.repository
Re: Latest maven-scm-plugin 1.4-SNAPSHOT broken
I had to expired the cache on my nexus' apache-snapshot repo. Now by build is ok. nexus may have picked up a bad deployment, and it would take a day to get the next one. -Dan On Fri, Mar 12, 2010 at 1:46 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Dan Tran wrote: java.lang.NoSuchMethodError: org.apache.maven.scm.provider.ScmProviderRepository.setPushChanges(Z)V at org.apache.maven.scm.plugin.AbstractScmMojo.getScmRepository(AbstractScmMojo.java:286) Sounds like you don't have the latest snapshot version of maven-scm. Benjamin - 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: [ANN] Surefire 2.5 Released
Good works and thanks for all the time you have put in to push this out. -Dan On Sun, Jan 17, 2010 at 12:29 PM, Stephen Connolly steph...@apache.org wrote: The Maven team is pleased to announce the release of the Sureire, version 2.5 This release includes the maven-surefire-plugin, which executes the unit tests of an application, the maven-surefire-report-plugin, which parses surefire/failsafe test results and renders them to DOXIA creating the web interface version of the test results, as well as the maven-failsafe-plugin, which executes the integration tests of an application. http://maven.apache.org/plugins/maven-surefire-plugin/ http://maven.apache.org/plugins/maven-surefire-report-plugin/ http://maven.apache.org/plugins/maven-failsafe-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.5/version /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId version2.5/version /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-failsafe-plugin/artifactId version2.5/version /plugin Release Notes - Maven Surefire - Version 2.5 ** Bug * [SUREFIRE-502] - Specified classesDirectory is added to the end of the classpath * [SUREFIRE-513] - Surefire Integration Test no longer valid when run with Maven 2.0.9+ * [SUREFIRE-529] - forkMode none deprecated but given as an example in the debugging documentation * [SUREFIRE-571] - Using jUnit 4, fork == always, TestSet triggers static initiailization for all test classes in each forked process. * [SUREFIRE-584] - Integration tests do not work during a release * [SUREFIRE-596] - Junit test output is broken with junit4-7+ ** Improvement * [SUREFIRE-511] - Proposal to use java Map for surefire's systemProperties * [SUREFIRE-585] - Add Swedish translation ** New Feature * [SUREFIRE-555] - Support junit core for parallel running of tests * [SUREFIRE-586] - Add support for Maven Toolchains * [SUREFIRE-589] - Add a help goal * [SUREFIRE-591] - Add maven-failsafe-plugin to surefire project ** Task * [SUREFIRE-565] - Bump to Doxia 1.0 * [SUREFIRE-567] - Review the Doxia Sink calls * [SUREFIRE-588] - Update to Maven Plugin Plugin 2.5.1 * [SUREFIRE-590] - Update to Maven Reporting Impl 2.0.4.3 Enjoy, -The Maven team - 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: Deploy snapshot to apache snapshot repo
Hi Brian, Great, i am looking forward to see the snapshots deployed soon. Should I ping you after few days I dont see them? Big Thanks -Dan On Fri, Jan 15, 2010 at 8:17 AM, Brian Fox bri...@infinity.nu wrote: If it's in the grid, it would be deployed to repository.sonatype.org and I have rao proxying that maven-snapshot folder. I figured it's more bandwidth efficient to proxy requested items than to push every single snapshot from the grid across. On Fri, Jan 15, 2010 at 12:10 AM, Brett Porter br...@apache.org wrote: On 15/01/2010, at 3:38 PM, Dan Tran wrote: they are not there :-) the interested artifacts are quite old. So I guess they are not automatically deployed. Ah, I saw the Jan 15 on https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-dependency-plugin/, but I guess it gets touched regularly. You might need to configure them in the grid. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - 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
Deploy snapshot to apache snapshot repo
I have a need to deploy maven-scm-plugin-1.4-SNAPSHOT and maven-dependency-plugin-2.2-SNAPSHOT. Do they happen automatically? Also how do have get karma to deploy manually? Thanks -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Deploy snapshot to apache snapshot repo
they are not there :-) the interested artifacts are quite old. So I guess they are not automatically deployed. -D On Thu, Jan 14, 2010 at 8:23 PM, Brett Porter br...@apache.org wrote: Try https://repository.apache.org/content/repositories/snapshots/ On 15/01/2010, at 3:10 PM, Dan Tran wrote: I have a need to deploy maven-scm-plugin-1.4-SNAPSHOT and maven-dependency-plugin-2.2-SNAPSHOT. Do they happen automatically? Also how do have get karma to deploy manually? Thanks -Dan - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - 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
