AW: [VOTE] Release Maven 2.0.5 (take 2)
+1 Works fine on my projects Marc -Ursprüngliche Nachricht- Von: Jason van Zyl [mailto:[EMAIL PROTECTED] Gesendet: Montag, 12. Februar 2007 05:33 An: Maven Developers List Betreff: [VOTE] Release Maven 2.0.5 (take 2) Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
Works fine for me, +1 fabrizio On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
Hi Brian, Strange, hey?... Which OS are you running Maven on? Because Stephen's got the same error as me on Fedore Core 6... Fabrice. On 2/13/07, Brian E. Fox [EMAIL PROTECTED] wrote: Hi Fabrice, I'm doing exactly what you describe and from what I can see, the latest 2.0.5 is working ok. I did find an issue in one of the early 2.0.5 release candidates, but it was fixed. The method I use is attached to http://jira.codehaus.org/browse/MNG-2749. Thanks, Brian -Original Message- From: Fabrice Bellingard [mailto:[EMAIL PROTECTED] Sent: Monday, February 12, 2007 10:02 AM To: Maven Developers List Subject: Re: [VOTE] Release Maven 2.0.5 (take 2) Hi Jason, The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/h ttp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
Actually, sorry for being misleading, but checkstyle as an extension seems to work just fine for me. However, I did notice that another case where I was using a build extension is broken for me. Again sorry for the confusion. I've created an issue for what I saw: http://jira.codehaus.org/browse/MNG-2821 -Stephen On 2/13/07, Fabrice Bellingard [EMAIL PROTECTED] wrote: Hi Brian, Strange, hey?... Which OS are you running Maven on? Because Stephen's got the same error as me on Fedore Core 6... Fabrice. On 2/13/07, Brian E. Fox [EMAIL PROTECTED] wrote: Hi Fabrice, I'm doing exactly what you describe and from what I can see, the latest 2.0.5 is working ok. I did find an issue in one of the early 2.0.5 release candidates, but it was fixed. The method I use is attached to http://jira.codehaus.org/browse/MNG-2749. Thanks, Brian -Original Message- From: Fabrice Bellingard [mailto:[EMAIL PROTECTED] Sent: Monday, February 12, 2007 10:02 AM To: Maven Developers List Subject: Re: [VOTE] Release Maven 2.0.5 (take 2) Hi Jason, The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/h ttp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Release Maven 2.0.5 (take 2)
Mostly windows, but also some flavors of linux (Fedora 6 and a custom built kernel). -Original Message- From: Fabrice Bellingard [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 13, 2007 4:17 AM To: Maven Developers List Subject: Re: [VOTE] Release Maven 2.0.5 (take 2) Hi Brian, Strange, hey?... Which OS are you running Maven on? Because Stephen's got the same error as me on Fedore Core 6... Fabrice. On 2/13/07, Brian E. Fox [EMAIL PROTECTED] wrote: Hi Fabrice, I'm doing exactly what you describe and from what I can see, the latest 2.0.5 is working ok. I did find an issue in one of the early 2.0.5 release candidates, but it was fixed. The method I use is attached to http://jira.codehaus.org/browse/MNG-2749. Thanks, Brian -Original Message- From: Fabrice Bellingard [mailto:[EMAIL PROTECTED] Sent: Monday, February 12, 2007 10:02 AM To: Maven Developers List Subject: Re: [VOTE] Release Maven 2.0.5 (take 2) Hi Jason, The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/h ttp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/order=DESC +1, my stuff builds. -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
On 13 Feb 07, at 9:41 AM 13 Feb 07, Trygve Laugstøl wrote: Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/ maven/maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1, my stuff builds. Great, looks like we're out of the frying pan at least :-) Jason. -- Trygve - 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: [VOTE] Release Maven 2.0.5 (take 2)
Our trunks build fine: +1 Thanks, Vincent 2007/2/11, Jason van Zyl [EMAIL PROTECTED]: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
+1 \o/ woohoo! On 2/13/07, Vincent Siveton [EMAIL PROTECTED] wrote: Our trunks build fine: +1 Thanks, Vincent 2007/2/11, Jason van Zyl [EMAIL PROTECTED]: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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] -- jesse mcconnell [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Release Maven 2.0.5 (take 2)
+1 works on my most complicated build, no problems. 2007/2/11, Jason van Zyl [EMAIL PROTECTED]: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/mave n/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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] -- jesse mcconnell [EMAIL PROTECTED] - 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: [VOTE] Release Maven 2.0.5 (take 2)
+1 (I get a binding vote, yay) Works on our project which includes an uber-archive of artifacts and an eclipse pde build - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
Works on our builds with pde-maven-plugin, native-maven-plugin, maven-dependency-plugin, and ofcourse java. -D On 2/13/07, Barrie Treloar [EMAIL PROTECTED] wrote: +1 (I get a binding vote, yay) Works on our project which includes an uber-archive of artifacts and an eclipse pde build - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
+1 Works fine on my projects Arnaud On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Release Maven 2.0.5 (take 2)
+1 (non binding). Tested on all corporate production builds. -- Olivier -Message d'origine- De : Jason van Zyl [mailto:[EMAIL PROTECTED] Envoyé : lundi 12 février 2007 05:33 À : Maven Developers List Objet : [VOTE] Release Maven 2.0.5 (take 2) Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Release Maven 2.0.5 (take 2)
Jason van Zyl wrote on Monday, February 12, 2007 7:12 AM: On 11 Feb 07, at 11:59 PM 11 Feb 07, Jason Dillon wrote: Are there release notes on the major changes or significant fixes which we might need to adapt to and/or be able to remove local build hacks? The JIRA road map is kinda hard to scrape the relevant details from. The only thing in the list which may bite you is that the the dependency resolution is more correct, at least in terms of what we documented, in that the nearest version of a dependency will be selected. This will affect if you are not specifying all dependencies which you actually need to compile your project. Technically you should always list the dependencies that your project actually needs to compile, but we currently don't enforce that as Jorg noted. So if you are relying on transitive deps to pick up your compile time requirements you might have some issues. Specifically this: http://jira.codehaus.org/browse/MNG-2794 The rest are bug fixes. There is only the one slight behavioral change that I am aware off. Well, in any case it would be great to integrate the code of http://jira.codehaus.org/browse/MNG-2676 into the dependencies plugin and get a release. It is a great help to analyse and fix such situations (here integrated into our internal info plugin): % = [INFO] [INFO] Building Commons Activation Project [INFO]task-segment: [info:analyse] [INFO] [INFO] Preparing info:analyse [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [info:analyse] [INFO] Used declared dependencies: [INFO]commons-io:commons-io:jar:1.3:compile [INFO]com.company.commons:company-commons-test:jar:2.0.10:test [INFO]proxytoys:proxytoys:jar:0.2.1:compile [INFO]com.company.commons:company-commons-lang:jar:2.0.6:compile [INFO]javax.activation:activation:jar:1.0.2:compile [INFO] Used undeclared dependencies: [INFO]jmock:jmock:jar:1.1.0:test [INFO]junit:junit:jar:3.8.1:test [INFO] Unused declared dependencies: [INFO]None [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 19 seconds [INFO] Finished at: Mon Feb 12 09:21:38 CET 2007 [INFO] Final Memory: 6M/11M [INFO] % = - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
+1 Our builds run fine. Thanks, Stéphane On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/order=DESC +1 Cocoon trunk builds fine, here my non-binding +1 -- Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
Hi Jason, The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/http://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
On 12 Feb 07, at 3:24 AM 12 Feb 07, Jörg Schaible wrote: Jason van Zyl wrote on Monday, February 12, 2007 7:12 AM: On 11 Feb 07, at 11:59 PM 11 Feb 07, Jason Dillon wrote: Are there release notes on the major changes or significant fixes which we might need to adapt to and/or be able to remove local build hacks? The JIRA road map is kinda hard to scrape the relevant details from. The only thing in the list which may bite you is that the the dependency resolution is more correct, at least in terms of what we documented, in that the nearest version of a dependency will be selected. This will affect if you are not specifying all dependencies which you actually need to compile your project. Technically you should always list the dependencies that your project actually needs to compile, but we currently don't enforce that as Jorg noted. So if you are relying on transitive deps to pick up your compile time requirements you might have some issues. Specifically this: http://jira.codehaus.org/browse/MNG-2794 The rest are bug fixes. There is only the one slight behavioral change that I am aware off. Well, in any case it would be great to integrate the code of http:// jira.codehaus.org/browse/MNG-2676 into the dependencies plugin and get a release. It is a great help to analyse and fix such situations (here integrated into our internal info plugin): Here you can now help having access to the sandbox. And I think Mark has access too. The sandbox is going to be the first place that I look for integrating things. Pulling in Dan's work in the remote resources plugin was a snap. He had a working build with tests and notes, it was great. You want something like this integrated, if you put it in the sandbox and ping one of us you're chances of getting it integrate are very likely. Jason. % = [INFO] -- -- [INFO] Building Commons Activation Project [INFO]task-segment: [info:analyse] [INFO] -- -- [INFO] Preparing info:analyse [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [info:analyse] [INFO] Used declared dependencies: [INFO]commons-io:commons-io:jar:1.3:compile [INFO]com.company.commons:company-commons-test:jar:2.0.10:test [INFO]proxytoys:proxytoys:jar:0.2.1:compile [INFO]com.company.commons:company-commons-lang:jar:2.0.6:compile [INFO]javax.activation:activation:jar:1.0.2:compile [INFO] Used undeclared dependencies: [INFO]jmock:jmock:jar:1.1.0:test [INFO]junit:junit:jar:3.8.1:test [INFO] Unused declared dependencies: [INFO]None [INFO] -- -- [INFO] BUILD SUCCESSFUL [INFO] -- -- [INFO] Total time: 19 seconds [INFO] Finished at: Mon Feb 12 09:21:38 CET 2007 [INFO] Final Memory: 6M/11M [INFO] -- -- % = - Jörg - 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: [VOTE] Release Maven 2.0.5 (take 2)
Fabrice, On Monday 12 February 2007 10:02, Fabrice Bellingard wrote: The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) Just FYI: we (CXF team) put our checkstyle rules into a jar bundle and use that. However, we don't put it in the extensions. We put it as a direct dependency for the plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-buildtools/artifactId version. /version /dependency /dependencies .. plugin and that works fine with 2.0.5. Dan I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ht tp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
On 12 Feb 07, at 10:02 AM 12 Feb 07, Fabrice Bellingard wrote: Hi Jason, The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... I checked your project in here: http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/ core-integration-tests/src/test/resources/it0114- extensionThatProvidesResources/ And I just ran it with the 2.0.5 that I built and put in the staging repository: http://rafb.net/p/humZR325.html I'm on OS X with: java version 1.5.0_06 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112) Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing) Are you on Windows? The bane of my existence? Jason. Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/ maven/http://people.apache.org/%7Ejvanzyl/staging-repository/org/ apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
What Dan describes is probably more correct and we should document this because extensions are really something that executes where you really just want something on the classpath of the plugin. But as far as I can tell with the test that I checked in the extension works, but that should really be a deprecated form of use. jason. On 12 Feb 07, at 10:17 AM 12 Feb 07, Daniel Kulp wrote: Fabrice, On Monday 12 February 2007 10:02, Fabrice Bellingard wrote: The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) Just FYI: we (CXF team) put our checkstyle rules into a jar bundle and use that. However, we don't put it in the extensions. We put it as a direct dependency for the plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-buildtools/artifactId version. /version /dependency /dependencies .. plugin and that works fine with 2.0.5. Dan I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/ maven/ht tp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/ maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] - 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: [VOTE] Release Maven 2.0.5 (take 2)
+1 (non-binding) Works for our builds. Thanks! Dan On Sunday 11 February 2007 23:33, Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
+1 from me. On 2/12/07, Daniel Kulp [EMAIL PROTECTED] wrote: +1 (non-binding) Works for our builds. Thanks! Dan On Sunday 11 February 2007 23:33, Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC Error code from mvn.bat is not returned correctly on windows, solution described at continuum site is not working so maven-invoker-plugin cannot be treat as reliable tool. Steps to reproduce: * checkout maven-antrun-plugin * break one pom.xml files inside src/it/test_n directories * run mvn install at project level maven-invoker-plugin will report all tests as 'passed' but 'build.log' file in directory with broken pom will contain errors. Should I add it into JIRA? Regards, Tomek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
+1 (looking forward to it) - Joakim Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
+1 Emmanuel Jason van Zyl a écrit : Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ Excalibur builds fine with this release, no apparent probs spotted. Thanks, Jorg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
On 12 Feb 07, at 4:06 PM 12 Feb 07, Jorg Heymans wrote: Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/ maven/maven-core/2.0.5/ Excalibur builds fine with this release, no apparent probs spotted. Cool, thanks for checking. Jason. Thanks, Jorg - 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: [VOTE] Release Maven 2.0.5 (take 2)
I've actually been telling people on the mailing list to use extensions for jar with checkstyle configuration, rather than plugin-dependencies. The reason was that, in my testing at the time, if you didn't already have that plugin dependency in your local repo, it would not search for it in all your defined repos, it would only look in central, and therefore break for other people. At the time I just assumed using extensions was the right mechanism, but if plugin-dependencies is 'correct' then it should be verified that it works correctly... -Stephen On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: What Dan describes is probably more correct and we should document this because extensions are really something that executes where you really just want something on the classpath of the plugin. But as far as I can tell with the test that I checked in the extension works, but that should really be a deprecated form of use. jason. On 12 Feb 07, at 10:17 AM 12 Feb 07, Daniel Kulp wrote: Fabrice, On Monday 12 February 2007 10:02, Fabrice Bellingard wrote: The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) Just FYI: we (CXF team) put our checkstyle rules into a jar bundle and use that. However, we don't put it in the extensions. We put it as a direct dependency for the plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-buildtools/artifactId version. /version /dependency /dependencies .. plugin and that works fine with 2.0.5. Dan I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/ maven/ht tp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/ maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] - 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
+1 Rahul Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
Aha! Apparently this was fixed in Maven 2.0.5, as I just tested and it failed with 2.0.4, but worked when I tried it right afterward in 2.0.5. Similarly, I have a project that uses the xfire-generator wsgen task, and I had it defined as an extension. This works with 2.0.4, but is broken with 2.0.5. However, changing it to a plugin dependency made it work again. Beyond this issue of extensions vs. plugin dependencies, the rest of my build worked fine with Maven 2.0.5. -Stephen On 2/12/07, Stephen Duncan [EMAIL PROTECTED] wrote: I've actually been telling people on the mailing list to use extensions for jar with checkstyle configuration, rather than plugin-dependencies. The reason was that, in my testing at the time, if you didn't already have that plugin dependency in your local repo, it would not search for it in all your defined repos, it would only look in central, and therefore break for other people. At the time I just assumed using extensions was the right mechanism, but if plugin-dependencies is 'correct' then it should be verified that it works correctly... -Stephen On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: What Dan describes is probably more correct and we should document this because extensions are really something that executes where you really just want something on the classpath of the plugin. But as far as I can tell with the test that I checked in the extension works, but that should really be a deprecated form of use. jason. On 12 Feb 07, at 10:17 AM 12 Feb 07, Daniel Kulp wrote: Fabrice, On Monday 12 February 2007 10:02, Fabrice Bellingard wrote: The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) Just FYI: we (CXF team) put our checkstyle rules into a jar bundle and use that. However, we don't put it in the extensions. We put it as a direct dependency for the plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-buildtools/artifactId version. /version /dependency /dependencies .. plugin and that works fine with 2.0.5. Dan I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/ maven/ht tp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/ maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] - 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] -- Stephen Duncan Jr www.stephenduncanjr.com -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
Thanks for the hint, Dan, this actually works perfectly! I wasn't aware of this way to specify the JAR. It would be worth updating the documentation of the Checkstyle plugin. I will create a JIRA issue for this. FYI, Jason, yes, I've executed the test project on the bane of your existence ;-) - Windows XP with Java 1.5.0_06 - Windows 2k with Java 1.4.2_02 So even if this way of using the build extension is deprecated, I think this remains a bug on Windows. Anyways, everything works fine now. So here is my (non-binding) +1 :-) Fabrice. On 2/12/07, Daniel Kulp [EMAIL PROTECTED] wrote: Just FYI: we (CXF team) put our checkstyle rules into a jar bundle and use that. However, we don't put it in the extensions. We put it as a direct dependency for the plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-buildtools/artifactId version. /version /dependency /dependencies .. plugin and that works fine with 2.0.5. Dan
Re: [VOTE] Release Maven 2.0.5 (take 2)
Actually, using build extensions in ways that worked in Maven 2.0.4 now fail in 2.0.5 for me using Fedora Core 6. - Stephen On 2/12/07, Fabrice Bellingard [EMAIL PROTECTED] wrote: Thanks for the hint, Dan, this actually works perfectly! I wasn't aware of this way to specify the JAR. It would be worth updating the documentation of the Checkstyle plugin. I will create a JIRA issue for this. FYI, Jason, yes, I've executed the test project on the bane of your existence ;-) - Windows XP with Java 1.5.0_06 - Windows 2k with Java 1.4.2_02 So even if this way of using the build extension is deprecated, I think this remains a bug on Windows. Anyways, everything works fine now. So here is my (non-binding) +1 :-) Fabrice. On 2/12/07, Daniel Kulp [EMAIL PROTECTED] wrote: Just FYI: we (CXF team) put our checkstyle rules into a jar bundle and use that. However, we don't put it in the extensions. We put it as a direct dependency for the plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-buildtools/artifactId version. /version /dependency /dependencies .. plugin and that works fine with 2.0.5. Dan -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Release Maven 2.0.5 (take 2)
Well, in any case it would be great to integrate the code of http://jira.codehaus.org/browse/MNG-2676 into the dependencies plugin and get a release. It is a great help to analyse and fix such situations (here integrated into our internal info plugin) The current alpha-2 release is close to ready with just a couple of issues. Anything major like this I'd like to put into alpha-3 so it doesn't hold up the release. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Release Maven 2.0.5 (take 2)
Hi Fabrice, I'm doing exactly what you describe and from what I can see, the latest 2.0.5 is working ok. I did find an issue in one of the early 2.0.5 release candidates, but it was fixed. The method I use is attached to http://jira.codehaus.org/browse/MNG-2749. Thanks, Brian -Original Message- From: Fabrice Bellingard [mailto:[EMAIL PROTECTED] Sent: Monday, February 12, 2007 10:02 AM To: Maven Developers List Subject: Re: [VOTE] Release Maven 2.0.5 (take 2) Hi Jason, The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/h ttp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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]
[VOTE] Release Maven 2.0.5 (take 2)
Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
Are there release notes on the major changes or significant fixes which we might need to adapt to and/or be able to remove local build hacks? The JIRA road map is kinda hard to scrape the relevant details from. --jason On Feb 11, 2007, at 8:33 PM, Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/ maven/maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
Seems to work fine for Geronimo trunk (2.0) and 1.2 builds... +1 --jason On Feb 11, 2007, at 8:33 PM, Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/ maven/maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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: [VOTE] Release Maven 2.0.5 (take 2)
On 11 Feb 07, at 11:59 PM 11 Feb 07, Jason Dillon wrote: Are there release notes on the major changes or significant fixes which we might need to adapt to and/or be able to remove local build hacks? The JIRA road map is kinda hard to scrape the relevant details from. The only thing in the list which may bite you is that the the dependency resolution is more correct, at least in terms of what we documented, in that the nearest version of a dependency will be selected. This will affect if you are not specifying all dependencies which you actually need to compile your project. Technically you should always list the dependencies that your project actually needs to compile, but we currently don't enforce that as Jorg noted. So if you are relying on transitive deps to pick up your compile time requirements you might have some issues. Specifically this: http://jira.codehaus.org/browse/MNG-2794 The rest are bug fixes. There is only the one slight behavioral change that I am aware off. Jason. --jason On Feb 11, 2007, at 8:33 PM, Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/ maven/maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
Thanks for the info... seems to be okay so far, build works with 2.0.4 and 2.0.5, will soon run the TCK on the 2.0.5 build to see if that shows any dependency related failures, but overall it looks good. There are still a few big issues which we are working around in the G builds which I hope to see fixed in more frequent releases ;-) Thanks, --jason On Feb 11, 2007, at 10:11 PM, Jason van Zyl wrote: On 11 Feb 07, at 11:59 PM 11 Feb 07, Jason Dillon wrote: Are there release notes on the major changes or significant fixes which we might need to adapt to and/or be able to remove local build hacks? The JIRA road map is kinda hard to scrape the relevant details from. The only thing in the list which may bite you is that the the dependency resolution is more correct, at least in terms of what we documented, in that the nearest version of a dependency will be selected. This will affect if you are not specifying all dependencies which you actually need to compile your project. Technically you should always list the dependencies that your project actually needs to compile, but we currently don't enforce that as Jorg noted. So if you are relying on transitive deps to pick up your compile time requirements you might have some issues. Specifically this: http://jira.codehaus.org/browse/MNG-2794 The rest are bug fixes. There is only the one slight behavioral change that I am aware off. Jason. --jason On Feb 11, 2007, at 8:33 PM, Jason van Zyl wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/ maven/maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - 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] - 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]
