Re: deprecate a method for wagon stream api (was Re: [VOTE] Apache Maven 3.0.4 )
Hello,
2011/11/30 Brett Porter br...@apache.org:
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.
Yup agree. I will try to remove that.
Finally, why do we still have both http-shared and http-shared4?
IMHO there is a design issue here (see WAGON-359), those two modules
have the same classes in the same package
(org.apache.maven.wagon.shared.http).
@mark any good reason for that ? :-)
As now there is nothing shared now, because dav jackrabbit use
httpclient3 and http wagon use httpcli4, those classes can move to
their own modules. Or at least the package in shared4 must be change!
For some backward comp, I tend to be for package rename and keep those
http-shared* modules in 2.x (and remove it in 3.x)
Others ?
- 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
--
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, Olivier Lamy wrote: 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 I tried the new version with our global build project, but it seems that the new version takes a lot more PermGen space than before. M303 could build all ~400 projects with 144MB PermGen space, but M304 bails out after building 2/3rd of the projects. Anyone else facing increased PermGen space consumption? - Jörg - 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
Now you mention it I have - but I've often seen some of our builds randomly blow out of memory during some of our tests so I can't confirm its M304 at fault or not. ( mind you - I was running Jason's Sonatype M304 dist before that so its possible its there among a number of the newer builds... -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Wed, Nov 30, 2011 at 9:41 PM, Jörg Schaible joerg.schai...@scalaris.comwrote: ~400 projects with 144MB PermGen space, but M304 bails out after building 2/3rd of the projects. Anyone else facing increased PermGen space consumption?
Re: [VOTE] Apache Maven 3.0.4
Did you verify that you're using all the same plugins/versions ? You might consider running something like jvisualvm attached to both 3.0.3 and 3.0.4 to see if your 3.0.3 build is just millimeters away from failing on permgen already ;) Kristian Den 30.11.2011 09:41, skrev Jörg Schaible: Hi, Olivier Lamy wrote: 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 I tried the new version with our global build project, but it seems that the new version takes a lot more PermGen space than before. M303 could build all ~400 projects with 144MB PermGen space, but M304 bails out after building 2/3rd of the projects. Anyone else facing increased PermGen space consumption? - Jörg - 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
Migration plan to commons-exec
Some time ago I did a very thorough review of commons-exec as a replacement for executeCommandLine in plexus-utils. commons-exec is a relative of plexus-utils executeCommandLine, as can be seen from the initial project description at https://github.com/apache/commons-exec/blob/trunk/STATUS . I was very pleased with the code (and vastly superiour test coverage!) and I would like to replace its usage in /all/ of maven in one operation. I went through all the patches we have applied to plexus-utils and I have one more minor patch that I'll get simo/olamy to apply for commons-exec, and thereafter hopefully release a minor update to commons-exec. When that is done I figured I'd do all the maven clients in one sitting. WDYT ? Kristian - 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
@Jörg any open source projects you can share ? What kind of builds are you doing ? install deploy ? with an empty repo or an already populated one ? is there any reporting done (site plugin use) ? etc... Any stack trace you could provide ? Perso, I have tested this build with asf projects with huge build (cxf and camel). Note my MAVEN_OPTS is export MAVEN_OPTS=-Djava.awt.headless=true -Xmx768m -Xms768m -XX:MaxPermSize=256m -client Could you add -XX:+HeapDumpOnOutOfMemoryError in your MAVEN_OPTS ? (-XX:HeapDumpPath= to control the path where it's generated- Maybe this can help us to see what's the issue. IMHO the reasons for that is probably in external libraries update, we did. Changes I see are in 3.0.4 from 3.0.3 * new wagon http: light one 1.0-beta-7 to http 2.1 * aether 1.11 to 1.13.1 * sisu-inject* 2.1.1 to 2.3.0 (with sisu-guice too 2.9.4 to 3.1.0) If you have a bit of time to play with changes back (one by one) to lib and test ? 2011/11/30 Kristian Rosenvold kristian.rosenv...@gmail.com: Did you verify that you're using all the same plugins/versions ? You might consider running something like jvisualvm attached to both 3.0.3 and 3.0.4 to see if your 3.0.3 build is just millimeters away from failing on permgen already ;) Kristian Den 30.11.2011 09:41, skrev Jörg Schaible: Hi, Olivier Lamy wrote: 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 I tried the new version with our global build project, but it seems that the new version takes a lot more PermGen space than before. M303 could build all ~400 projects with 144MB PermGen space, but M304 bails out after building 2/3rd of the projects. Anyone else facing increased PermGen space consumption? - Jörg - 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: Migration plan to commons-exec
wearing both caps of commons PMC and maven Committer, I'm (not binding) +1 :) Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Wed, Nov 30, 2011 at 11:13 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Some time ago I did a very thorough review of commons-exec as a replacement for executeCommandLine in plexus-utils. commons-exec is a relative of plexus-utils executeCommandLine, as can be seen from the initial project description at https://github.com/apache/commons-exec/blob/trunk/STATUS . I was very pleased with the code (and vastly superiour test coverage!) and I would like to replace its usage in /all/ of maven in one operation. I went through all the patches we have applied to plexus-utils and I have one more minor patch that I'll get simo/olamy to apply for commons-exec, and thereafter hopefully release a minor update to commons-exec. When that is done I figured I'd do all the maven clients in one sitting. WDYT ? Kristian - 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: Migration plan to commons-exec
Sounds good: +1 2011/11/30 Kristian Rosenvold kristian.rosenv...@gmail.com: Some time ago I did a very thorough review of commons-exec as a replacement for executeCommandLine in plexus-utils. commons-exec is a relative of plexus-utils executeCommandLine, as can be seen from the initial project description at https://github.com/apache/commons-exec/blob/trunk/STATUS . I was very pleased with the code (and vastly superiour test coverage!) and I would like to replace its usage in /all/ of maven in one operation. I went through all the patches we have applied to plexus-utils and I have one more minor patch that I'll get simo/olamy to apply for commons-exec, and thereafter hopefully release a minor update to commons-exec. When that is done I figured I'd do all the maven clients in one sitting. WDYT ? Kristian - 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: Migration plan to commons-exec
Great! Long overdue. (I see it's 6 years 4 months since I checked in the STATUS file on commons-exec, with this very intent... :) On 30/11/2011, at 9:13 PM, Kristian Rosenvold wrote: Some time ago I did a very thorough review of commons-exec as a replacement for executeCommandLine in plexus-utils. commons-exec is a relative of plexus-utils executeCommandLine, as can be seen from the initial project description at https://github.com/apache/commons-exec/blob/trunk/STATUS . I was very pleased with the code (and vastly superiour test coverage!) and I would like to replace its usage in /all/ of maven in one operation. I went through all the patches we have applied to plexus-utils and I have one more minor patch that I'll get simo/olamy to apply for commons-exec, and thereafter hopefully release a minor update to commons-exec. When that is done I figured I'd do all the maven clients in one sitting. WDYT ? Kristian - 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: Migration plan to commons-exec
as we Italian says: better later than never, we now have the chance to improve both commons-exec and maven! :) All the best! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Wed, Nov 30, 2011 at 11:39 AM, Brett Porter br...@apache.org wrote: Great! Long overdue. (I see it's 6 years 4 months since I checked in the STATUS file on commons-exec, with this very intent... :) On 30/11/2011, at 9:13 PM, Kristian Rosenvold wrote: Some time ago I did a very thorough review of commons-exec as a replacement for executeCommandLine in plexus-utils. commons-exec is a relative of plexus-utils executeCommandLine, as can be seen from the initial project description at https://github.com/apache/commons-exec/blob/trunk/STATUS . I was very pleased with the code (and vastly superiour test coverage!) and I would like to replace its usage in /all/ of maven in one operation. I went through all the patches we have applied to plexus-utils and I have one more minor patch that I'll get simo/olamy to apply for commons-exec, and thereafter hopefully release a minor update to commons-exec. When that is done I figured I'd do all the maven clients in one sitting. WDYT ? Kristian - 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 - 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 Oliver, Olivier Lamy wrote: @Jörg any open source projects you can share ? Sorry, no, but I am try some runs now on a dedicated build server ... a run takes some time though What kind of builds are you doing ? install deploy ? mvn clean install with an empty repo or an already populated one ? populated is there any reporting done (site plugin use) no ? etc... Any stack trace you could provide ? Perso, I have tested this build with asf projects with huge build (cxf and camel). Note my MAVEN_OPTS is export MAVEN_OPTS=-Djava.awt.headless=true -Xmx768m -Xms768m -XX:MaxPermSize=256m -client Mine are -Xmx1g -XX:MaxPermSize=144m. PermSize was chosen to allow such a build to succeed. Could you add -XX:+HeapDumpOnOutOfMemoryError in your MAVEN_OPTS ? (-XX:HeapDumpPath= to control the path where it's generated- Maybe this can help us to see what's the issue. OK, I try to repeat the situation first on the build server above. IMHO the reasons for that is probably in external libraries update, we did. Changes I see are in 3.0.4 from 3.0.3 * new wagon http: light one 1.0-beta-7 to http 2.1 * aether 1.11 to 1.13.1 * sisu-inject* 2.1.1 to 2.3.0 (with sisu-guice too 2.9.4 to 3.1.0) If you have a bit of time to play with changes back (one by one) to lib and test ? When I have a stable environment for this :) 2011/11/30 Kristian Rosenvold kristian.rosenv...@gmail.com: Did you verify that you're using all the same plugins/versions ? All involved plugins are pinned in a global pluginMgmt section. You might consider running something like jvisualvm attached to both 3.0.3 and 3.0.4 to see if your 3.0.3 build is just millimeters away from failing on permgen already ;) I don't know about jvisualvm, but yes, the build with M303 will use nearly all of the 144m PermSpace. However, M304 runs out of resources after 66% of the involved projects. Just for the records: % === $ mvn --version Apache Maven 3.0.4 (r1206075; 2011-11-25 09:20:29+0100) Maven home: /usr/share/maven-bin-3.0 Java version: 1.6.0_29, vendor: Sun Microsystems Inc. Java home: /opt/sun-jdk-1.6.0.29/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.0.6-gentoo, arch: i386, family: unix % === - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Migration plan to commons-exec
+1 On Nov 30, 2011, at 2:13 AM, Kristian Rosenvold wrote: Some time ago I did a very thorough review of commons-exec as a replacement for executeCommandLine in plexus-utils. commons-exec is a relative of plexus-utils executeCommandLine, as can be seen from the initial project description at https://github.com/apache/commons-exec/blob/trunk/STATUS . I was very pleased with the code (and vastly superiour test coverage!) and I would like to replace its usage in /all/ of maven in one operation. I went through all the patches we have applied to plexus-utils and I have one more minor patch that I'll get simo/olamy to apply for commons-exec, and thereafter hopefully release a minor update to commons-exec. When that is done I figured I'd do all the maven clients in one sitting. WDYT ? Kristian - 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 -
[VOTE] Release Maven Surefire version 2.11, take 2
Hi, We solved 22 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=17856 This version supports JUnit 4.8 @Category annotation, using the groups parameter on the plugin (using the 4.7 provider). The other new feature in this release are runOrder=failedfirst and runOrder=balanced, this last parameter tries to optimize the overall run-time for parallel test runs. Users migrating from classic JUnit4 to the 4.7 provider to use categories may want to take note of http://jira.codehaus.org/browse/SUREFIRE-798 Changes to the proposed Surefire API are documented in the API section of the site, which also has a lovely new skin, thanks to Simon! This version is marked as the last java 1.4 compatible version in JIRA, the next version will be java 1.5 for the plugin. Surefire can still *fork* all the way down to jdk 1.3 for JUnit 3.8.1. There are still lots of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+ SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-272/ Staging site (sync pending): http://maven.apache.org/surefire-2.11/ http://maven.apache.org/plugins/maven-failsafe-plugin-2.11/ http://maven.apache.org/plugins/maven-surefire-plugin-2.11/ http://maven.apache.org/plugins/maven-surefire-reports-plugin-2.11/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 And here's my +1 Kristian
Re: [VOTE] release maven-assembly-plugin version 2.2.2
+1 (not binding) - Mail original - De : Benson Margulies bimargul...@gmail.com À : Maven Developers List dev@maven.apache.org Cc : Envoyé le : Mardi 29 Novembre 2011 18h02 Objet : [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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Migration plan to commons-exec
+1 On Wed, Nov 30, 2011 at 2:34 PM, Jason van Zyl ja...@tesla.io wrote: +1 On Nov 30, 2011, at 2:13 AM, Kristian Rosenvold wrote: Some time ago I did a very thorough review of commons-exec as a replacement for executeCommandLine in plexus-utils. commons-exec is a relative of plexus-utils executeCommandLine, as can be seen from the initial project description at https://github.com/apache/commons-exec/blob/trunk/STATUS . I was very pleased with the code (and vastly superiour test coverage!) and I would like to replace its usage in /all/ of maven in one operation. I went through all the patches we have applied to plexus-utils and I have one more minor patch that I'll get simo/olamy to apply for commons-exec, and thereafter hopefully release a minor update to commons-exec. When that is done I figured I'd do all the maven clients in one sitting. WDYT ? Kristian - 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 -
Re: [VOTE] release maven-assembly-plugin version 2.2.2
+1 Kristian 2011/11/30 Julien HENRY henr...@yahoo.fr +1 (not binding) - Mail original - De : Benson Margulies bimargul...@gmail.com À : Maven Developers List dev@maven.apache.org Cc : Envoyé le : Mardi 29 Novembre 2011 18h02 Objet : [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 - 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
+1 2011/11/29 Benson Margulies bimargul...@apache.org: 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 -- 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] release maven-assembly-plugin version 2.2.2
+1 On 11/29/11 12:02 PM, Benson Margulies wrote: 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 -- John Casey Developer, PMC Chair - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] release maven-common-artifact-filters 1.4
+1 On 11/29/11 6:44 AM, Benson Margulies 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 -- John Casey Developer, PMC Chair - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Migration plan to commons-exec
+1 On 11/30/11 5:13 AM, Kristian Rosenvold wrote: Some time ago I did a very thorough review of commons-exec as a replacement for executeCommandLine in plexus-utils. commons-exec is a relative of plexus-utils executeCommandLine, as can be seen from the initial project description at https://github.com/apache/commons-exec/blob/trunk/STATUS . I was very pleased with the code (and vastly superiour test coverage!) and I would like to replace its usage in /all/ of maven in one operation. I went through all the patches we have applied to plexus-utils and I have one more minor patch that I'll get simo/olamy to apply for commons-exec, and thereafter hopefully release a minor update to commons-exec. When that is done I figured I'd do all the maven clients in one sitting. WDYT ? Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- John Casey Developer, PMC Chair - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven SCM 1.6
+1 2011/11/29 Olivier Lamy ol...@apache.org 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] release maven-common-artifact-filters 1.4
+1 Hervé Le Mardi 29 Novembre 2011 06:44:29 Benson Margulies a écrit : Hi, We solved an issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-QX7G-9I AS%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=hidejql Query=component+%3D+maven-common-artifact-filters+AND+project+%3D+MSHARED+AN D+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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] release maven-assembly-plugin version 2.2.2
+1 Hervé Le Mardi 29 Novembre 2011 12:02:48 Benson Margulies a écrit : Hi, We solved N issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126version=13 669 There are still a couple of issues left in JIRA: https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=pro ject+%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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
It's not so easy to be a CORS client in Java
If I believe http://javasourcecode.org/html/open-source/jdk/jdk-6u23/sun/net/www/protocol/http/HttpURLConnection.java.html, and I have reason to do so, HttpUrlConnection silently flushes Origin (and other relevant headers) without actually implementing the protocol. It might be possible to set sun.net.http.allowRestrictedHeaders to get around this, however, that flag is picked up statically, so it would need to be set at JVM launch. I hope that the commons http connection uses a raw socket. So, if anyone wants to play along with CORS from a JAX-RS client, we'd need an option to WebClient to avoid the HttpUrlConnection. Unless of course we already have one. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] release maven-assembly-plugin version 2.2.2
+1 2011/11/29 Benson Margulies bimargul...@gmail.com: 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 -- 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
