Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
Benjamin Bentmann wrote: Hi, we're aiming at a bugfix release of Maven 3 in the next week and following tradition we invite interested users in taking the RC for a test drive in order to detect and fix potential regressions since version 3.0.1 before the actual release of 3.0.2. Works well for our build. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
In 6245a072-ee21-4b6a-87cf-1ce84ea4e...@apache.org Brett Porter wrote: http://jira.codehaus.org/browse/SCM-581 It isn't clear from the issue whether this is in the SCM provider (which is independent of Maven releases), or in Maven (in which case this is filed in the wrong place). Right. A few weeks ago I made a weak attempt to look into the source code of the scm module, but I found nothing obvious there that did something wrong with the url. Which component is it that actually parses the pom.xml and extracts the string from the scm/connection element? What is the difference in behaviour between Maven 2.2.1 and Maven 3.0? Is there a relevant MNG issue for that? In maven 2.2.1 you can use a scm url for mercurial that contains a absolute file path reference. In maven 3.x the absolute path is incorrectly converted to a relative path before it is handed over to hg. Mercurial then looks for the project in the wrong place and the release build checkout fails. Mercurial has a special non-standard url annotation of two consecutive slashes after the hostname, to separate relative paths from absolute paths: For example this scm url works in 2.2.1 but fails in 3.x: scm connectionscm:hg:ssh://localhost//opt/foo/connection /scm Above the double slashes after 'localhost' tells hg that the file path is absolute and in the file system located at '/opt/foo'. If the double slash is removed hg will instead search for the directory 'opt/foo' relative to the home directory of the user on the server, perhaps '/home/luser/opt/foo'. -- Fredrik Jonson - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
Brett Porter wrote: http://jira.codehaus.org/browse/SCM-581 It isn't clear from the issue whether this is in the SCM provider (which is independent of Maven releases), or in Maven (in which case this is filed in the wrong place). I think I've actually tracked it down now, to the DefaultUrlNormalizer class in the module maven-model-builder, that indeed is a part of maven-core. The DefaultUrlNormalizer does the following to the element scm/connection: result = result.replaceAll( (?![:/])/+, / ); Which removes any double slash after the hostname part of a url. The normalization occurs when the release plugin doesn't find a ScmSourceUrl in the plugin descriptor. Instead MavenProject.getScm().getConnection() is used to retrieve a scm url. When that method returns the scm connection url is normalized and that all so important double slash is removed. It is also here somewhere I'm lost in the maze of maven-core again, sorry I can't pinpoint the issue better! -- Fredrik Jonson - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
So... about the double slashes issue SCM-581... I've opened a MNG-issue that contains a simplistic patch and a fix for the relevant test case too. The fix might be a bit invasive as it affects all url:s, not only the scm connection url. The alternative is perhaps to have a separate UrlNormalizer specificly for the scm connection. http://jira.codehaus.org/browse/MNG-4966 All other normal tests passes. I suppose the original code that removes the double slashes is there for a reason, avoiding http redirects perhaps? Anyone know? Oh, and the documentation mentions a profile for integration tests (-P run-its), but maven 3.0 tells me there is no such profile. http://maven.apache.org/guides/development/guide-building-m2.htm -- Fredrik Jonson - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
Hello, I understand if this is strictly not a concern or blocker for a release of maven itself, but SCM-581 is still blocking a upgrade from 2.2.1 to 3.x including 3.0.2-RC1 for anyone using mercurial (hg) as SCM and absolute paths on a remote server with the maven release plugin. http://jira.codehaus.org/browse/SCM-581 Any chance to get a fix for that included in 3.0.2? -- Fredrik Jonson - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
Fredrik Jonson wrote: Any chance to get a fix for that included in 3.0.2? Unlikely. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
It isn't clear from the issue whether this is in the SCM provider (which is independent of Maven releases), or in Maven (in which case this is filed in the wrong place). What is the difference in behaviour between Maven 2.2.1 and Maven 3.0? Is there a relevant MNG issue for that? On 08/01/2011, at 1:06 AM, Fredrik Jonson wrote: Hello, I understand if this is strictly not a concern or blocker for a release of maven itself, but SCM-581 is still blocking a upgrade from 2.2.1 to 3.x including 3.0.2-RC1 for anyone using mercurial (hg) as SCM and absolute paths on a remote server with the maven release plugin. http://jira.codehaus.org/browse/SCM-581 Any chance to get a fix for that included in 3.0.2? -- Fredrik Jonson - 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: [PLEASE TEST] Apache Maven 3.0.2-RC1
Works for me building JBoss AS and some other projects. On 01/05/2011 03:20 PM, Benjamin Bentmann wrote: Hi, we're aiming at a bugfix release of Maven 3 in the next week and following tradition we invite interested users in taking the RC for a test drive in order to detect and fix potential regressions since version 3.0.1 before the actual release of 3.0.2. For the duration of the RC testing, sources and binaries are staged at: https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0.2-RC1/ As usual, the changes since the previous release are listed in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16952 Thanks, -The Maven Team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
Hi, I test m3 3.0.2-RC1 and maybe it's regression : [WARNING] The metadata /Users/carpentierxqvier/.m2/repository/com/greenivory/redmole/client/commons/com.greenivory.redmole.client.commons/2.3.0-SNAPSHOT/maven-metadata-local.xml is invalid: Snapshot information corrupted with remote repository data, please verify that no remote repository uses the id 'local' [WARNING] The metadata /Users/carpentierxqvier/.m2/repository/com/greenivory/redmole/client/commons/com.greenivory.redmole.client.commons/2.3.0-SNAPSHOT/maven-metadata-local.xml is invalid: Snapshot information corrupted with remote repository data, please verify that no remote repository uses the id 'local' It's new jar project, generate with artefact quick-start. Maybe not, it is ? -- Carpentier Xavier Ingénieur Développement - x.carpent...@greenivory.com - http://www.greenivory.com GreenIvory Europe 10 rue Saint Wendelin 67500 Haguenau France GreenIvory America Suite 200 3608 Shannon Road Durham NC 27707 USA Tél.+33 9 50 53 10 34 Tel.+1 (617) 862-2319 Fax +1 (919) 493-8837 GSM +33 6 68 81 87 68 Consider the environment. Don’t print this e-mail unless you need to. To avoid excessive data transfer, we’ve removed our logo. On Jan 5, 2011, at 10:20 PM, Benjamin Bentmann wrote: Hi, we're aiming at a bugfix release of Maven 3 in the next week and following tradition we invite interested users in taking the RC for a test drive in order to detect and fix potential regressions since version 3.0.1 before the actual release of 3.0.2. For the duration of the RC testing, sources and binaries are staged at: https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0.2-RC1/ As usual, the changes since the previous release are listed in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16952 Thanks, -The Maven Team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
No problem with my tests. Arnaud On Wed, Jan 5, 2011 at 10:20 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hi, we're aiming at a bugfix release of Maven 3 in the next week and following tradition we invite interested users in taking the RC for a test drive in order to detect and fix potential regressions since version 3.0.1 before the actual release of 3.0.2. For the duration of the RC testing, sources and binaries are staged at: https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0.2-RC1/ As usual, the changes since the previous release are listed in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16952 Thanks, -The Maven Team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
I'm having a problem with the release plugin, BOMs in the reactor, and Maven 3.x. I just uncovered the problem last night, and spent a good part of today trying to narrow it down and verify that it isn't something I'm doing wrong. The issue is http://jira.codehaus.org/browse/MNG-4962 This will definitely have an effect on groups that are building large project structures with BOMs to help coordinate versions. I'm still trying to figure out what might be the best way to fix it, or even to understand how I might go about fixing it at all (still don't completely understand the root cause yet), but I'm happy to help where I can. On 1/5/11 4:20 PM, Benjamin Bentmann wrote: Hi, we're aiming at a bugfix release of Maven 3 in the next week and following tradition we invite interested users in taking the RC for a test drive in order to detect and fix potential regressions since version 3.0.1 before the actual release of 3.0.2. For the duration of the RC testing, sources and binaries are staged at: https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0.2-RC1/ As usual, the changes since the previous release are listed in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16952 Thanks, -The Maven Team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- John Casey Developer, PMC Member - 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: [PLEASE TEST] Apache Maven 3.0.2-RC1
I should mention that this is a problem I have verified is still present in 3.0.2-RC1, but it's also happening in all the 3.x releases. Maven 2.2.1 works fine. On 1/6/11 5:30 PM, John Casey wrote: I'm having a problem with the release plugin, BOMs in the reactor, and Maven 3.x. I just uncovered the problem last night, and spent a good part of today trying to narrow it down and verify that it isn't something I'm doing wrong. The issue is http://jira.codehaus.org/browse/MNG-4962 This will definitely have an effect on groups that are building large project structures with BOMs to help coordinate versions. I'm still trying to figure out what might be the best way to fix it, or even to understand how I might go about fixing it at all (still don't completely understand the root cause yet), but I'm happy to help where I can. On 1/5/11 4:20 PM, Benjamin Bentmann wrote: Hi, we're aiming at a bugfix release of Maven 3 in the next week and following tradition we invite interested users in taking the RC for a test drive in order to detect and fix potential regressions since version 3.0.1 before the actual release of 3.0.2. For the duration of the RC testing, sources and binaries are staged at: https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0.2-RC1/ As usual, the changes since the previous release are listed in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16952 Thanks, -The Maven Team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- John Casey Developer, PMC Member - 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: [PLEASE TEST] Apache Maven 3.0.2-RC1
Hi, Works fine for all Sonar projects, including builds with Tycho. On Fri, Jan 7, 2011 at 01:32, John Casey jdca...@commonjava.org wrote: I should mention that this is a problem I have verified is still present in 3.0.2-RC1, but it's also happening in all the 3.x releases. Maven 2.2.1 works fine. On 1/6/11 5:30 PM, John Casey wrote: I'm having a problem with the release plugin, BOMs in the reactor, and Maven 3.x. I just uncovered the problem last night, and spent a good part of today trying to narrow it down and verify that it isn't something I'm doing wrong. The issue is http://jira.codehaus.org/browse/MNG-4962 This will definitely have an effect on groups that are building large project structures with BOMs to help coordinate versions. I'm still trying to figure out what might be the best way to fix it, or even to understand how I might go about fixing it at all (still don't completely understand the root cause yet), but I'm happy to help where I can. On 1/5/11 4:20 PM, Benjamin Bentmann wrote: Hi, we're aiming at a bugfix release of Maven 3 in the next week and following tradition we invite interested users in taking the RC for a test drive in order to detect and fix potential regressions since version 3.0.1 before the actual release of 3.0.2. For the duration of the RC testing, sources and binaries are staged at: https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0.2-RC1/ As usual, the changes since the previous release are listed in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16952 Thanks, -The Maven Team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- John Casey Developer, PMC Member - 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 -- Best regards, Evgeny Mandrikov aka Godin http://godin.net.ru http://twitter.com/_godin_ http://www.SonarSource.com http://www.sonarsource.com/
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
Hi, may be i have observed a little issue... I have checked the following project https://github.com/khmarbaise/Maven-Licenses-Verifier-Plugin and did an mvn clean package on it. The result was that twice times the line Running TestSuite occured with with MVN 3.0.2-RC1 but not not with Maven 3.0.1. I have observed that behaviour with maven-surefire 2.7.1 (in relationship with Maven 3.0.1) but i use maven-surefire plugin 2.4.3...(see http://jira.codehaus.org/browse/SUREFIRE-680) So the question is: Does this regards the new release or is this related to something different ? Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
Karl Heinz Marbaise wrote: I have observed that behaviour with maven-surefire 2.7.1 (in relationship with Maven 3.0.1) but i use maven-surefire plugin 2.4.3...(see http://jira.codehaus.org/browse/SUREFIRE-680) From your build's log: [INFO] --- maven-surefire-plugin:2.7.1:test (default-test) @ licenses-verifier --- [INFO] Surefire report directory: M:\Maven-Licenses-Verifier-Plugin\licenses-verifier\target\surefire-reports which matches the observation that your POM locks down maven-surefire-report-plugin to 2.4.3 but not maven-surefire-plugin. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
Hi, outch...i've found the problem...as i expected it was my pom which was the problem...not the release... Sorry for that noise... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
Hi Benjamin, which matches the observation that your POM locks down maven-surefire-report-plugin to 2.4.3 but not maven-surefire-plugin. Yes you're right...Mea culpa... Fixed that in my project... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0.2-RC1
Works for me for building and working with - Maven Android Plugin - Maven Android SDK Deplouer - a JasperServer war project - ksaop2-android project - Maven Android Plugin Samples project (4 android project including a scala one) manfred http://www.simpligility.com Hi, we're aiming at a bugfix release of Maven 3 in the next week and following tradition we invite interested users in taking the RC for a test drive in order to detect and fix potential regressions since version 3.0.1 before the actual release of 3.0.2. For the duration of the RC testing, sources and binaries are staged at: https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0.2-RC1/ As usual, the changes since the previous release are listed in JIRA: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16952 Thanks, -The Maven Team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
