Re: Propose release of assembly plugin
if you are stepping up to make the release, you decide the version number, and you decide if there is enough of a change to merrit your effort. sounds like you feel it is worth your time and you are adding a feature, so it is not a bug fix = 2.3 or 3.0 depending obey how big that feature feels to you - 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 29 Nov 2011 01:18, Benson Margulies bimargul...@gmail.com wrote: I just added a feature I care about, and there's a short list of others pending. By the way, I had to go clear the fix versions from a slew of open JIRAs on this project. Somehow, they all got marked '2.3'. Strangely, JIRA will include open jiras in the release notes if they have the appropriate fix version. Please advise as to the next version #: 2.2.2 or 2.3? To save you the trouble of checking JIRA, here's what would ship as a release today. I think that 570 implies that some others complaining of related items are also fixed. Release Notes - Maven 2.x Assembly Plugin - Version 2.3 ** Bug * [MASSEMBLY-175] - MANIFEST entries are not preserved during assemby * [MASSEMBLY-544] - DependencySet includes filter not working in 2.2 * [MASSEMBLY-561] - Encoding is broken when filtering is enabled * [MASSEMBLY-570] - dependency includes filters don't match wildcard (*) in middle of coordinate segment * [MASSEMBLY-581] - Allow formats in configuration to override descriptor ** Improvement * [MASSEMBLY-562] - [documentation] Add links to Maven Shade plugin ** Task * [MASSEMBLY-547] - The class CommandLineUtils doesn't have an Apache license - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Propose release of assembly plugin
Judging by the current set of changes, I'd go for 2.2.2 Kristian Den 29.11.2011 09:27, skrev Stephen Connolly: if you are stepping up to make the release, you decide the version number, and you decide if there is enough of a change to merrit your effort. sounds like you feel it is worth your time and you are adding a feature, so it is not a bug fix = 2.3 or 3.0 depending obey how big that feature feels to you - 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 29 Nov 2011 01:18, Benson Marguliesbimargul...@gmail.com wrote: I just added a feature I care about, and there's a short list of others pending. By the way, I had to go clear the fix versions from a slew of open JIRAs on this project. Somehow, they all got marked '2.3'. Strangely, JIRA will include open jiras in the release notes if they have the appropriate fix version. Please advise as to the next version #: 2.2.2 or 2.3? To save you the trouble of checking JIRA, here's what would ship as a release today. I think that 570 implies that some others complaining of related items are also fixed. Release Notes - Maven 2.x Assembly Plugin - Version 2.3 ** Bug * [MASSEMBLY-175] - MANIFEST entries are not preserved during assemby * [MASSEMBLY-544] - DependencySet includes filter not working in 2.2 * [MASSEMBLY-561] - Encoding is broken when filtering is enabled * [MASSEMBLY-570] - dependency includes filters don't match wildcard (*) in middle of coordinate segment * [MASSEMBLY-581] - Allow formats in configuration to override descriptor ** Improvement * [MASSEMBLY-562] - [documentation] Add links to Maven Shade plugin ** Task * [MASSEMBLY-547] - The class CommandLineUtils doesn't have an Apache license - 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: Propose release of assembly plugin
+1 On Tue, Nov 29, 2011 at 9:32 AM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: Judging by the current set of changes, I'd go for 2.2.2 Kristian Den 29.11.2011 09:27, skrev Stephen Connolly: if you are stepping up to make the release, you decide the version number, and you decide if there is enough of a change to merrit your effort. sounds like you feel it is worth your time and you are adding a feature, so it is not a bug fix = 2.3 or 3.0 depending obey how big that feature feels to you - 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 29 Nov 2011 01:18, Benson Marguliesbimargulies@gmail.**combimargul...@gmail.com wrote: I just added a feature I care about, and there's a short list of others pending. By the way, I had to go clear the fix versions from a slew of open JIRAs on this project. Somehow, they all got marked '2.3'. Strangely, JIRA will include open jiras in the release notes if they have the appropriate fix version. Please advise as to the next version #: 2.2.2 or 2.3? To save you the trouble of checking JIRA, here's what would ship as a release today. I think that 570 implies that some others complaining of related items are also fixed. Release Notes - Maven 2.x Assembly Plugin - Version 2.3 ** Bug * [MASSEMBLY-175] - MANIFEST entries are not preserved during assemby * [MASSEMBLY-544] - DependencySet includes filter not working in 2.2 * [MASSEMBLY-561] - Encoding is broken when filtering is enabled * [MASSEMBLY-570] - dependency includes filters don't match wildcard (*) in middle of coordinate segment * [MASSEMBLY-581] - Allow formats in configuration to override descriptor ** Improvement * [MASSEMBLY-562] - [documentation] Add links to Maven Shade plugin ** Task * [MASSEMBLY-547] - The class CommandLineUtils doesn't have an Apache license --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven 3.0.4
Just did a release of maven scm and md5/sha1 are there : https://repository.apache.org/content/repositories/maven-265/org/apache/maven/scm/maven-scm-api/1.6/ My env: mbp-olamy:scm olamy$ which mvn /Users/olamy/softs/maven/apache-maven-3.0.4/bin/mvn mbp-olamy:scm olamy$ env | grep MAVEN_OPTS MAVEN_OPTS=-Djava.awt.headless=true -Xmx768m -Xms768m -XX:MaxPermSize=256m -client mbp-olamy:scm olamy$ mvn -v Apache Maven 3.0.4 (r1206075; 2011-11-25 09:20:29+0100) Maven home: /Users/olamy/softs/maven/apache-maven-3.0.4 Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: fr_FR, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac So even I don't like that, I will probably release even with a -1 in the vote thread. Someone else reproduce that ? 2011/11/28 Stephen Connolly stephen.alan.conno...@gmail.com: I will check again tomorrow AM... but no extensions only depend on oss version 7 here is the project https://github.com/stephenc/high-scale-lib and benjamin, here is the unclosed staging repo: com.github.stephenc-299 On 28 November 2011 22:53, Olivier Lamy ol...@apache.org wrote: 2011/11/28 Benjamin Bentmann benjamin.bentm...@udo.edu: Stephen Connolly wrote: I just tried deploying to oss.sonatype.org and with the staged 3.0.4 there were no .md5's or .sha1's deployed to the staging repo Sounds like http://jira.codehaus.org/browse/WAGON-353, so maybe double-check that you don't have that wagon version in there as some extension or plugin dependency. Yup agree wagon release was only for this issue. And frankly I have build the current release with a 3.0.4 build. And md5 are there. https://repository.apache.org/content/repositories/maven-244/org/apache/maven/maven-core/3.0.4/ Benjamin - 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 -- 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
Re: Propose release of assembly plugin
+1 2011/11/29 Stephane Nicoll stephane.nic...@gmail.com: +1 On Tue, Nov 29, 2011 at 9:32 AM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: Judging by the current set of changes, I'd go for 2.2.2 Kristian Den 29.11.2011 09:27, skrev Stephen Connolly: if you are stepping up to make the release, you decide the version number, and you decide if there is enough of a change to merrit your effort. sounds like you feel it is worth your time and you are adding a feature, so it is not a bug fix = 2.3 or 3.0 depending obey how big that feature feels to you - 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 29 Nov 2011 01:18, Benson Marguliesbimargulies@gmail.**combimargul...@gmail.com wrote: I just added a feature I care about, and there's a short list of others pending. By the way, I had to go clear the fix versions from a slew of open JIRAs on this project. Somehow, they all got marked '2.3'. Strangely, JIRA will include open jiras in the release notes if they have the appropriate fix version. Please advise as to the next version #: 2.2.2 or 2.3? To save you the trouble of checking JIRA, here's what would ship as a release today. I think that 570 implies that some others complaining of related items are also fixed. Release Notes - Maven 2.x Assembly Plugin - Version 2.3 ** Bug * [MASSEMBLY-175] - MANIFEST entries are not preserved during assemby * [MASSEMBLY-544] - DependencySet includes filter not working in 2.2 * [MASSEMBLY-561] - Encoding is broken when filtering is enabled * [MASSEMBLY-570] - dependency includes filters don't match wildcard (*) in middle of coordinate segment * [MASSEMBLY-581] - Allow formats in configuration to override descriptor ** Improvement * [MASSEMBLY-562] - [documentation] Add links to Maven Shade plugin ** Task * [MASSEMBLY-547] - The class CommandLineUtils doesn't have an Apache license --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-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
Re: [VOTE] Apache Maven 3.0.4
Just tried a deploy @ mojo and having the same issue I'll try for a minimal pom on local file system, see how that goes On 29 November 2011 08:44, Olivier Lamy ol...@apache.org wrote: Just did a release of maven scm and md5/sha1 are there : https://repository.apache.org/content/repositories/maven-265/org/apache/maven/scm/maven-scm-api/1.6/ My env: mbp-olamy:scm olamy$ which mvn /Users/olamy/softs/maven/apache-maven-3.0.4/bin/mvn mbp-olamy:scm olamy$ env | grep MAVEN_OPTS MAVEN_OPTS=-Djava.awt.headless=true -Xmx768m -Xms768m -XX:MaxPermSize=256m -client mbp-olamy:scm olamy$ mvn -v Apache Maven 3.0.4 (r1206075; 2011-11-25 09:20:29+0100) Maven home: /Users/olamy/softs/maven/apache-maven-3.0.4 Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: fr_FR, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac So even I don't like that, I will probably release even with a -1 in the vote thread. Someone else reproduce that ? 2011/11/28 Stephen Connolly stephen.alan.conno...@gmail.com: I will check again tomorrow AM... but no extensions only depend on oss version 7 here is the project https://github.com/stephenc/high-scale-lib and benjamin, here is the unclosed staging repo: com.github.stephenc-299 On 28 November 2011 22:53, Olivier Lamy ol...@apache.org wrote: 2011/11/28 Benjamin Bentmann benjamin.bentm...@udo.edu: Stephen Connolly wrote: I just tried deploying to oss.sonatype.org and with the staged 3.0.4 there were no .md5's or .sha1's deployed to the staging repo Sounds like http://jira.codehaus.org/browse/WAGON-353, so maybe double-check that you don't have that wagon version in there as some extension or plugin dependency. Yup agree wagon release was only for this issue. And frankly I have build the current release with a 3.0.4 build. And md5 are there. https://repository.apache.org/content/repositories/maven-244/org/apache/maven/maven-core/3.0.4/ Benjamin - 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 -- 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
OK, just tried a simple deploy using a file: based wagon with the staged artifacts... [stephenc@stephenc ~]$ md5 ~/Downloads/apache-maven-3.0.4-bin.tar.gz MD5 (/Users/stephenc/Downloads/apache-maven-3.0.4-bin.tar.gz) = c1e67c7f32929b428266c88f7f62bee4 [stephenc@stephenc ~]$ tar -xzvf ~/Downloads/apache-maven-3.0.4-bin.tar.gz x apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar x apache-maven-3.0.4/lib/maven-embedder-3.0.4.jar x apache-maven-3.0.4/lib/maven-settings-3.0.4.jar x apache-maven-3.0.4/lib/plexus-utils-2.0.6.jar x apache-maven-3.0.4/lib/maven-core-3.0.4.jar x apache-maven-3.0.4/lib/maven-model-3.0.4.jar x apache-maven-3.0.4/lib/maven-settings-builder-3.0.4.jar x apache-maven-3.0.4/lib/plexus-interpolation-1.14.jar x apache-maven-3.0.4/lib/plexus-component-annotations-1.5.5.jar x apache-maven-3.0.4/lib/plexus-sec-dispatcher-1.3.jar x apache-maven-3.0.4/lib/plexus-cipher-1.7.jar x apache-maven-3.0.4/lib/maven-repository-metadata-3.0.4.jar x apache-maven-3.0.4/lib/maven-artifact-3.0.4.jar x apache-maven-3.0.4/lib/maven-plugin-api-3.0.4.jar x apache-maven-3.0.4/lib/sisu-inject-plexus-2.3.0.jar x apache-maven-3.0.4/lib/sisu-inject-bean-2.3.0.jar x apache-maven-3.0.4/lib/sisu-guice-3.1.0-no_aop.jar x apache-maven-3.0.4/lib/sisu-guava-0.9.9.jar x apache-maven-3.0.4/lib/maven-model-builder-3.0.4.jar x apache-maven-3.0.4/lib/maven-aether-provider-3.0.4.jar x apache-maven-3.0.4/lib/aether-api-1.13.jar x apache-maven-3.0.4/lib/aether-spi-1.13.jar x apache-maven-3.0.4/lib/aether-util-1.13.jar x apache-maven-3.0.4/lib/aether-impl-1.13.jar x apache-maven-3.0.4/lib/maven-compat-3.0.4.jar x apache-maven-3.0.4/lib/wagon-provider-api-2.1.jar x apache-maven-3.0.4/lib/commons-cli-1.2.jar x apache-maven-3.0.4/lib/wagon-http-2.1-shaded.jar x apache-maven-3.0.4/lib/wagon-file-2.1.jar x apache-maven-3.0.4/lib/aether-connector-wagon-1.13.jar x apache-maven-3.0.4/LICENSE.txt x apache-maven-3.0.4/NOTICE.txt x apache-maven-3.0.4/README.txt x apache-maven-3.0.4/bin/m2.conf x apache-maven-3.0.4/bin/mvn.bat x apache-maven-3.0.4/bin/mvnDebug.bat x apache-maven-3.0.4/bin/mvn x apache-maven-3.0.4/bin/mvnDebug x apache-maven-3.0.4/bin/mvnyjp x apache-maven-3.0.4/conf/ x apache-maven-3.0.4/conf/settings.xml x apache-maven-3.0.4/lib/ x apache-maven-3.0.4/lib/ext/ x apache-maven-3.0.4/lib/ext/README.txt [stephenc@stephenc ~]$ export MAVEN_HOME=~/apache-maven-3.0.4 [stephenc@stephenc ~]$ export PATH=$MAVEN_HOME/bin:$PATH [stephenc@stephenc ~]$ mvn -version Apache Maven 3.0.4 (r1206075; 2011-11-25 08:20:29+) Maven home: /Users/stephenc/apache-maven-3.0.4 Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.6.8, arch: x86_64, family: mac [stephenc@stephenc ~]$ find file-repo file-repo [stephenc@stephenc ~]$ mvn deploy:deploy-file -Dfile=readme.txt -Durl=file:///Users/stephenc/file-repo/ -Dversion=1.0 -DgroupId=foo -DartifactId=bar -Dpackaging=txt [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Maven Stub Project (No POM) 1 [INFO] [INFO] [INFO] --- maven-deploy-plugin:2.7:deploy-file (default-cli) @ standalone-pom --- Uploading: file:///Users/stephenc/file-repo/foo/bar/1.0/bar-1.0.txt Uploaded: file:///Users/stephenc/file-repo/foo/bar/1.0/bar-1.0.txt (7 B at 1.1 KB/sec) Uploading: file:///Users/stephenc/file-repo/foo/bar/1.0/bar-1.0.pom Uploaded: file:///Users/stephenc/file-repo/foo/bar/1.0/bar-1.0.pom (406 B at 396.5 KB/sec) Downloading: file:///Users/stephenc/file-repo/foo/bar/maven-metadata.xml Uploading: file:///Users/stephenc/file-repo/foo/bar/maven-metadata.xml Uploaded: file:///Users/stephenc/file-repo/foo/bar/maven-metadata.xml (282 B at 275.4 KB/sec) [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 0.553s [INFO] Finished at: Tue Nov 29 09:29:14 GMT 2011 [INFO] Final Memory: 3M/81M [INFO] [stephenc@stephenc ~]$ find file-repofile-repo file-repo/foo file-repo/foo/bar file-repo/foo/bar/1.0 file-repo/foo/bar/1.0/bar-1.0.pom file-repo/foo/bar/1.0/bar-1.0.pom.md5 file-repo/foo/bar/1.0/bar-1.0.pom.sha1 file-repo/foo/bar/1.0/bar-1.0.txt file-repo/foo/bar/1.0/bar-1.0.txt.md5 file-repo/foo/bar/1.0/bar-1.0.txt.sha1 file-repo/foo/bar/maven-metadata.xml file-repo/foo/bar/maven-metadata.xml.md5 file-repo/foo/bar/maven-metadata.xml.sha1 [stephenc@stephenc ~]$ The metadata is there so there may be something wrong with some of the forges' parent poms and wagon 2.1 as I had lack of md5's and sha1's when
Re: [VOTE] Apache Maven 3.0.4
hi Stephen! I did a local install of Apache MyFaces-2.1.6 to a private Nexus and I got the md5 and sha1 Just to be sure: are you really looking under 'browse storage', because 'browse index' doesn't show md5 and sha1 at all? txs and LieGrue, strub - Original Message - From: Stephen Connolly stephen.alan.conno...@gmail.com To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 10:21 AM Subject: Re: [VOTE] Apache Maven 3.0.4 Just tried a deploy @ mojo and having the same issue I'll try for a minimal pom on local file system, see how that goes On 29 November 2011 08:44, Olivier Lamy ol...@apache.org wrote: Just did a release of maven scm and md5/sha1 are there : https://repository.apache.org/content/repositories/maven-265/org/apache/maven/scm/maven-scm-api/1.6/ My env: mbp-olamy:scm olamy$ which mvn /Users/olamy/softs/maven/apache-maven-3.0.4/bin/mvn mbp-olamy:scm olamy$ env | grep MAVEN_OPTS MAVEN_OPTS=-Djava.awt.headless=true -Xmx768m -Xms768m -XX:MaxPermSize=256m -client mbp-olamy:scm olamy$ mvn -v Apache Maven 3.0.4 (r1206075; 2011-11-25 09:20:29+0100) Maven home: /Users/olamy/softs/maven/apache-maven-3.0.4 Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: fr_FR, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac So even I don't like that, I will probably release even with a -1 in the vote thread. Someone else reproduce that ? 2011/11/28 Stephen Connolly stephen.alan.conno...@gmail.com: I will check again tomorrow AM... but no extensions only depend on oss version 7 here is the project https://github.com/stephenc/high-scale-lib and benjamin, here is the unclosed staging repo: com.github.stephenc-299 On 28 November 2011 22:53, Olivier Lamy ol...@apache.org wrote: 2011/11/28 Benjamin Bentmann benjamin.bentm...@udo.edu: Stephen Connolly wrote: I just tried deploying to oss.sonatype.org and with the staged 3.0.4 there were no .md5's or .sha1's deployed to the staging repo Sounds like http://jira.codehaus.org/browse/WAGON-353, so maybe double-check that you don't have that wagon version in there as some extension or plugin dependency. Yup agree wagon release was only for this issue. And frankly I have build the current release with a 3.0.4 build. And md5 are there. https://repository.apache.org/content/repositories/maven-244/org/apache/maven/maven-core/3.0.4/ Benjamin - 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 -- 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 - 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
I have side-by side staging repos with 3.0.3 and 3.0.4, the only change between them was MAVEN_HOME 3.0.3 has the md5's 3.0.4 doesn't for the exact same screen, and oss.sonatype.org refused to close the 3.0.4 deployed release last night because its validation failed due to missing md5's On 29 November 2011 09:37, Mark Struberg strub...@yahoo.de wrote: hi Stephen! I did a local install of Apache MyFaces-2.1.6 to a private Nexus and I got the md5 and sha1 Just to be sure: are you really looking under 'browse storage', because 'browse index' doesn't show md5 and sha1 at all? txs and LieGrue, strub - Original Message - From: Stephen Connolly stephen.alan.conno...@gmail.com To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 10:21 AM Subject: Re: [VOTE] Apache Maven 3.0.4 Just tried a deploy @ mojo and having the same issue I'll try for a minimal pom on local file system, see how that goes On 29 November 2011 08:44, Olivier Lamy ol...@apache.org wrote: Just did a release of maven scm and md5/sha1 are there : https://repository.apache.org/content/repositories/maven-265/org/apache/maven/scm/maven-scm-api/1.6/ My env: mbp-olamy:scm olamy$ which mvn /Users/olamy/softs/maven/apache-maven-3.0.4/bin/mvn mbp-olamy:scm olamy$ env | grep MAVEN_OPTS MAVEN_OPTS=-Djava.awt.headless=true -Xmx768m -Xms768m -XX:MaxPermSize=256m -client mbp-olamy:scm olamy$ mvn -v Apache Maven 3.0.4 (r1206075; 2011-11-25 09:20:29+0100) Maven home: /Users/olamy/softs/maven/apache-maven-3.0.4 Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: fr_FR, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac So even I don't like that, I will probably release even with a -1 in the vote thread. Someone else reproduce that ? 2011/11/28 Stephen Connolly stephen.alan.conno...@gmail.com: I will check again tomorrow AM... but no extensions only depend on oss version 7 here is the project https://github.com/stephenc/high-scale-lib and benjamin, here is the unclosed staging repo: com.github.stephenc-299 On 28 November 2011 22:53, Olivier Lamy ol...@apache.org wrote: 2011/11/28 Benjamin Bentmann benjamin.bentm...@udo.edu: Stephen Connolly wrote: I just tried deploying to oss.sonatype.org and with the staged 3.0.4 there were no .md5's or .sha1's deployed to the staging repo Sounds like http://jira.codehaus.org/browse/WAGON-353, so maybe double-check that you don't have that wagon version in there as some extension or plugin dependency. Yup agree wagon release was only for this issue. And frankly I have build the current release with a 3.0.4 build. And md5 are there. https://repository.apache.org/content/repositories/maven-244/org/apache/maven/maven-core/3.0.4/ Benjamin - 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 -- 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 - 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
Attached are screenshots of a more recent example On 29 November 2011 09:44, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I have side-by side staging repos with 3.0.3 and 3.0.4, the only change between them was MAVEN_HOME 3.0.3 has the md5's 3.0.4 doesn't for the exact same screen, and oss.sonatype.org refused to close the 3.0.4 deployed release last night because its validation failed due to missing md5's On 29 November 2011 09:37, Mark Struberg strub...@yahoo.de wrote: hi Stephen! I did a local install of Apache MyFaces-2.1.6 to a private Nexus and I got the md5 and sha1 Just to be sure: are you really looking under 'browse storage', because 'browse index' doesn't show md5 and sha1 at all? txs and LieGrue, strub - Original Message - From: Stephen Connolly stephen.alan.conno...@gmail.com To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 10:21 AM Subject: Re: [VOTE] Apache Maven 3.0.4 Just tried a deploy @ mojo and having the same issue I'll try for a minimal pom on local file system, see how that goes On 29 November 2011 08:44, Olivier Lamy ol...@apache.org wrote: Just did a release of maven scm and md5/sha1 are there : https://repository.apache.org/content/repositories/maven-265/org/apache/maven/scm/maven-scm-api/1.6/ My env: mbp-olamy:scm olamy$ which mvn /Users/olamy/softs/maven/apache-maven-3.0.4/bin/mvn mbp-olamy:scm olamy$ env | grep MAVEN_OPTS MAVEN_OPTS=-Djava.awt.headless=true -Xmx768m -Xms768m -XX:MaxPermSize=256m -client mbp-olamy:scm olamy$ mvn -v Apache Maven 3.0.4 (r1206075; 2011-11-25 09:20:29+0100) Maven home: /Users/olamy/softs/maven/apache-maven-3.0.4 Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: fr_FR, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac So even I don't like that, I will probably release even with a -1 in the vote thread. Someone else reproduce that ? 2011/11/28 Stephen Connolly stephen.alan.conno...@gmail.com: I will check again tomorrow AM... but no extensions only depend on oss version 7 here is the project https://github.com/stephenc/high-scale-lib and benjamin, here is the unclosed staging repo: com.github.stephenc-299 On 28 November 2011 22:53, Olivier Lamy ol...@apache.org wrote: 2011/11/28 Benjamin Bentmann benjamin.bentm...@udo.edu: Stephen Connolly wrote: I just tried deploying to oss.sonatype.org and with the staged 3.0.4 there were no .md5's or .sha1's deployed to the staging repo Sounds like http://jira.codehaus.org/browse/WAGON-353, so maybe double-check that you don't have that wagon version in there as some extension or plugin dependency. Yup agree wagon release was only for this issue. And frankly I have build the current release with a 3.0.4 build. And md5 are there. https://repository.apache.org/content/repositories/maven-244/org/apache/maven/maven-core/3.0.4/ Benjamin - 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 -- 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 - 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
for got to mention On 29 November 2011 09:44, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I have side-by side staging repos with 3.0.3 and 3.0.4, the only change between them was MAVEN_HOME and PATH 3.0.3 has the md5's 3.0.4 doesn't for the exact same screen, and oss.sonatype.org refused to close the 3.0.4 deployed release last night because its validation failed due to missing md5's On 29 November 2011 09:37, Mark Struberg strub...@yahoo.de wrote: hi Stephen! I did a local install of Apache MyFaces-2.1.6 to a private Nexus and I got the md5 and sha1 Just to be sure: are you really looking under 'browse storage', because 'browse index' doesn't show md5 and sha1 at all? txs and LieGrue, strub - Original Message - From: Stephen Connolly stephen.alan.conno...@gmail.com To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 10:21 AM Subject: Re: [VOTE] Apache Maven 3.0.4 Just tried a deploy @ mojo and having the same issue I'll try for a minimal pom on local file system, see how that goes On 29 November 2011 08:44, Olivier Lamy ol...@apache.org wrote: Just did a release of maven scm and md5/sha1 are there : https://repository.apache.org/content/repositories/maven-265/org/apache/maven/scm/maven-scm-api/1.6/ My env: mbp-olamy:scm olamy$ which mvn /Users/olamy/softs/maven/apache-maven-3.0.4/bin/mvn mbp-olamy:scm olamy$ env | grep MAVEN_OPTS MAVEN_OPTS=-Djava.awt.headless=true -Xmx768m -Xms768m -XX:MaxPermSize=256m -client mbp-olamy:scm olamy$ mvn -v Apache Maven 3.0.4 (r1206075; 2011-11-25 09:20:29+0100) Maven home: /Users/olamy/softs/maven/apache-maven-3.0.4 Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: fr_FR, platform encoding: MacRoman OS name: mac os x, version: 10.7.2, arch: x86_64, family: mac So even I don't like that, I will probably release even with a -1 in the vote thread. Someone else reproduce that ? 2011/11/28 Stephen Connolly stephen.alan.conno...@gmail.com: I will check again tomorrow AM... but no extensions only depend on oss version 7 here is the project https://github.com/stephenc/high-scale-lib and benjamin, here is the unclosed staging repo: com.github.stephenc-299 On 28 November 2011 22:53, Olivier Lamy ol...@apache.org wrote: 2011/11/28 Benjamin Bentmann benjamin.bentm...@udo.edu: Stephen Connolly wrote: I just tried deploying to oss.sonatype.org and with the staged 3.0.4 there were no .md5's or .sha1's deployed to the staging repo Sounds like http://jira.codehaus.org/browse/WAGON-353, so maybe double-check that you don't have that wagon version in there as some extension or plugin dependency. Yup agree wagon release was only for this issue. And frankly I have build the current release with a 3.0.4 build. And md5 are there. https://repository.apache.org/content/repositories/maven-244/org/apache/maven/maven-core/3.0.4/ Benjamin - 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 -- 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 - 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
@Stephen the issue was with wagon-http 2.0 see http://jira.codehaus.org/browse/WAGON-353 I will add a core it test which check deploy of sha1 and md5. 2011/11/29 Stephen Connolly stephen.alan.conno...@gmail.com: OK, just tried a simple deploy using a file: based wagon with the staged artifacts... [stephenc@stephenc ~]$ md5 ~/Downloads/apache-maven-3.0.4-bin.tar.gz MD5 (/Users/stephenc/Downloads/apache-maven-3.0.4-bin.tar.gz) = c1e67c7f32929b428266c88f7f62bee4 [stephenc@stephenc ~]$ tar -xzvf ~/Downloads/apache-maven-3.0.4-bin.tar.gz x apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar x apache-maven-3.0.4/lib/maven-embedder-3.0.4.jar x apache-maven-3.0.4/lib/maven-settings-3.0.4.jar x apache-maven-3.0.4/lib/plexus-utils-2.0.6.jar x apache-maven-3.0.4/lib/maven-core-3.0.4.jar x apache-maven-3.0.4/lib/maven-model-3.0.4.jar x apache-maven-3.0.4/lib/maven-settings-builder-3.0.4.jar x apache-maven-3.0.4/lib/plexus-interpolation-1.14.jar x apache-maven-3.0.4/lib/plexus-component-annotations-1.5.5.jar x apache-maven-3.0.4/lib/plexus-sec-dispatcher-1.3.jar x apache-maven-3.0.4/lib/plexus-cipher-1.7.jar x apache-maven-3.0.4/lib/maven-repository-metadata-3.0.4.jar x apache-maven-3.0.4/lib/maven-artifact-3.0.4.jar x apache-maven-3.0.4/lib/maven-plugin-api-3.0.4.jar x apache-maven-3.0.4/lib/sisu-inject-plexus-2.3.0.jar x apache-maven-3.0.4/lib/sisu-inject-bean-2.3.0.jar x apache-maven-3.0.4/lib/sisu-guice-3.1.0-no_aop.jar x apache-maven-3.0.4/lib/sisu-guava-0.9.9.jar x apache-maven-3.0.4/lib/maven-model-builder-3.0.4.jar x apache-maven-3.0.4/lib/maven-aether-provider-3.0.4.jar x apache-maven-3.0.4/lib/aether-api-1.13.jar x apache-maven-3.0.4/lib/aether-spi-1.13.jar x apache-maven-3.0.4/lib/aether-util-1.13.jar x apache-maven-3.0.4/lib/aether-impl-1.13.jar x apache-maven-3.0.4/lib/maven-compat-3.0.4.jar x apache-maven-3.0.4/lib/wagon-provider-api-2.1.jar x apache-maven-3.0.4/lib/commons-cli-1.2.jar x apache-maven-3.0.4/lib/wagon-http-2.1-shaded.jar x apache-maven-3.0.4/lib/wagon-file-2.1.jar x apache-maven-3.0.4/lib/aether-connector-wagon-1.13.jar x apache-maven-3.0.4/LICENSE.txt x apache-maven-3.0.4/NOTICE.txt x apache-maven-3.0.4/README.txt x apache-maven-3.0.4/bin/m2.conf x apache-maven-3.0.4/bin/mvn.bat x apache-maven-3.0.4/bin/mvnDebug.bat x apache-maven-3.0.4/bin/mvn x apache-maven-3.0.4/bin/mvnDebug x apache-maven-3.0.4/bin/mvnyjp x apache-maven-3.0.4/conf/ x apache-maven-3.0.4/conf/settings.xml x apache-maven-3.0.4/lib/ x apache-maven-3.0.4/lib/ext/ x apache-maven-3.0.4/lib/ext/README.txt [stephenc@stephenc ~]$ export MAVEN_HOME=~/apache-maven-3.0.4 [stephenc@stephenc ~]$ export PATH=$MAVEN_HOME/bin:$PATH [stephenc@stephenc ~]$ mvn -version Apache Maven 3.0.4 (r1206075; 2011-11-25 08:20:29+) Maven home: /Users/stephenc/apache-maven-3.0.4 Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.6.8, arch: x86_64, family: mac [stephenc@stephenc ~]$ find file-repo file-repo [stephenc@stephenc ~]$ mvn deploy:deploy-file -Dfile=readme.txt -Durl=file:///Users/stephenc/file-repo/ -Dversion=1.0 -DgroupId=foo -DartifactId=bar -Dpackaging=txt [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Maven Stub Project (No POM) 1 [INFO] [INFO] [INFO] --- maven-deploy-plugin:2.7:deploy-file (default-cli) @ standalone-pom --- Uploading: file:///Users/stephenc/file-repo/foo/bar/1.0/bar-1.0.txt Uploaded: file:///Users/stephenc/file-repo/foo/bar/1.0/bar-1.0.txt (7 B at 1.1 KB/sec) Uploading: file:///Users/stephenc/file-repo/foo/bar/1.0/bar-1.0.pom Uploaded: file:///Users/stephenc/file-repo/foo/bar/1.0/bar-1.0.pom (406 B at 396.5 KB/sec) Downloading: file:///Users/stephenc/file-repo/foo/bar/maven-metadata.xml Uploading: file:///Users/stephenc/file-repo/foo/bar/maven-metadata.xml Uploaded: file:///Users/stephenc/file-repo/foo/bar/maven-metadata.xml (282 B at 275.4 KB/sec) [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 0.553s [INFO] Finished at: Tue Nov 29 09:29:14 GMT 2011 [INFO] Final Memory: 3M/81M [INFO] [stephenc@stephenc ~]$ find file-repofile-repo file-repo/foo file-repo/foo/bar file-repo/foo/bar/1.0 file-repo/foo/bar/1.0/bar-1.0.pom file-repo/foo/bar/1.0/bar-1.0.pom.md5 file-repo/foo/bar/1.0/bar-1.0.pom.sha1 file-repo/foo/bar/1.0/bar-1.0.txt file-repo/foo/bar/1.0/bar-1.0.txt.md5 file-repo/foo/bar/1.0/bar-1.0.txt.sha1 file-repo/foo/bar/maven-metadata.xml file-repo/foo/bar/maven-metadata.xml.md5
[fluido] Css fix for search
Current search button in fludio is not using bootstrapped css. Here is patch which make it look more nicely. Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de - 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
Even with a clean local repo, .md5's are still not being deployed for me... If this is an issue with the embedded WAGON (and it is looking like it could be) then I have to change my vote back negative -0.9 (binding) [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Failed to transfer file: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom.sha1. Return code is: 411, ReasonPhrase:Length Required. org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom.sha1. Return code is: 411, ReasonPhrase:Length Required. at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:586) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:495) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.putFromStream(AbstractHttpClientWagon.java:489) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.putFromStream(AbstractHttpClientWagon.java:935) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) [DEBUG] Failed to upload MD5 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Failed to transfer file: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom.md5. Return code is: 411, ReasonPhrase:Length Required. org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom.md5. Return code is: 411, ReasonPhrase:Length Required. at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:586) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:495) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.putFromStream(AbstractHttpClientWagon.java:489) at
Re: [fluido] Css fix for search
ML didn't let me sent hte patches, here is the issue: https://jira.codehaus.org/browse/MSKINS-13 On Tue, Nov 29, 2011 at 10:58 AM, Christian Grobmeier grobme...@gmail.com wrote: Current search button in fludio is not using bootstrapped css. Here is patch which make it look more nicely. Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de -- http://www.grobmeier.de https://www.timeandbill.de - 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
That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) And if I try without extensions [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Failed to transfer file: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom.sha1. Return code is: 411, ReasonPhrase:Length Required. org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom.sha1. Return code is: 411, ReasonPhrase:Length Required. at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:586) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:495) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.putFromStream(AbstractHttpClientWagon.java:489) at
Re: [VOTE] Apache Maven 3.0.4
I see the same checksum issue when trying to deploy a snapshot over at Codehaus mojo: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/jboss-packaging-maven-plugin/2.3-SNAPSHOT/ I'm changing my vote to -1 (non-binding). IMHO we do not want end user issues due to something like this. /Anders On Tue, Nov 29, 2011 at 11:09, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) And if I try without extensions [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Failed to transfer file: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom.sha1. Return code is: 411, ReasonPhrase:Length Required. org.apache.maven.wagon.TransferFailedException: Failed to transfer file:
Re: [fluido] Upgrading version
my fault: http://maven.apache.org/skins/maven-fluido-skin/source-repository.html this shows the tag which is the version i have created the patch against On Tue, Nov 29, 2011 at 10:57 AM, Christian Grobmeier grobme...@gmail.com wrote: Hello, shouldnt fluido have v1.1-SNAPSHOP in trunk? Patch attached. Cheers -- http://www.grobmeier.de https://www.timeandbill.de -- http://www.grobmeier.de https://www.timeandbill.de - 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
I think delivering artifacts without md5 and sha1 is pretty much a blocker as this might introduce security issues along the line. So I'd say we investigate further before we go ahead. Thus I change my vote to a -1 (binding) also. We now have a few cases which work well and a few cases which cause this error. Means we have to check where the difference is. LieGrue, strub - Original Message - From: Anders Hammar and...@hammar.net To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 11:14 AM Subject: Re: [VOTE] Apache Maven 3.0.4 I see the same checksum issue when trying to deploy a snapshot over at Codehaus mojo: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/jboss-packaging-maven-plugin/2.3-SNAPSHOT/ I'm changing my vote to -1 (non-binding). IMHO we do not want end user issues due to something like this. /Anders On Tue, Nov 29, 2011 at 11:09, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at
Re: [VOTE] Apache Maven 3.0.4
Olivier Lamy wrote: I will add a core it test which check deploy of sha1 and md5. You might want to check MavenITmng4235HttpAuthDeploymentChecksumsTest before. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Propose release of assembly plugin
Folks, A couple of thoughts in response to Stephen: The convention seems pretty clear to send a 'yoo-hoo' before starting a release in case anyone is dying to add something. Since I had to do that anyway, I thought I might as well solicit input on the version number. I did get poked once about the sensibility of releasing on a short list, albeit from a visitor, but he is a very distinguished visitor, so that left me cautious. Off I go. In fact I need to run a component release first. --benson On Tue, Nov 29, 2011 at 3:44 AM, Olivier Lamy ol...@apache.org wrote: +1 2011/11/29 Stephane Nicoll stephane.nic...@gmail.com: +1 On Tue, Nov 29, 2011 at 9:32 AM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: Judging by the current set of changes, I'd go for 2.2.2 Kristian Den 29.11.2011 09:27, skrev Stephen Connolly: if you are stepping up to make the release, you decide the version number, and you decide if there is enough of a change to merrit your effort. sounds like you feel it is worth your time and you are adding a feature, so it is not a bug fix = 2.3 or 3.0 depending obey how big that feature feels to you - 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 29 Nov 2011 01:18, Benson Marguliesbimargulies@gmail.**combimargul...@gmail.com wrote: I just added a feature I care about, and there's a short list of others pending. By the way, I had to go clear the fix versions from a slew of open JIRAs on this project. Somehow, they all got marked '2.3'. Strangely, JIRA will include open jiras in the release notes if they have the appropriate fix version. Please advise as to the next version #: 2.2.2 or 2.3? To save you the trouble of checking JIRA, here's what would ship as a release today. I think that 570 implies that some others complaining of related items are also fixed. Release Notes - Maven 2.x Assembly Plugin - Version 2.3 ** Bug * [MASSEMBLY-175] - MANIFEST entries are not preserved during assemby * [MASSEMBLY-544] - DependencySet includes filter not working in 2.2 * [MASSEMBLY-561] - Encoding is broken when filtering is enabled * [MASSEMBLY-570] - dependency includes filters don't match wildcard (*) in middle of coordinate segment * [MASSEMBLY-581] - Allow formats in configuration to override descriptor ** Improvement * [MASSEMBLY-562] - [documentation] Add links to Maven Shade plugin ** Task * [MASSEMBLY-547] - The class CommandLineUtils doesn't have an Apache license --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-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
[fluido] Upgrading version
Hello, shouldnt fluido have v1.1-SNAPSHOP in trunk? Patch attached. Cheers -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Propose release of assembly plugin
On 29 November 2011 11:17, Benson Margulies bimargul...@gmail.com wrote: Folks, A couple of thoughts in response to Stephen: The convention seems pretty clear to send a 'yoo-hoo' before starting a release in case anyone is dying to add something. Since I had to do that anyway, I thought I might as well solicit input on the version number. No worries, it's best practice to say that you want to run a release in say 24hr unless anyone has any blocking issues they think need to be fixed first... but at the end of the day, if you have the energy to release right now and you likely won't have the energy to make the release later, I say just go ahead and run the release. My point is lets not waste energy when we have it... calling vote-like threads before you do something has the potential to waste your energy when you have it, or the potential to miss a window where you could make the release (i.e. your significant other or dependents suddenly need your attention just after the vote-like has ended, and now you cannot deliver on making the release)... so we should not be in the habit of wasting energy... I tend to know that I will have a window of energy to do a release tomorrow (say) in which case I ping the ML with a heads up... but if I suddenly had a window of energy and felt the itch to make a release of something, then I would say push the release, no delays ;-) I did get poked once about the sensibility of releasing on a short list, albeit from a visitor, but he is a very distinguished visitor, so that left me cautious. Well at the end of the day, the release manager is in charge... and who is the release manager? whoever (from the set of committers) has the energy to make a release _now_. Off I go. In fact I need to run a component release first. Good luck! --benson On Tue, Nov 29, 2011 at 3:44 AM, Olivier Lamy ol...@apache.org wrote: +1 2011/11/29 Stephane Nicoll stephane.nic...@gmail.com: +1 On Tue, Nov 29, 2011 at 9:32 AM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: Judging by the current set of changes, I'd go for 2.2.2 Kristian Den 29.11.2011 09:27, skrev Stephen Connolly: if you are stepping up to make the release, you decide the version number, and you decide if there is enough of a change to merrit your effort. sounds like you feel it is worth your time and you are adding a feature, so it is not a bug fix = 2.3 or 3.0 depending obey how big that feature feels to you - 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 29 Nov 2011 01:18, Benson Marguliesbimargulies@gmail.**com bimargul...@gmail.com wrote: I just added a feature I care about, and there's a short list of others pending. By the way, I had to go clear the fix versions from a slew of open JIRAs on this project. Somehow, they all got marked '2.3'. Strangely, JIRA will include open jiras in the release notes if they have the appropriate fix version. Please advise as to the next version #: 2.2.2 or 2.3? To save you the trouble of checking JIRA, here's what would ship as a release today. I think that 570 implies that some others complaining of related items are also fixed. Release Notes - Maven 2.x Assembly Plugin - Version 2.3 ** Bug * [MASSEMBLY-175] - MANIFEST entries are not preserved during assemby * [MASSEMBLY-544] - DependencySet includes filter not working in 2.2 * [MASSEMBLY-561] - Encoding is broken when filtering is enabled * [MASSEMBLY-570] - dependency includes filters don't match wildcard (*) in middle of coordinate segment * [MASSEMBLY-581] - Allow formats in configuration to override descriptor ** Improvement * [MASSEMBLY-562] - [documentation] Add links to Maven Shade plugin ** Task * [MASSEMBLY-547] - The class CommandLineUtils doesn't have an Apache license --**--** - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org 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,
Re: [VOTE] Apache Maven 3.0.4
Agree I will cancel the vote to investigate more. I wonder why it works when deploying maven scm to repository.apache.org and tested on a locally installed nexus instance ? Can nexus folks who are listening here explains to me in which case this happen http Return code: 411, ReasonPhrase:Length Required. Bad or empty Content-Length http header ? 2011/11/29 Mark Struberg strub...@yahoo.de: I think delivering artifacts without md5 and sha1 is pretty much a blocker as this might introduce security issues along the line. So I'd say we investigate further before we go ahead. Thus I change my vote to a -1 (binding) also. We now have a few cases which work well and a few cases which cause this error. Means we have to check where the difference is. LieGrue, strub - Original Message - From: Anders Hammar and...@hammar.net To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 11:14 AM Subject: Re: [VOTE] Apache Maven 3.0.4 I see the same checksum issue when trying to deploy a snapshot over at Codehaus mojo: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/jboss-packaging-maven-plugin/2.3-SNAPSHOT/ I'm changing my vote to -1 (non-binding). IMHO we do not want end user issues due to something like this. /Anders On Tue, Nov 29, 2011 at 11:09, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at
[VOTE] release maven-common-artifact-filters 1.4
Hi, We solved an issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-QX7G-9IAS%7C083f4f243731b9ee702e76ba2ccc07788ab70ac3%7Clinversion=16798styleName=TextprojectId=11761Create=Create Release Notes - Maven Shared Components - Version maven-common-artifact-filters-1.4 ** Bug * [MSHARED-205] - wildcard in middle of artifact-coordinate segment not recognized in Pattern*ArtifactFilter There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=component+%3D+maven-common-artifact-filters+AND+project+%3D+MSHARED+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-266/ Staging site: http://maven.apache.org/shared/maven-common-artifact-filters-1.4 (staged) 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 Maven 3.0.4
2011/11/29 Benjamin Bentmann benjamin.bentm...@udo.edu: Olivier Lamy wrote: I will add a core it test which check deploy of sha1 and md5. You might want to check MavenITmng4235HttpAuthDeploymentChecksumsTest before. Thanks. And btw this it pass well :-) Benjamin - 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
[CANCEL VOTE] Apache Maven 3.0.4
So due to issues when releasing project and missing md5/sha1 on some env whereas not on other. The vote is cancelled for more investigations. 2011/11/25 Olivier Lamy ol...@apache.org: Hello, I'd like to release Apache Maven 3.0.4. We fixed 31 issues. See release notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=17215 The staged repo is available here: https://repository.apache.org/content/repositories/maven-244/ . 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 (which is around 120 hours) [+1] [0] [-1] Here my +1 Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- 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
Re: [VOTE] Apache Maven 3.0.4
Hi, Nexus does not respond with HTTP 411. It has to be some nexus-fronting app (httpd or nginx?) And I am 99% confident that according to RFC[1], this was a case of incomplete request or such. As I inspected, nexus@codehaus is fronted by nginx 0.8.24 By googling, I found this: http://www.lamnk.com/blog/computer/fix-nginx-411-length-required-error/ [1] http://tools.ietf.org/html/rfc2616 Thanks, ~t~ On Tue, Nov 29, 2011 at 12:35 PM, Olivier Lamy ol...@apache.org wrote: Agree I will cancel the vote to investigate more. I wonder why it works when deploying maven scm to repository.apache.org and tested on a locally installed nexus instance ? Can nexus folks who are listening here explains to me in which case this happen http Return code: 411, ReasonPhrase:Length Required. Bad or empty Content-Length http header ? 2011/11/29 Mark Struberg strub...@yahoo.de: I think delivering artifacts without md5 and sha1 is pretty much a blocker as this might introduce security issues along the line. So I'd say we investigate further before we go ahead. Thus I change my vote to a -1 (binding) also. We now have a few cases which work well and a few cases which cause this error. Means we have to check where the difference is. LieGrue, strub - Original Message - From: Anders Hammar and...@hammar.net To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 11:14 AM Subject: Re: [VOTE] Apache Maven 3.0.4 I see the same checksum issue when trying to deploy a snapshot over at Codehaus mojo: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/jboss-packaging-maven-plugin/2.3-SNAPSHOT/ I'm changing my vote to -1 (non-binding). IMHO we do not want end user issues due to something like this. /Anders On Tue, Nov 29, 2011 at 11:09, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at
Re: [VOTE] Apache Maven 3.0.4
Thanks. That's what I have seen. Content-Lenght is null because chunked is used. I will enhance core it to ensure Content-Length header is correct and update wagon http to fix that. BTW canceling a release because a http server does not support chunck is a pain 2011/11/29 Tamás Cservenák ta...@cservenak.net: Hi, Nexus does not respond with HTTP 411. It has to be some nexus-fronting app (httpd or nginx?) And I am 99% confident that according to RFC[1], this was a case of incomplete request or such. As I inspected, nexus@codehaus is fronted by nginx 0.8.24 By googling, I found this: http://www.lamnk.com/blog/computer/fix-nginx-411-length-required-error/ [1] http://tools.ietf.org/html/rfc2616 Thanks, ~t~ On Tue, Nov 29, 2011 at 12:35 PM, Olivier Lamy ol...@apache.org wrote: Agree I will cancel the vote to investigate more. I wonder why it works when deploying maven scm to repository.apache.org and tested on a locally installed nexus instance ? Can nexus folks who are listening here explains to me in which case this happen http Return code: 411, ReasonPhrase:Length Required. Bad or empty Content-Length http header ? 2011/11/29 Mark Struberg strub...@yahoo.de: I think delivering artifacts without md5 and sha1 is pretty much a blocker as this might introduce security issues along the line. So I'd say we investigate further before we go ahead. Thus I change my vote to a -1 (binding) also. We now have a few cases which work well and a few cases which cause this error. Means we have to check where the difference is. LieGrue, strub - Original Message - From: Anders Hammar and...@hammar.net To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 11:14 AM Subject: Re: [VOTE] Apache Maven 3.0.4 I see the same checksum issue when trying to deploy a snapshot over at Codehaus mojo: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/jboss-packaging-maven-plugin/2.3-SNAPSHOT/ I'm changing my vote to -1 (non-binding). IMHO we do not want end user issues due to something like this. /Anders On Tue, Nov 29, 2011 at 11:09, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at
Re: [VOTE] Apache Maven 3.0.4
Out of curiosity, why is chunked transfer encoding used to transfer the few byte long SHA1 string? Personally, I'd avoid the use of chunked whenever possible, since -- just like this example shows -- many servers does not support it completely... Thanks, ~t~ On Tue, Nov 29, 2011 at 1:21 PM, Olivier Lamy ol...@apache.org wrote: Thanks. That's what I have seen. Content-Lenght is null because chunked is used. I will enhance core it to ensure Content-Length header is correct and update wagon http to fix that. BTW canceling a release because a http server does not support chunck is a pain 2011/11/29 Tamás Cservenák ta...@cservenak.net: Hi, Nexus does not respond with HTTP 411. It has to be some nexus-fronting app (httpd or nginx?) And I am 99% confident that according to RFC[1], this was a case of incomplete request or such. As I inspected, nexus@codehaus is fronted by nginx 0.8.24 By googling, I found this: http://www.lamnk.com/blog/computer/fix-nginx-411-length-required-error/ [1] http://tools.ietf.org/html/rfc2616 Thanks, ~t~ On Tue, Nov 29, 2011 at 12:35 PM, Olivier Lamy ol...@apache.org wrote: Agree I will cancel the vote to investigate more. I wonder why it works when deploying maven scm to repository.apache.org and tested on a locally installed nexus instance ? Can nexus folks who are listening here explains to me in which case this happen http Return code: 411, ReasonPhrase:Length Required. Bad or empty Content-Length http header ? 2011/11/29 Mark Struberg strub...@yahoo.de: I think delivering artifacts without md5 and sha1 is pretty much a blocker as this might introduce security issues along the line. So I'd say we investigate further before we go ahead. Thus I change my vote to a -1 (binding) also. We now have a few cases which work well and a few cases which cause this error. Means we have to check where the difference is. LieGrue, strub - Original Message - From: Anders Hammar and...@hammar.net To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 11:14 AM Subject: Re: [VOTE] Apache Maven 3.0.4 I see the same checksum issue when trying to deploy a snapshot over at Codehaus mojo: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/jboss-packaging-maven-plugin/2.3-SNAPSHOT/ I'm changing my vote to -1 (non-binding). IMHO we do not want end user issues due to something like this. /Anders On Tue, Nov 29, 2011 at 11:09, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) at
Re: [VOTE] Apache Maven 3.0.4
because for those files the streaming api is used. something like putFromStream( InputStream stream, String destination ) so to know the size I will have to dump the stream to a tmp file to calculate the size. (crazy) 2011/11/29 Tamás Cservenák ta...@cservenak.net: Out of curiosity, why is chunked transfer encoding used to transfer the few byte long SHA1 string? Personally, I'd avoid the use of chunked whenever possible, since -- just like this example shows -- many servers does not support it completely... Thanks, ~t~ On Tue, Nov 29, 2011 at 1:21 PM, Olivier Lamy ol...@apache.org wrote: Thanks. That's what I have seen. Content-Lenght is null because chunked is used. I will enhance core it to ensure Content-Length header is correct and update wagon http to fix that. BTW canceling a release because a http server does not support chunck is a pain 2011/11/29 Tamás Cservenák ta...@cservenak.net: Hi, Nexus does not respond with HTTP 411. It has to be some nexus-fronting app (httpd or nginx?) And I am 99% confident that according to RFC[1], this was a case of incomplete request or such. As I inspected, nexus@codehaus is fronted by nginx 0.8.24 By googling, I found this: http://www.lamnk.com/blog/computer/fix-nginx-411-length-required-error/ [1] http://tools.ietf.org/html/rfc2616 Thanks, ~t~ On Tue, Nov 29, 2011 at 12:35 PM, Olivier Lamy ol...@apache.org wrote: Agree I will cancel the vote to investigate more. I wonder why it works when deploying maven scm to repository.apache.org and tested on a locally installed nexus instance ? Can nexus folks who are listening here explains to me in which case this happen http Return code: 411, ReasonPhrase:Length Required. Bad or empty Content-Length http header ? 2011/11/29 Mark Struberg strub...@yahoo.de: I think delivering artifacts without md5 and sha1 is pretty much a blocker as this might introduce security issues along the line. So I'd say we investigate further before we go ahead. Thus I change my vote to a -1 (binding) also. We now have a few cases which work well and a few cases which cause this error. Means we have to check where the difference is. LieGrue, strub - Original Message - From: Anders Hammar and...@hammar.net To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 11:14 AM Subject: Re: [VOTE] Apache Maven 3.0.4 I see the same checksum issue when trying to deploy a snapshot over at Codehaus mojo: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/jboss-packaging-maven-plugin/2.3-SNAPSHOT/ I'm changing my vote to -1 (non-binding). IMHO we do not want end user issues due to something like this. /Anders On Tue, Nov 29, 2011 at 11:09, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at
Re: [VOTE] Apache Maven 3.0.4
btw for who interested benjamin (thanks !) did a quick change on aether to have content length passed to wagon which fix the issue (a core it test has been changed to failed in case chunked is used) I'm waiting now the release 1.14 available in central to start again the release process. 2011/11/29 Olivier Lamy ol...@apache.org: because for those files the streaming api is used. something like putFromStream( InputStream stream, String destination ) so to know the size I will have to dump the stream to a tmp file to calculate the size. (crazy) 2011/11/29 Tamás Cservenák ta...@cservenak.net: Out of curiosity, why is chunked transfer encoding used to transfer the few byte long SHA1 string? Personally, I'd avoid the use of chunked whenever possible, since -- just like this example shows -- many servers does not support it completely... Thanks, ~t~ On Tue, Nov 29, 2011 at 1:21 PM, Olivier Lamy ol...@apache.org wrote: Thanks. That's what I have seen. Content-Lenght is null because chunked is used. I will enhance core it to ensure Content-Length header is correct and update wagon http to fix that. BTW canceling a release because a http server does not support chunck is a pain 2011/11/29 Tamás Cservenák ta...@cservenak.net: Hi, Nexus does not respond with HTTP 411. It has to be some nexus-fronting app (httpd or nginx?) And I am 99% confident that according to RFC[1], this was a case of incomplete request or such. As I inspected, nexus@codehaus is fronted by nginx 0.8.24 By googling, I found this: http://www.lamnk.com/blog/computer/fix-nginx-411-length-required-error/ [1] http://tools.ietf.org/html/rfc2616 Thanks, ~t~ On Tue, Nov 29, 2011 at 12:35 PM, Olivier Lamy ol...@apache.org wrote: Agree I will cancel the vote to investigate more. I wonder why it works when deploying maven scm to repository.apache.org and tested on a locally installed nexus instance ? Can nexus folks who are listening here explains to me in which case this happen http Return code: 411, ReasonPhrase:Length Required. Bad or empty Content-Length http header ? 2011/11/29 Mark Struberg strub...@yahoo.de: I think delivering artifacts without md5 and sha1 is pretty much a blocker as this might introduce security issues along the line. So I'd say we investigate further before we go ahead. Thus I change my vote to a -1 (binding) also. We now have a few cases which work well and a few cases which cause this error. Means we have to check where the difference is. LieGrue, strub - Original Message - From: Anders Hammar and...@hammar.net To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 11:14 AM Subject: Re: [VOTE] Apache Maven 3.0.4 I see the same checksum issue when trying to deploy a snapshot over at Codehaus mojo: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/jboss-packaging-maven-plugin/2.3-SNAPSHOT/ I'm changing my vote to -1 (non-binding). IMHO we do not want end user issues due to something like this. /Anders On Tue, Nov 29, 2011 at 11:09, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at
Re: [VOTE] Apache Maven 3.0.4
CXF has a nice CachedOutputStream that fits into this space. Let me know of I can help. On Tue, Nov 29, 2011 at 6:35 AM, Olivier Lamy ol...@apache.org wrote: Agree I will cancel the vote to investigate more. I wonder why it works when deploying maven scm to repository.apache.org and tested on a locally installed nexus instance ? Can nexus folks who are listening here explains to me in which case this happen http Return code: 411, ReasonPhrase:Length Required. Bad or empty Content-Length http header ? 2011/11/29 Mark Struberg strub...@yahoo.de: I think delivering artifacts without md5 and sha1 is pretty much a blocker as this might introduce security issues along the line. So I'd say we investigate further before we go ahead. Thus I change my vote to a -1 (binding) also. We now have a few cases which work well and a few cases which cause this error. Means we have to check where the difference is. LieGrue, strub - Original Message - From: Anders Hammar and...@hammar.net To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 11:14 AM Subject: Re: [VOTE] Apache Maven 3.0.4 I see the same checksum issue when trying to deploy a snapshot over at Codehaus mojo: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/jboss-packaging-maven-plugin/2.3-SNAPSHOT/ I'm changing my vote to -1 (non-binding). IMHO we do not want end user issues due to something like this. /Anders On Tue, Nov 29, 2011 at 11:09, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/ as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:885) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:167) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:149) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at
Accelerating nested releases
This morning, I considered the following: 1) Stage maven-common-filters 1.4 and call a vote 2) Make a settings.xml for myself that included the staging repo. 3) Update maven-assembly-plugin to use maven-common-filters 1.4, building using the settings.xml. 4) stage maven-assembly-plugin and call a vote, explaining how to duplicate the configuration for testing. Then I realized that the jenkins builds would break. Then I realized that, if we have an up-to-date enough Jenkins, I could temporarily add the same settings.xml to the job. WDYT? - 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
1.13.1 AFAIR on irc :-) On Tue, Nov 29, 2011 at 2:17 PM, Olivier Lamy ol...@apache.org wrote: btw for who interested benjamin (thanks !) did a quick change on aether to have content length passed to wagon which fix the issue (a core it test has been changed to failed in case chunked is used) I'm waiting now the release 1.14 available in central to start again the release process. 2011/11/29 Olivier Lamy ol...@apache.org: because for those files the streaming api is used. something like putFromStream( InputStream stream, String destination ) so to know the size I will have to dump the stream to a tmp file to calculate the size. (crazy) 2011/11/29 Tamás Cservenák ta...@cservenak.net: Out of curiosity, why is chunked transfer encoding used to transfer the few byte long SHA1 string? Personally, I'd avoid the use of chunked whenever possible, since -- just like this example shows -- many servers does not support it completely... Thanks, ~t~ On Tue, Nov 29, 2011 at 1:21 PM, Olivier Lamy ol...@apache.org wrote: Thanks. That's what I have seen. Content-Lenght is null because chunked is used. I will enhance core it to ensure Content-Length header is correct and update wagon http to fix that. BTW canceling a release because a http server does not support chunck is a pain 2011/11/29 Tamás Cservenák ta...@cservenak.net: Hi, Nexus does not respond with HTTP 411. It has to be some nexus-fronting app (httpd or nginx?) And I am 99% confident that according to RFC[1], this was a case of incomplete request or such. As I inspected, nexus@codehaus is fronted by nginx 0.8.24 By googling, I found this: http://www.lamnk.com/blog/computer/fix-nginx-411-length-required-error/ [1] http://tools.ietf.org/html/rfc2616 Thanks, ~t~ On Tue, Nov 29, 2011 at 12:35 PM, Olivier Lamy ol...@apache.org wrote: Agree I will cancel the vote to investigate more. I wonder why it works when deploying maven scm to repository.apache.org and tested on a locally installed nexus instance ? Can nexus folks who are listening here explains to me in which case this happen http Return code: 411, ReasonPhrase:Length Required. Bad or empty Content-Length http header ? 2011/11/29 Mark Struberg strub...@yahoo.de: I think delivering artifacts without md5 and sha1 is pretty much a blocker as this might introduce security issues along the line. So I'd say we investigate further before we go ahead. Thus I change my vote to a -1 (binding) also. We now have a few cases which work well and a few cases which cause this error. Means we have to check where the difference is. LieGrue, strub - Original Message - From: Anders Hammar and...@hammar.net To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, November 29, 2011 11:14 AM Subject: Re: [VOTE] Apache Maven 3.0.4 I see the same checksum issue when trying to deploy a snapshot over at Codehaus mojo: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/jboss-packaging-maven-plugin/2.3-SNAPSHOT/ I'm changing my vote to -1 (non-binding). IMHO we do not want end user issues due to something like this. /Anders On Tue, Nov 29, 2011 at 11:09, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That stacktrace was with extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version2.1/version /extension /extensions in the pom... if I try extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-http/artifactId version1.0/version /extension /extensions I get [DEBUG] Using connector WagonRepositoryConnector with priority 0 for https://nexus.codehaus.org/service/local/staging/deploy/maven2/as stephenconnolly Uploading: https://nexus.codehaus.org/service/local/staging/deploy/maven2/org/codehaus/mojo/mrm/1.0-alpha-1/mrm-1.0-alpha-1.pom Nov 29, 2011 10:06:08 AM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme INFO: basic authentication scheme selected [DEBUG] Failed to upload SHA-1 checksum for /Users/stephenc/codehaus/mrm/target/checkout/pom.xml: Should not be using the streaming wagon for HTTP PUT java.lang.IllegalStateException: Should not be using the streaming wagon for HTTP PUT at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillOutputData(AbstractHttpClientWagon.java:692) at org.apache.maven.wagon.StreamWagon.getOutputStream(StreamWagon.java:188) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:272) at org.apache.maven.wagon.StreamWagon.putFromStream(StreamWagon.java:252) at
[VOTE] Apache Maven SCM 1.6
Hello, I'd like to release Apache Maven SCM 1.6 We fixed 18 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17296styleName=TextprojectId=10527Create=Create Staged repo: https://repository.apache.org/content/repositories/maven-265/ Staging site: http://maven.apache.org/scm-1.6/ (note the use of the new skin :-) ). [+1]: [ 0] : [-1] : Here my +1. Thanks, -- 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
Fluido skin for Maven sites Re: [VOTE] Apache Maven SCM 1.6
Just a useless thing : Could it be possible to have the feather logo vertically centered and with the same width of the Maven logo to have it aligned ? My 0,0001 cents On Tue, Nov 29, 2011 at 2:26 PM, Olivier Lamy ol...@apache.org wrote: Hello, I'd like to release Apache Maven SCM 1.6 We fixed 18 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17296styleName=TextprojectId=10527Create=Create Staged repo: https://repository.apache.org/content/repositories/maven-265/ Staging site: http://maven.apache.org/scm-1.6/ (note the use of the new skin :-) ). [+1]: [ 0] : [-1] : Here my +1. Thanks, -- 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
Re: [VOTE] Apache Maven SCM 1.6
2011/11/29 Olivier Lamy ol...@apache.org: Hello, I'd like to release Apache Maven SCM 1.6 We fixed 18 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17296styleName=TextprojectId=10527Create=Create Staged repo: https://repository.apache.org/content/repositories/maven-265/ Staging site: http://maven.apache.org/scm-1.6/ (note the use of the new skin :-) ). [+1]: [ 0] : [-1] : Here my +1. Missed to say vote open for the usual 72H. Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- 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
Re: [VOTE] Apache Maven 3.0.4
Tamás Cservenák wrote: Out of curiosity, why is chunked transfer encoding used to transfer the few byte long SHA1 string? https://issues.sonatype.org/browse/AETHER-128 many servers does not support it completely... Which suggests to deprecate the problematic method in the StreamingWagon API. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
deprecate a method for wagon stream api (was Re: [VOTE] Apache Maven 3.0.4 )
2011/11/29 Benjamin Bentmann benjamin.bentm...@udo.edu: Tamás Cservenák wrote: Out of curiosity, why is chunked transfer encoding used to transfer the few byte long SHA1 string? https://issues.sonatype.org/browse/AETHER-128 many servers does not support it completely... Which suggests to deprecate the problematic method in the StreamingWagon API. Agree I will . Benjamin - 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
Re: Accelerating nested releases
I'd just vote on both at the same time... jenkins can fail if it wants... or I can see about getting Apache a license for skippy (a.k.a. CloudBee's Skip Builds plugin) On 29 November 2011 13:22, Benson Margulies bimargul...@gmail.com wrote: This morning, I considered the following: 1) Stage maven-common-filters 1.4 and call a vote 2) Make a settings.xml for myself that included the staging repo. 3) Update maven-assembly-plugin to use maven-common-filters 1.4, building using the settings.xml. 4) stage maven-assembly-plugin and call a vote, explaining how to duplicate the configuration for testing. Then I realized that the jenkins builds would break. Then I realized that, if we have an up-to-date enough Jenkins, I could temporarily add the same settings.xml to the job. WDYT? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Accelerating nested releases
What I'm doing at eXo to manage such cascading releases without having a huge manual process to keep everything up-to-date is that I have a profile that allow to activate a group with all staging repositories. Jenkins is allowed to take artifacts from this staging group BUT it has to delete all local repositories every night. Thus if a project has to republish something in staging then Jenkins will be up-to-date at the maximum after 24h It's far from beeing perfect but at least there is no/few management cost on jenkins side and we can chain releases with few maven settings. I don't know if we could have a similar setup here. Arnaud On Tue, Nov 29, 2011 at 3:01 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I'd just vote on both at the same time... jenkins can fail if it wants... or I can see about getting Apache a license for skippy (a.k.a. CloudBee's Skip Builds plugin) On 29 November 2011 13:22, Benson Margulies bimargul...@gmail.com wrote: This morning, I considered the following: 1) Stage maven-common-filters 1.4 and call a vote 2) Make a settings.xml for myself that included the staging repo. 3) Update maven-assembly-plugin to use maven-common-filters 1.4, building using the settings.xml. 4) stage maven-assembly-plugin and call a vote, explaining how to duplicate the configuration for testing. Then I realized that the jenkins builds would break. Then I realized that, if we have an up-to-date enough Jenkins, I could temporarily add the same settings.xml to the job. WDYT? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [CANCEL VOTE] Apache Maven 3.0.4
I think doing RCs like we have done in the past for all other 3.x releases might be a good idea. On Nov 29, 2011, at 4:00 AM, Olivier Lamy wrote: So due to issues when releasing project and missing md5/sha1 on some env whereas not on other. The vote is cancelled for more investigations. 2011/11/25 Olivier Lamy ol...@apache.org: Hello, I'd like to release Apache Maven 3.0.4. We fixed 31 issues. See release notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=17215 The staged repo is available here: https://repository.apache.org/content/repositories/maven-244/ . 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 (which is around 120 hours) [+1] [0] [-1] Here my +1 Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- 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 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
Re: Accelerating nested releases
2011/11/29 Arnaud Héritier aherit...@gmail.com: What I'm doing at eXo to manage such cascading releases without having a huge manual process to keep everything up-to-date is that I have a profile that allow to activate a group with all staging repositories. Jenkins is allowed to take artifacts from this staging group BUT it has to delete all local repositories every night. Thus if a project has to republish something in staging then Jenkins will be up-to-date at the maximum after 24h It's far from beeing perfect but at least there is no/few management cost on jenkins side and we can chain releases with few maven settings. I don't know if we could have a similar setup here. I asked the nexus list if it is possible to define a repository group that consists of all the currently pending (e.g. closed) repositories on our group ID. We could then define the jenkins jobs to always use it, and CI would always test against anything out for a vote. Arnaud On Tue, Nov 29, 2011 at 3:01 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I'd just vote on both at the same time... jenkins can fail if it wants... or I can see about getting Apache a license for skippy (a.k.a. CloudBee's Skip Builds plugin) On 29 November 2011 13:22, Benson Margulies bimargul...@gmail.com wrote: This morning, I considered the following: 1) Stage maven-common-filters 1.4 and call a vote 2) Make a settings.xml for myself that included the staging repo. 3) Update maven-assembly-plugin to use maven-common-filters 1.4, building using the settings.xml. 4) stage maven-assembly-plugin and call a vote, explaining how to duplicate the configuration for testing. Then I realized that the jenkins builds would break. Then I realized that, if we have an up-to-date enough Jenkins, I could temporarily add the same settings.xml to the job. WDYT? - 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
Staging path for sites for components seem a bit verbose to me
http://maven.apache.org/shared/maven-common-artifact-filters-1.4/shared/maven-common-artifact-filters/ Is this on purpose or by accident? There seem to be two extra directories to me. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] release maven-common-artifact-filters 1.4
The site is in fact sitting at http://maven.apache.org/shared/maven-common-artifact-filters-1.4/shared/maven-common-artifact-filters/. On Tue, Nov 29, 2011 at 6:44 AM, Benson Margulies bimargul...@apache.org wrote: Hi, We solved an issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-QX7G-9IAS%7C083f4f243731b9ee702e76ba2ccc07788ab70ac3%7Clinversion=16798styleName=TextprojectId=11761Create=Create Release Notes - Maven Shared Components - Version maven-common-artifact-filters-1.4 ** Bug * [MSHARED-205] - wildcard in middle of artifact-coordinate segment not recognized in Pattern*ArtifactFilter There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=component+%3D+maven-common-artifact-filters+AND+project+%3D+MSHARED+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-266/ Staging site: http://maven.apache.org/shared/maven-common-artifact-filters-1.4 (staged) 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: Staging path for sites for components seem a bit verbose to me
Hi Yes, it's a bug in the site plugin. It's fixed in the next version. On Tuesday, November 29, 2011, Benson Margulies bimargul...@gmail.com wrote: http://maven.apache.org/shared/maven-common-artifact-filters-1.4/shared/maven-common-artifact-filters/ Is this on purpose or by accident? There seem to be two extra directories to me. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg
Re: Accelerating nested releases
Indeed nexus has a feature that allows a single, persistent, group, to map to whatever staging repos we have pending. I've opened an INFRA ticket to make use of this, and I will proceed to improve the Jenkins jobs to use it unless someone objects. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Accelerating nested releases
Will need the jenkins jobs to clean their local repo periodically in case of re-votes On 29 November 2011 15:24, Benson Margulies bimargul...@gmail.com wrote: Indeed nexus has a feature that allows a single, persistent, group, to map to whatever staging repos we have pending. I've opened an INFRA ticket to make use of this, and I will proceed to improve the Jenkins jobs to use it unless someone objects. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Accelerating nested releases
On Tue, Nov 29, 2011 at 10:25 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Will need the jenkins jobs to clean their local repo periodically in case of re-votes On 29 November 2011 15:24, Benson Margulies bimargul...@gmail.com wrote: Indeed nexus has a feature that allows a single, persistent, group, to map to whatever staging repos we have pending. I've opened an INFRA ticket to make use of this, and I will proceed to improve the Jenkins jobs to use it unless someone objects. Not a bad idea in any case if you ask me. - 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: Staging path for sites for components seem a bit verbose to me
Oh, good, I don't need to do anything. On Tue, Nov 29, 2011 at 10:17 AM, Dennis Lundberg dennisl.apa...@gmail.com wrote: Hi Yes, it's a bug in the site plugin. It's fixed in the next version. On Tuesday, November 29, 2011, Benson Margulies bimargul...@gmail.com wrote: http://maven.apache.org/shared/maven-common-artifact-filters-1.4/shared/maven-common-artifact-filters/ Is this on purpose or by accident? There seem to be two extra directories to me. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Fluido skin for Maven sites Re: [VOTE] Apache Maven SCM 1.6
Salut Arnaud! of course, I need to check my designer skills but I'm sure we can do it :) In that case I think that missing alignment is due to the fact that the right logo is bigger than the feather one and the Bootstrap css pushed on top images. Thanks for the feedback! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ 2011/11/29 Arnaud Héritier aherit...@gmail.com: Just a useless thing : Could it be possible to have the feather logo vertically centered and with the same width of the Maven logo to have it aligned ? My 0,0001 cents On Tue, Nov 29, 2011 at 2:26 PM, Olivier Lamy ol...@apache.org wrote: Hello, I'd like to release Apache Maven SCM 1.6 We fixed 18 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17296styleName=TextprojectId=10527Create=Create Staged repo: https://repository.apache.org/content/repositories/maven-265/ Staging site: http://maven.apache.org/scm-1.6/ (note the use of the new skin :-) ). [+1]: [ 0] : [-1] : Here my +1. Thanks, -- 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
[VOTE] release maven-assembly-plugin version 2.2.2
Hi, We solved N issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126version=13669 There are still a couple of issues left in JIRA: https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+MASSEMBLY+AND+status+%3D+Open+ORDER+BY+priority+DESCmode=hide Staging repo: https://repository.apache.org/content/repositories/maven-268/ Staging site: http://maven.apache.org/plugins/maven-assembly-plugin-2.2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html NOTE: this release was built using the staged version of maven-common-filters-1.4. Add https://repository.apache.org/content/groups/staging/ to your repository list to test. 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
We now now have our own staging group
https://issues.apache.org/jira/browse/INFRA-4163 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: We now now have our own staging group
On Wed, Nov 30, 2011 at 3:34 AM, Benson Margulies bimargul...@gmail.com wrote: https://issues.apache.org/jira/browse/INFRA-4163 I read that issue, but I don't understand how its meant to be used. And I suspect its my lack of understanding of Nexus. Are you able to give an overview or point me at the docs I haven't read yet. Thanks. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: We now now have our own staging group
On Tue, Nov 29, 2011 at 5:37 PM, Barrie Treloar baerr...@gmail.com wrote: On Wed, Nov 30, 2011 at 3:34 AM, Benson Margulies bimargul...@gmail.com wrote: https://issues.apache.org/jira/browse/INFRA-4163 I read that issue, but I don't understand how its meant to be used. And I suspect its my lack of understanding of Nexus. Are you able to give an overview or point me at the docs I haven't read yet. So, whenever we stage a release, Nexus creates a private repository just for that one release of that one item. That's the URL sent around in release votes. You can put that URL into a repository, but once the release is promoted, it goes away. What Brian set up is a virtual repository that aggregates all the private repos of this kind for things in our groupId (org.apache.maven). So, if you add a repository with that URL, and pending releases are visible to you. This enables a number of interesting things. First, if you put that in your settings.xml, you can now do tests of any Maven release up for a vote without having to manually configure the url of the vote thread. Second, an RM can stage a release of a shared component, and then go ahead and modify something else to use it, and stage a release of *that*. Thanks. - 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: We now now have our own staging group
On Wed, Nov 30, 2011 at 9:33 AM, Benson Margulies bimargul...@gmail.com wrote: Are you able to give an overview or point me at the docs I haven't read yet. So, whenever we stage a release, Nexus creates a private repository just for that one release of that one item. That's the URL sent around in release votes. You can put that URL into a repository, but once the release is promoted, it goes away. What Brian set up is a virtual repository that aggregates all the private repos of this kind for things in our groupId (org.apache.maven). So, if you add a repository with that URL, and pending releases are visible to you. This enables a number of interesting things. First, if you put that in your settings.xml, you can now do tests of any Maven release up for a vote without having to manually configure the url of the vote thread. Second, an RM can stage a release of a shared component, and then go ahead and modify something else to use it, and stage a release of *that*. Sweet thanks. Having to muck around with settings.xml for release votes is painful for me. Being behind a firewall makes it annoying. I can set this up once and forget about it. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: We now now have our own staging group
yep... now all we need is a way to easily purge if the vote is cancelled - 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 30 Nov 2011 00:24, Barrie Treloar baerr...@gmail.com wrote: On Wed, Nov 30, 2011 at 9:33 AM, Benson Margulies bimargul...@gmail.com wrote: Are you able to give an overview or point me at the docs I haven't read yet. So, whenever we stage a release, Nexus creates a private repository just for that one release of that one item. That's the URL sent around in release votes. You can put that URL into a repository, but once the release is promoted, it goes away. What Brian set up is a virtual repository that aggregates all the private repos of this kind for things in our groupId (org.apache.maven). So, if you add a repository with that URL, and pending releases are visible to you. This enables a number of interesting things. First, if you put that in your settings.xml, you can now do tests of any Maven release up for a vote without having to manually configure the url of the vote thread. Second, an RM can stage a release of a shared component, and then go ahead and modify something else to use it, and stage a release of *that*. Sweet thanks. Having to muck around with settings.xml for release votes is painful for me. Being behind a firewall makes it annoying. I can set this up once and forget about it. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: We now now have our own staging group
purge local repo and any caching proxies in between that is - 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 30 Nov 2011 05:16, Stephen Connolly stephen.alan.conno...@gmail.com wrote: yep... now all we need is a way to easily purge if the vote is cancelled - 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 30 Nov 2011 00:24, Barrie Treloar baerr...@gmail.com wrote: On Wed, Nov 30, 2011 at 9:33 AM, Benson Margulies bimargul...@gmail.com wrote: Are you able to give an overview or point me at the docs I haven't read yet. So, whenever we stage a release, Nexus creates a private repository just for that one release of that one item. That's the URL sent around in release votes. You can put that URL into a repository, but once the release is promoted, it goes away. What Brian set up is a virtual repository that aggregates all the private repos of this kind for things in our groupId (org.apache.maven). So, if you add a repository with that URL, and pending releases are visible to you. This enables a number of interesting things. First, if you put that in your settings.xml, you can now do tests of any Maven release up for a vote without having to manually configure the url of the vote thread. Second, an RM can stage a release of a shared component, and then go ahead and modify something else to use it, and stage a release of *that*. Sweet thanks. Having to muck around with settings.xml for release votes is painful for me. Being behind a firewall makes it annoying. I can set this up once and forget about it. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: deprecate a method for wagon stream api (was Re: [VOTE] Apache Maven 3.0.4 )
Note that it wasn't really called until r1179571, so I think maybe the
http-shared module should go back to not supporting it. I suppose that was
added for Aether, which in turn is no longer needed :)
While looking at that I noticed this code is probably being called for anything
using the new putFromStream:
FileOutputStream fos = null;
try
{
this.source = File.createTempFile( http-wagon., .tmp );
this.source.deleteOnExit();
fos = new FileOutputStream( this.source );
IOUtil.copy( stream, fos );
John authored this code a long time ago:
http://svn.apache.org/viewvc?view=revisionrevision=786701. I get the feeling
with your recent changes this hack might no longer be necessary.
Finally, why do we still have both http-shared and http-shared4?
- Brett
On 30/11/2011, at 12:59 AM, Olivier Lamy wrote:
2011/11/29 Benjamin Bentmann benjamin.bentm...@udo.edu:
Tamás Cservenák wrote:
Out of curiosity, why is chunked transfer encoding used to transfer
the few byte long SHA1 string?
https://issues.sonatype.org/browse/AETHER-128
many servers does not support it
completely...
Which suggests to deprecate the problematic method in the StreamingWagon
API.
Agree I will .
Benjamin
-
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
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: We now now have our own staging group
To purge the local repo we have a jenkins plugin that can be used : https://wiki.jenkins-ci.org/display/JENKINS/Maven+Repo+Cleaner+Plugin (note that these days I have a doubt that it doesn't have a bug thus if we are using it at Apache too it could help us to stabilize it :-) ) For real HTTP proxy I'm not sure we could do something. The solution might be to have the good http header to not put these binaries in cache but I don't think that Nexus has such feature. This was a problem that shouldn't occur before because URLs were changing if we restaged something For MRMs they shouldn't be use to cache such group/repo excepted if they have the ability to update released binaries (I'm not sure for Nexus users). For local repo, it doesn't change, we have to purge it manually. On Wed, Nov 30, 2011 at 6:49 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: purge local repo and any caching proxies in between that is - 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 30 Nov 2011 05:16, Stephen Connolly stephen.alan.conno...@gmail.com wrote: yep... now all we need is a way to easily purge if the vote is cancelled - 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 30 Nov 2011 00:24, Barrie Treloar baerr...@gmail.com wrote: On Wed, Nov 30, 2011 at 9:33 AM, Benson Margulies bimargul...@gmail.com wrote: Are you able to give an overview or point me at the docs I haven't read yet. So, whenever we stage a release, Nexus creates a private repository just for that one release of that one item. That's the URL sent around in release votes. You can put that URL into a repository, but once the release is promoted, it goes away. What Brian set up is a virtual repository that aggregates all the private repos of this kind for things in our groupId (org.apache.maven). So, if you add a repository with that URL, and pending releases are visible to you. This enables a number of interesting things. First, if you put that in your settings.xml, you can now do tests of any Maven release up for a vote without having to manually configure the url of the vote thread. Second, an RM can stage a release of a shared component, and then go ahead and modify something else to use it, and stage a release of *that*. Sweet thanks. Having to muck around with settings.xml for release votes is painful for me. Being behind a firewall makes it annoying. I can set this up once and forget about it. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
