Re: Maven 2.0.10-RC3 - Please Test!
Hi John, With RC-3, Javadoc ITs (MJAVADOC-172 and MJAVADOC-194) failed. Sounds like an issue in the invoker-plugin (defined as 1.2 in the pom). Unfortunately, I tried with 1.2.1-snap without success. So it is probably in the core. Could you have a glance? Last step before calling a vote ;) Cheers, Vincent 2008/7/25 John Casey [EMAIL PROTECTED]: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
Is there a chance to get maven-2.0.10 running with maven-scm-1.1? You know, I'd like to see native git support in maven ;) LieGrü, strub --- Vincent Siveton [EMAIL PROTECTED] schrieb am Do, 31.7.2008: Von: Vincent Siveton [EMAIL PROTECTED] Betreff: Re: Maven 2.0.10-RC3 - Please Test! An: Maven Developers List dev@maven.apache.org Datum: Donnerstag, 31. Juli 2008, 14:36 Hi John, With RC-3, Javadoc ITs (MJAVADOC-172 and MJAVADOC-194) failed. Sounds like an issue in the invoker-plugin (defined as 1.2 in the pom). Unfortunately, I tried with 1.2.1-snap without success. So it is probably in the core. Could you have a glance? Last step before calling a vote ;) Cheers, Vincent 2008/7/25 John Casey [EMAIL PROTECTED]: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 2.0.10-RC3 - Please Test!
We're already started the RC process so only blocking issues and regressions are being included. -Original Message- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 10:28 AM To: Maven Developers List Subject: Re: Maven 2.0.10-RC3 - Please Test! Is there a chance to get maven-2.0.10 running with maven-scm-1.1? You know, I'd like to see native git support in maven ;) LieGrü, strub --- Vincent Siveton [EMAIL PROTECTED] schrieb am Do, 31.7.2008: Von: Vincent Siveton [EMAIL PROTECTED] Betreff: Re: Maven 2.0.10-RC3 - Please Test! An: Maven Developers List dev@maven.apache.org Datum: Donnerstag, 31. Juli 2008, 14:36 Hi John, With RC-3, Javadoc ITs (MJAVADOC-172 and MJAVADOC-194) failed. Sounds like an issue in the invoker-plugin (defined as 1.2 in the pom). Unfortunately, I tried with 1.2.1-snap without success. So it is probably in the core. Could you have a glance? Last step before calling a vote ;) Cheers, Vincent 2008/7/25 John Casey [EMAIL PROTECTED]: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
Hi Vincent, I can't even get the javadoc plugin to run on my machine under Maven 2.0.9, not with JDK 1.4 or JDK 1.6...so I'm afraid I'm of little use on these issues. I can give you some time to distill a failing test case that I can pursue, if you like... Let me know. Maybe I'll cut the RC4 and we can test vs. that. -john Vincent Siveton wrote: Hi John, With RC-3, Javadoc ITs (MJAVADOC-172 and MJAVADOC-194) failed. Sounds like an issue in the invoker-plugin (defined as 1.2 in the pom). Unfortunately, I tried with 1.2.1-snap without success. So it is probably in the core. Could you have a glance? Last step before calling a vote ;) Cheers, Vincent 2008/7/25 John Casey [EMAIL PROTECTED]: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
check if the CLASSPATH environment variable is set. it blows up javadoc if it is Sent from my iPod On 31 Jul 2008, at 18:06, John Casey [EMAIL PROTECTED] wrote: Hi Vincent, I can't even get the javadoc plugin to run on my machine under Maven 2.0.9, not with JDK 1.4 or JDK 1.6...so I'm afraid I'm of little use on these issues. I can give you some time to distill a failing test case that I can pursue, if you like... Let me know. Maybe I'll cut the RC4 and we can test vs. that. -john Vincent Siveton wrote: Hi John, With RC-3, Javadoc ITs (MJAVADOC-172 and MJAVADOC-194) failed. Sounds like an issue in the invoker-plugin (defined as 1.2 in the pom). Unfortunately, I tried with 1.2.1-snap without success. So it is probably in the core. Could you have a glance? Last step before calling a vote ;) Cheers, Vincent 2008/7/25 John Casey [EMAIL PROTECTED]: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
The core release doesn't have any dependency on SCM - I think you are looking for native support in the release plugin? Cheers, Brett On 01/08/2008, at 12:27 AM, Mark Struberg wrote: Is there a chance to get maven-2.0.10 running with maven-scm-1.1? You know, I'd like to see native git support in maven ;) LieGrü, strub --- Vincent Siveton [EMAIL PROTECTED] schrieb am Do, 31.7.2008: Von: Vincent Siveton [EMAIL PROTECTED] Betreff: Re: Maven 2.0.10-RC3 - Please Test! An: Maven Developers List dev@maven.apache.org Datum: Donnerstag, 31. Juli 2008, 14:36 Hi John, With RC-3, Javadoc ITs (MJAVADOC-172 and MJAVADOC-194) failed. Sounds like an issue in the invoker-plugin (defined as 1.2 in the pom). Unfortunately, I tried with 1.2.1-snap without success. So it is probably in the core. Could you have a glance? Last step before calling a vote ;) Cheers, Vincent 2008/7/25 John Casey [EMAIL PROTECTED]: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
Would it behoove the Javadoc plugin developers to test for the CLASSPATH variable? Issue a warning instead of blowing up? I know it's not a plugin problem, per se, but it obviously leads some people to believe it is. Paul On Thu, Jul 31, 2008 at 12:43 PM, Stephen Connolly [EMAIL PROTECTED] wrote: check if the CLASSPATH environment variable is set. it blows up javadoc if it is Sent from my iPod On 31 Jul 2008, at 18:06, John Casey [EMAIL PROTECTED] wrote: Hi Vincent, I can't even get the javadoc plugin to run on my machine under Maven 2.0.9, not with JDK 1.4 or JDK 1.6...so I'm afraid I'm of little use on these issues. I can give you some time to distill a failing test case that I can pursue, if you like... Let me know. Maybe I'll cut the RC4 and we can test vs. that. -john
Re: Maven 2.0.10-RC3 - Please Test!
Hi Paul, 2008/7/31 Paul Benedict [EMAIL PROTECTED]: Would it behoove the Javadoc plugin developers to test for the CLASSPATH variable? Issue a warning instead of blowing up? I know it's not a plugin problem, per se, but it obviously leads some people to believe it is. The last entry in the FAQ [1] already explains that: if your CLASSPATH env var has incorrect env variable, the javadoc will crash on windows. It is a known Sun issue (6219854). IMHO it is enough from an user point of view (we have also jira so the user could found it easily). I don't think that Javadoc Plugin needs to display warning for a given Sun issue (even less to make a workaround). Cheers, Vincent [1] https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-javadoc-plugin/src/site/fml/faq.fml Paul On Thu, Jul 31, 2008 at 12:43 PM, Stephen Connolly [EMAIL PROTECTED] wrote: check if the CLASSPATH environment variable is set. it blows up javadoc if it is Sent from my iPod On 31 Jul 2008, at 18:06, John Casey [EMAIL PROTECTED] wrote: Hi Vincent, I can't even get the javadoc plugin to run on my machine under Maven 2.0.9, not with JDK 1.4 or JDK 1.6...so I'm afraid I'm of little use on these issues. I can give you some time to distill a failing test case that I can pursue, if you like... Let me know. Maybe I'll cut the RC4 and we can test vs. that. -john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
Hi John, Maybe your pb was related to CLASSPATH as said by Stephen. FYI I am able to built it with 1.4, 1.5 and 1.6 and mvn 2.0.9 on two stations and Hudson was happy yesterday. Unfortunately, with rc3, it's failing on twice. The twice javadoc ITs seem to not call javadoc goal, and so apidocs output dir don't exist. I will waiting for RC4. Cheers, Vincent 2008/7/31 John Casey [EMAIL PROTECTED]: Hi Vincent, I can't even get the javadoc plugin to run on my machine under Maven 2.0.9, not with JDK 1.4 or JDK 1.6...so I'm afraid I'm of little use on these issues. I can give you some time to distill a failing test case that I can pursue, if you like... Let me know. Maybe I'll cut the RC4 and we can test vs. that. -john Vincent Siveton wrote: Hi John, With RC-3, Javadoc ITs (MJAVADOC-172 and MJAVADOC-194) failed. Sounds like an issue in the invoker-plugin (defined as 1.2 in the pom). Unfortunately, I tried with 1.2.1-snap without success. So it is probably in the core. Could you have a glance? Last step before calling a vote ;) Cheers, Vincent 2008/7/25 John Casey [EMAIL PROTECTED]: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
This is not the case on my machine. I've been very careful NOT to set M2_HOME, JAVA_HOME, or CLASSPATH on my machine. The first two are set using a mvn delegating script in ~/bin that sets the maven version and jdk version before calling the real maven script. I've just verified that CLASSPATH is not set in my bash shell. BTW, I'm running on OS X. -john Stephen Connolly wrote: check if the CLASSPATH environment variable is set. it blows up javadoc if it is Sent from my iPod On 31 Jul 2008, at 18:06, John Casey [EMAIL PROTECTED] wrote: Hi Vincent, I can't even get the javadoc plugin to run on my machine under Maven 2.0.9, not with JDK 1.4 or JDK 1.6...so I'm afraid I'm of little use on these issues. I can give you some time to distill a failing test case that I can pursue, if you like... Let me know. Maybe I'll cut the RC4 and we can test vs. that. -john Vincent Siveton wrote: Hi John, With RC-3, Javadoc ITs (MJAVADOC-172 and MJAVADOC-194) failed. Sounds like an issue in the invoker-plugin (defined as 1.2 in the pom). Unfortunately, I tried with 1.2.1-snap without success. So it is probably in the core. Could you have a glance? Last step before calling a vote ;) Cheers, Vincent 2008/7/25 John Casey [EMAIL PROTECTED]: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
On 30/07/2008, at 12:01 PM, John Casey wrote: I think you're misunderstanding me: I was talking about test coverage within _wagon_ itself. Since wagon is on a separate release cycle to Maven core, Maven releases have to consume released versions of wagon. This means 72h of voting and so forth before releasing a new wagon version. I get that... but with the release having passed it'll be out today anyway. If there were going to be repeated cycles of releases of Wagon needed then that'd be an issue - but so far only one bug was found. My biggest concern here is that proxied connections are one of the most common problems new users have with Maven; I appreciate that they're fixed in the 1.0-beta-4 snapshot up for a vote, but the fact that something this common wasn't tested in wagon itself before it was released worries me. A lot. It's not appropriate for Maven's own ITs to serve as the only test suite for wagon, because that means its much more likely Maven releases will get stuck on this sort of issue, where we're blocked by a wagon release before we can move forward. Again, to me it's all about the fact that Maven's core is a consumer of the wagon libraries, which are released on a separate cycle, for use in (I'm assuming) several projects. The fact that we got three RCs into a release of a Wagon consumer project says something about that consumer project; but IMO the fact that Wagon made it through testing to get a release out with a defect in such a common feature is much more worrisome. I'm saying that, again IMO, we need to spend some serious time on wagon's test suite before we attempt to upgrade the version Maven uses. Well, I went ahead and did this to the best of my abilities. It now tests: - HTTPS - HTTP over proxy - HTTP proxy authentication - HTTP header setting - HTTP Basic authentication - SSH + HTTP proxy - SSH + SOCKS proxy - all wagon methods (code coverage is 80%, only some exceptional conditions are skipped). - internals better, like checksum observer What is not tested: - SSH and FTP group and permission setting (I tried a couple of things, but you just can't do this from Java - we'll need to a programmable test server like we have for Jetty). That said, I spent a lot of time testing SSH permissions on the original changes by hand because it was the issues I was correcting and I'm confident they are right now. This didn't require any non-test code changes, so the results are applicable to beta-4. Is there anything else you need? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
Thanks for the time on all of this. I had made a note locally to take a look at the tests in wagon to see what could be improved once I got 2.0.10 out the door, but you've beaten me to it. I'll hold off on the RC4 I was about to announce, if you're releasing it tomorrow, and we can try pushing it with -beta-4 to see how it works, if you like. It shouldn't be too hard by now to figure out what needs to change in the maven code to support this...IIRC beyond POMs and a couple ITs' ranges, it's just StringWagon. -john Brett Porter wrote: On 30/07/2008, at 12:01 PM, John Casey wrote: I think you're misunderstanding me: I was talking about test coverage within _wagon_ itself. Since wagon is on a separate release cycle to Maven core, Maven releases have to consume released versions of wagon. This means 72h of voting and so forth before releasing a new wagon version. I get that... but with the release having passed it'll be out today anyway. If there were going to be repeated cycles of releases of Wagon needed then that'd be an issue - but so far only one bug was found. My biggest concern here is that proxied connections are one of the most common problems new users have with Maven; I appreciate that they're fixed in the 1.0-beta-4 snapshot up for a vote, but the fact that something this common wasn't tested in wagon itself before it was released worries me. A lot. It's not appropriate for Maven's own ITs to serve as the only test suite for wagon, because that means its much more likely Maven releases will get stuck on this sort of issue, where we're blocked by a wagon release before we can move forward. Again, to me it's all about the fact that Maven's core is a consumer of the wagon libraries, which are released on a separate cycle, for use in (I'm assuming) several projects. The fact that we got three RCs into a release of a Wagon consumer project says something about that consumer project; but IMO the fact that Wagon made it through testing to get a release out with a defect in such a common feature is much more worrisome. I'm saying that, again IMO, we need to spend some serious time on wagon's test suite before we attempt to upgrade the version Maven uses. Well, I went ahead and did this to the best of my abilities. It now tests: - HTTPS - HTTP over proxy - HTTP proxy authentication - HTTP header setting - HTTP Basic authentication - SSH + HTTP proxy - SSH + SOCKS proxy - all wagon methods (code coverage is 80%, only some exceptional conditions are skipped). - internals better, like checksum observer What is not tested: - SSH and FTP group and permission setting (I tried a couple of things, but you just can't do this from Java - we'll need to a programmable test server like we have for Jetty). That said, I spent a lot of time testing SSH permissions on the original changes by hand because it was the issues I was correcting and I'm confident they are right now. This didn't require any non-test code changes, so the results are applicable to beta-4. Is there anything else you need? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
I think you're misunderstanding me: I was talking about test coverage within _wagon_ itself. Since wagon is on a separate release cycle to Maven core, Maven releases have to consume released versions of wagon. This means 72h of voting and so forth before releasing a new wagon version. I understand this is a lot like interpolation changes within maven-project, but there is one important difference: when problems arise with interpolation during RCs, we have a lot of flexibility WRT fixing those issues, since it's in the Maven codebase (or else in a dependency that has more relaxed criteria for a release). My biggest concern here is that proxied connections are one of the most common problems new users have with Maven; I appreciate that they're fixed in the 1.0-beta-4 snapshot up for a vote, but the fact that something this common wasn't tested in wagon itself before it was released worries me. A lot. It's not appropriate for Maven's own ITs to serve as the only test suite for wagon, because that means its much more likely Maven releases will get stuck on this sort of issue, where we're blocked by a wagon release before we can move forward. Again, to me it's all about the fact that Maven's core is a consumer of the wagon libraries, which are released on a separate cycle, for use in (I'm assuming) several projects. The fact that we got three RCs into a release of a Wagon consumer project says something about that consumer project; but IMO the fact that Wagon made it through testing to get a release out with a defect in such a common feature is much more worrisome. I'm saying that, again IMO, we need to spend some serious time on wagon's test suite before we attempt to upgrade the version Maven uses. -john Brett Porter wrote: I understand the concerns, but let me try and explain where I'm coming from. On 29/07/2008, at 1:58 AM, John Casey wrote: What really concerns me is that this release has been in the wild for quite awhile now, and this issue is just coming to light. Plenty of people use proxies, so it's not like it's that shady a corner of the implementation. Do you mean beta-3, or 2.0.10-RC? For beta-3, the problem is that it's just impossible to test it without upgrading core, because it forces the provider-api on you. I guess what I'm getting at is I wonder if the test suite for wagon is good enough to give us confidence in moving forward without a substantial soak period in something like Maven (as could happen if we make the change asap after 2.0.10, to give people a lot of time using it in the run-up to 2.0.11). Unfortunately, I'm not exactly sure how this is going to be any different to 2.0.10. It was already in there for a month and no one noticed this particular issue. I tested HTTP proxying, but I messed something up in my environment - there is now an integration test to verify it instead. I spent a lot more time on testing WebDAV and SSH as that's where the bulk of the changes were. We did go through a reasonable amount of testing a month ago to the point people were happy to approve the wagon release. I think this is quite the same as the interpolation changes - we knew they were risky and were prepared to spend more time testing them, and as issues have cropped up you have fixed them and moved forward beefing up the test suite along the way. The fixes in Wagon have been very insignificant in b3 to b4 if you want to review them all: http://mail-archives.apache.org/mod_mbox/maven-wagon-commits/200806.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/maven-wagon-commits/200807.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/maven-wagon-commits/200807.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/maven-wagon-commits/200807.mbox/[EMAIL PROTECTED] I would prefer to get this in and call on users to test deployment and proxying in their environment specifically. The RCs are the best time to draw light to it. I care as much as everyone else about not having any regressions. Given the extent of the interpolation changes as well as these, this is a good release to run through a longer series of RCs anyway, and we're in no rush - right? Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
I think moving back to -beta-2 will be much less risky. We can try again for -beta-3 in 2.0.11 or when it's ready. -john Brett Porter wrote: Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
On 29/07/2008, at 12:40 AM, John Casey wrote: I think moving back to -beta-2 will be much less risky. We can try again for -beta-3 in 2.0.11 or when it's ready. I'll leave it up to you. I still think it is worth the upgrade, if only to get proper scp group permission setting available finally. beta-3 has been in place for a month, and there's a couple of other things to revert if this is done, so there's risk both ways. The beta-4 JARs are staged and the integration tests for proxying are in place if you want to try it out - it was a one line fix for a missing variable assignment, and aside from that there are just two NPE fixes that had been reported earlier. Cheers, Brett -john Brett Porter wrote: Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
Do we have a list of exactly what would have to be rolled back? Brett Porter wrote: On 29/07/2008, at 12:40 AM, John Casey wrote: I think moving back to -beta-2 will be much less risky. We can try again for -beta-3 in 2.0.11 or when it's ready. I'll leave it up to you. I still think it is worth the upgrade, if only to get proper scp group permission setting available finally. beta-3 has been in place for a month, and there's a couple of other things to revert if this is done, so there's risk both ways. The beta-4 JARs are staged and the integration tests for proxying are in place if you want to try it out - it was a one line fix for a missing variable assignment, and aside from that there are just two NPE fixes that had been reported earlier. Cheers, Brett -john Brett Porter wrote: Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
What really concerns me is that this release has been in the wild for quite awhile now, and this issue is just coming to light. Plenty of people use proxies, so it's not like it's that shady a corner of the implementation. I guess what I'm getting at is I wonder if the test suite for wagon is good enough to give us confidence in moving forward without a substantial soak period in something like Maven (as could happen if we make the change asap after 2.0.10, to give people a lot of time using it in the run-up to 2.0.11). Beta-2 might be inferior in some ways, but it's a known quantity. At this point I'm really concerned about dashing ahead with -beta-4 after -beta-3 had this sort of latent issue. Just my $0.02. -john Brett Porter wrote: On 29/07/2008, at 12:40 AM, John Casey wrote: I think moving back to -beta-2 will be much less risky. We can try again for -beta-3 in 2.0.11 or when it's ready. I'll leave it up to you. I still think it is worth the upgrade, if only to get proper scp group permission setting available finally. beta-3 has been in place for a month, and there's a couple of other things to revert if this is done, so there's risk both ways. The beta-4 JARs are staged and the integration tests for proxying are in place if you want to try it out - it was a one line fix for a missing variable assignment, and aside from that there are just two NPE fixes that had been reported earlier. Cheers, Brett -john Brett Porter wrote: Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
I don't think the speed with with beta-3 and beta-4 were done are in sync with the rigor that's been going into the 2.0.x releases. I think beta-2 should have been cut as 1.0 and then moved one. Applied real bug fixes but we did a bunch of things to the API and sweep changes to implementations and I don't think we can let a library destabilize the 2.0.x releases even if the potential is low. Wagon problems seem to be cropping up and it's just safer to go back. On 28-Jul-08, at 8:58 AM, John Casey wrote: What really concerns me is that this release has been in the wild for quite awhile now, and this issue is just coming to light. Plenty of people use proxies, so it's not like it's that shady a corner of the implementation. I guess what I'm getting at is I wonder if the test suite for wagon is good enough to give us confidence in moving forward without a substantial soak period in something like Maven (as could happen if we make the change asap after 2.0.10, to give people a lot of time using it in the run-up to 2.0.11). Beta-2 might be inferior in some ways, but it's a known quantity. At this point I'm really concerned about dashing ahead with -beta-4 after -beta-3 had this sort of latent issue. Just my $0.02. -john Brett Porter wrote: On 29/07/2008, at 12:40 AM, John Casey wrote: I think moving back to -beta-2 will be much less risky. We can try again for -beta-3 in 2.0.11 or when it's ready. I'll leave it up to you. I still think it is worth the upgrade, if only to get proper scp group permission setting available finally. beta-3 has been in place for a month, and there's a couple of other things to revert if this is done, so there's risk both ways. The beta-4 JARs are staged and the integration tests for proxying are in place if you want to try it out - it was a one line fix for a missing variable assignment, and aside from that there are just two NPE fixes that had been reported earlier. Cheers, Brett -john Brett Porter wrote: Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4- SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/
RE: Maven 2.0.10-RC3 - Please Test!
Same here. I think that before we go ahead and put out beta-4, we should have significant coverage in Maven Its to capture the integration. Since the .10 is on a branch, you can put out a snapshot of beta-4, bump the .11 branch to use it and add some Its that cover everything like proxies etc. I don't think we should move forward with beta-4 until this happens. -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Monday, July 28, 2008 11:59 AM To: Maven Developers List Subject: Re: Maven 2.0.10-RC3 - Please Test! What really concerns me is that this release has been in the wild for quite awhile now, and this issue is just coming to light. Plenty of people use proxies, so it's not like it's that shady a corner of the implementation. I guess what I'm getting at is I wonder if the test suite for wagon is good enough to give us confidence in moving forward without a substantial soak period in something like Maven (as could happen if we make the change asap after 2.0.10, to give people a lot of time using it in the run-up to 2.0.11). Beta-2 might be inferior in some ways, but it's a known quantity. At this point I'm really concerned about dashing ahead with -beta-4 after -beta-3 had this sort of latent issue. Just my $0.02. -john Brett Porter wrote: On 29/07/2008, at 12:40 AM, John Casey wrote: I think moving back to -beta-2 will be much less risky. We can try again for -beta-3 in 2.0.11 or when it's ready. I'll leave it up to you. I still think it is worth the upgrade, if only to get proper scp group permission setting available finally. beta-3 has been in place for a month, and there's a couple of other things to revert if this is done, so there's risk both ways. The beta-4 JARs are staged and the integration tests for proxying are in place if you want to try it out - it was a one line fix for a missing variable assignment, and aside from that there are just two NPE fixes that had been reported earlier. Cheers, Brett -john Brett Porter wrote: Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleNa me=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog
Re: Maven 2.0.10-RC3 - Please Test!
I tested RC3 on several projects with success. Note : I don't use http proxy in this environment cheers Arnaud On Fri, Jul 25, 2008 at 11:20 PM, John Casey [EMAIL PROTECTED] wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Re: Maven 2.0.10-RC3 - Please Test!
On 28-Jul-08, at 9:04 AM, Jason van Zyl wrote: I don't think the speed with with beta-3 and beta-4 were done are in sync with the rigor that's been going into the 2.0.x releases. Sorry, switched timezones and without coffee. Let me say that again: I don't think the speed with which beta-3/4 were done are in sync with the rigor that's been going into the 2.0.x releases. I think beta-2 should have been cut as 1.0 and then moved one. Applied real bug fixes but we did a bunch of things to the API and sweep changes to implementations and I don't think we can let a library destabilize the 2.0.x releases even if the potential is low. Wagon problems seem to be cropping up and it's just safer to go back. On 28-Jul-08, at 8:58 AM, John Casey wrote: What really concerns me is that this release has been in the wild for quite awhile now, and this issue is just coming to light. Plenty of people use proxies, so it's not like it's that shady a corner of the implementation. I guess what I'm getting at is I wonder if the test suite for wagon is good enough to give us confidence in moving forward without a substantial soak period in something like Maven (as could happen if we make the change asap after 2.0.10, to give people a lot of time using it in the run-up to 2.0.11). Beta-2 might be inferior in some ways, but it's a known quantity. At this point I'm really concerned about dashing ahead with -beta-4 after -beta-3 had this sort of latent issue. Just my $0.02. -john Brett Porter wrote: On 29/07/2008, at 12:40 AM, John Casey wrote: I think moving back to -beta-2 will be much less risky. We can try again for -beta-3 in 2.0.11 or when it's ready. I'll leave it up to you. I still think it is worth the upgrade, if only to get proper scp group permission setting available finally. beta-3 has been in place for a month, and there's a couple of other things to revert if this is done, so there's risk both ways. The beta-4 JARs are staged and the integration tests for proxying are in place if you want to try it out - it was a one line fix for a missing variable assignment, and aside from that there are just two NPE fixes that had been reported earlier. Cheers, Brett -john Brett Porter wrote: Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4- SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To
Re: Maven 2.0.10-RC3 - Please Test!
On 28-Jul-08, at 9:09 AM, Arnaud HERITIER wrote: I tested RC3 on several projects with success. Note : I don't use http proxy in this environment Right, changing the functionality of something the vast majority of people don't use logically means that demographic gets nailed. I think some of the additions are nice, it just needs to be tested more before sticking it in 2.0.x. We've been doing so well with the last couple releases in keeping things stable. I don't want to back track now. cheers Arnaud On Fri, Jul 25, 2008 at 11:20 PM, John Casey [EMAIL PROTECTED] wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10- RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
the trick at this point is to figure out what rolling back to -beta-2 will undo in terms of our JIRA count for the release, and where the associated code is. I'll get started on this today. -john Jason van Zyl wrote: On 28-Jul-08, at 9:04 AM, Jason van Zyl wrote: I don't think the speed with with beta-3 and beta-4 were done are in sync with the rigor that's been going into the 2.0.x releases. Sorry, switched timezones and without coffee. Let me say that again: I don't think the speed with which beta-3/4 were done are in sync with the rigor that's been going into the 2.0.x releases. I think beta-2 should have been cut as 1.0 and then moved one. Applied real bug fixes but we did a bunch of things to the API and sweep changes to implementations and I don't think we can let a library destabilize the 2.0.x releases even if the potential is low. Wagon problems seem to be cropping up and it's just safer to go back. On 28-Jul-08, at 8:58 AM, John Casey wrote: What really concerns me is that this release has been in the wild for quite awhile now, and this issue is just coming to light. Plenty of people use proxies, so it's not like it's that shady a corner of the implementation. I guess what I'm getting at is I wonder if the test suite for wagon is good enough to give us confidence in moving forward without a substantial soak period in something like Maven (as could happen if we make the change asap after 2.0.10, to give people a lot of time using it in the run-up to 2.0.11). Beta-2 might be inferior in some ways, but it's a known quantity. At this point I'm really concerned about dashing ahead with -beta-4 after -beta-3 had this sort of latent issue. Just my $0.02. -john Brett Porter wrote: On 29/07/2008, at 12:40 AM, John Casey wrote: I think moving back to -beta-2 will be much less risky. We can try again for -beta-3 in 2.0.11 or when it's ready. I'll leave it up to you. I still think it is worth the upgrade, if only to get proper scp group permission setting available finally. beta-3 has been in place for a month, and there's a couple of other things to revert if this is done, so there's risk both ways. The beta-4 JARs are staged and the integration tests for proxying are in place if you want to try it out - it was a one line fix for a missing variable assignment, and aside from that there are just two NPE fixes that had been reported earlier. Cheers, Brett -john Brett Porter wrote: Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For
Re: Maven 2.0.10-RC3 - Please Test!
On 29/07/2008, at 2:05 AM, Brian E. Fox wrote: Same here. I think that before we go ahead and put out beta-4, we should have significant coverage in Maven Its to capture the integration. I had already added a number of tests over recent times related to this. The touch points with Maven are actually quite few and I would say we have them all covered. Since the .10 is on a branch, you can put out a snapshot of beta-4, bump the .11 branch to use it and add some Its that cover everything like proxies etc. I don't think we should move forward with beta-4 until this happens. Done on 2.0.x and trunk. Independently of the decision about what to include in 2.0.10/2.0.11, I hope you'll test and vote on the wagon release. There's nothing wrong with having frequent releases with small changes such as this one. Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
I understand the concerns, but let me try and explain where I'm coming from. On 29/07/2008, at 1:58 AM, John Casey wrote: What really concerns me is that this release has been in the wild for quite awhile now, and this issue is just coming to light. Plenty of people use proxies, so it's not like it's that shady a corner of the implementation. Do you mean beta-3, or 2.0.10-RC? For beta-3, the problem is that it's just impossible to test it without upgrading core, because it forces the provider-api on you. I guess what I'm getting at is I wonder if the test suite for wagon is good enough to give us confidence in moving forward without a substantial soak period in something like Maven (as could happen if we make the change asap after 2.0.10, to give people a lot of time using it in the run-up to 2.0.11). Unfortunately, I'm not exactly sure how this is going to be any different to 2.0.10. It was already in there for a month and no one noticed this particular issue. I tested HTTP proxying, but I messed something up in my environment - there is now an integration test to verify it instead. I spent a lot more time on testing WebDAV and SSH as that's where the bulk of the changes were. We did go through a reasonable amount of testing a month ago to the point people were happy to approve the wagon release. I think this is quite the same as the interpolation changes - we knew they were risky and were prepared to spend more time testing them, and as issues have cropped up you have fixed them and moved forward beefing up the test suite along the way. The fixes in Wagon have been very insignificant in b3 to b4 if you want to review them all: http://mail-archives.apache.org/mod_mbox/maven-wagon-commits/200806.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/maven-wagon-commits/200807.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/maven-wagon-commits/200807.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/maven-wagon-commits/200807.mbox/[EMAIL PROTECTED] I would prefer to get this in and call on users to test deployment and proxying in their environment specifically. The RCs are the best time to draw light to it. I care as much as everyone else about not having any regressions. Given the extent of the interpolation changes as well as these, this is a good release to run through a longer series of RCs anyway, and we're in no rush - right? Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10- RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix- for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
On 27-Jul-08, at 12:34 PM, Brett Porter wrote: Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) I would prefer to rollback to wagon-beta-2. What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10- RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 2.0.10-RC3 - Please Test!
Rollback. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Sunday, July 27, 2008 2:37 PM To: Maven Developers List Subject: Re: Maven 2.0.10-RC3 - Please Test! On 27-Jul-08, at 12:34 PM, Brett Porter wrote: Hi John, Unfortunately, I've found that HTTP proxies don't work. I added an integration test which passes on 2.0.9. I've already fixed the problem on Wagon trunk and the test passes with 2.0.10-RC4-SNAPSHOT (not committed as it would bump wagon to a snapshot). This leaves the following options: - release Wagon for inclusion as we continue through the RC cycle (I will start the vote process tomorrow regardless) - I can try a workaround either by including the patched AbstractWagon source file or creating a delegating wagon implementation that corrects the proxy setting. - rollback to wagon-beta-2 (would need to mark any related fixes as in 2.0.11, remove the user agent stuff, etc.) I would prefer to rollback to wagon-beta-2. What are your thoughts? Sorry about the inconvenience. Cheers, Brett On 26/07/2008, at 7:20 AM, John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10- RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleNa me=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
This appears to be another permutation of MNG-2739. I've reopened it. -john Olivier Lamy wrote: Hi, In my settings.xml, I have : mirror mirrorOfrec-ap2/mirrorOf urlhttp://xx.xxx.xxx.xxx:10080/maven2/url !--idproxy-recap2/id-- /mirror This causes : bash-3.00$ mvn validate [INFO] [ERROR] FATAL ERROR [INFO] [INFO] id can not be null [INFO] [INFO] Trace java.lang.NullPointerException: id can not be null at org.apache.maven.wagon.repository.Repository.init(Repository.java:81) at org.apache.maven.artifact.repository.DefaultArtifactRepository.init(DefaultArtifac tRepository.java:87) at org.apache.maven.artifact.repository.DefaultArtifactRepository.init(DefaultArtifac tRepository.java:57) at org.apache.maven.artifact.manager.DefaultWagonManager.addMirror(DefaultWagonManager. java:960) at org.apache.maven.DefaultMaven.resolveParameters(DefaultMaven.java:695) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:270) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25 ) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 1 second [INFO] Finished at: Sat Jul 26 00:39:33 CEST 2008 [INFO] Final Memory: 1M/510M [INFO] Anyway adding a id element is not a big pain. -- Olivier 2008/7/25 John Casey [EMAIL PROTECTED]: Sorry, the URL for RC3 is: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC3/org/apache/maven/apache-maven/2.0.10-RC3 -j John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
Sorry, the URL for RC3 is: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC3/org/apache/maven/apache-maven/2.0.10-RC3 -j John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC3 - Please Test!
Hi, In my settings.xml, I have : mirror mirrorOfrec-ap2/mirrorOf urlhttp://xx.xxx.xxx.xxx:10080/maven2/url !--idproxy-recap2/id-- /mirror This causes : bash-3.00$ mvn validate [INFO] [ERROR] FATAL ERROR [INFO] [INFO] id can not be null [INFO] [INFO] Trace java.lang.NullPointerException: id can not be null at org.apache.maven.wagon.repository.Repository.init(Repository.java:81) at org.apache.maven.artifact.repository.DefaultArtifactRepository.init(DefaultArtifac tRepository.java:87) at org.apache.maven.artifact.repository.DefaultArtifactRepository.init(DefaultArtifac tRepository.java:57) at org.apache.maven.artifact.manager.DefaultWagonManager.addMirror(DefaultWagonManager. java:960) at org.apache.maven.DefaultMaven.resolveParameters(DefaultMaven.java:695) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:270) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25 ) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 1 second [INFO] Finished at: Sat Jul 26 00:39:33 CEST 2008 [INFO] Final Memory: 1M/510M [INFO] Anyway adding a id element is not a big pain. -- Olivier 2008/7/25 John Casey [EMAIL PROTECTED]: Sorry, the URL for RC3 is: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC3/org/apache/maven/apache-maven/2.0.10-RC3 -j John Casey wrote: Hi again, We've solved all of the issues brought up in response to the 2.0.10-RC2 release candidate, minus MNG-3678 (which I've postponed to 2.0.11 so we can take a look at whether this is happening by design, and what resolution we want to pursue for it). The issues we've solved for this release candidate are: - MNG-3679 - MNG-3680 - MNG-3684 ...in addition, Brett took care of the verbose output related to artifact resolution that were popping up. Again, for a full list of issues resolved so far for the 2.0.10 release, see: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14112 Please give this release candidate a whirl, and let me know if you have any problems. I'm trying to collect all issues in JIRA with fix-for of 2.0.10, so if you want to file a JIRA ticket for your issue and include a failing test case, that will make my job that much quicker. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
