Re: Maven 1.1 RC1 SNAPSHOT needs testers
Hi, We just pushed a new snapshot here : http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20061029/ Since the last one mentionned below : - we fixed a problem on the encoding of the pom when maven installs a plugin. If you had some special character in the pom (accents, ...), maven wasn't able to read the pom, that it previously generated. - we improved the reporting of errors during the build. Now you should have by default the stack of errors. - this snapshot bundles last released plugins : maven-simian-plugin v 1.6.1, maven-pom-plugin v 1.5.1, maven-jira-plugin v 1.3.1, maven-java-plugin v 1.6.1, maven-genapp-plugin v 2.3.1, maven-clover-plugin v 1.11.1, maven-changes-plugin v. 1.7 - it contains the snapshots of maven-nsis-plugin v 2.1 and maven-pdf-plugin v 2.5.1 - the windows installer was slightly modified to put MAVEN_HOME in the system environment variables if the user has admin rights Cheers Arnaud Arnaud HERITIER wrote: > > Hi everybody, > > We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This version > incorporates 2 important changes and we would like to have your feedback : > >- MAVEN-1755 : We fixed the last main backward incompability with >maven 1.0.x, this new version supports XML entities in the POM. >- MAVEN-1789 : The default repository is now > http://repo1.maven.org/maven/ > > > ( These two issues aren't yet closed because we have to update the > documentation and we are waiting for your feedback ;-) ) > > Be careful, that to use this snapshot version, you'll certainly have to > define the following set of remote repositories to download dependencies. > maven.repo.remote = > http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/ > > These version includes severals plugins [4] updated since the beta 3, > and > particularly the fix for MPARTIFACT-71 to avoid the error about the > rejected > key of the host if you use the scp or the sftp protocols to deploy your > artifacts. > > The more feedbacks we'll have, the more stable will be the RC1 !! > > Thanks for your help... > > Cheers, > > The maven team. > > [1] > http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20061009/ > [2] http://jira.codehaus.org/browse/MAVEN-1755 > [3] http://jira.codehaus.org/browse/MAVEN-1789 > [4] http://jira.codehaus.org/browse/MAVEN-1769 > > -- View this message in context: http://www.nabble.com/Maven-1.1-RC1-SNAPSHOT-needs-testers-tf2413198s177.html#a7071132 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
ok, thant Wendy for your feedback. I'm happy to see that the pdf plugin is always useful ;-) Arnaud On 10/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: On 10/9/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > Hi everybody, > > We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This version > incorporates 2 important changes and we would like to have your feedback : The only thing I still use Maven 1 for is the PDF plugin... m2 has nothing that even comes close. FWIW, 'maven site' works fine in my current project. :) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
On 10/9/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: Hi everybody, We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This version incorporates 2 important changes and we would like to have your feedback : The only thing I still use Maven 1 for is the PDF plugin... m2 has nothing that even comes close. FWIW, 'maven site' works fine in my current project. :) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 1.1 RC1 SNAPSHOT needs testers
> -Original Message- > From: Tomasz Pik [mailto:[EMAIL PROTECTED] > Sent: lundi 16 octobre 2006 15:17 > To: Maven Users List > Subject: Re: Maven 1.1 RC1 SNAPSHOT needs testers > > On 10/16/06, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > Another option is to clean the cache by default upon installation. > One > > simple way of doing it would be to add a marker file named after the > > version. If there's no file with the current version then maven would > clean > > the cache when it runs and create such a marker file. > > This will be very helpful, but should 'clear' only plugins provided > by maven distro so users do not have to reinstall 3-rd party plugins. Thomas, it wouldn't "clear" any plugin at all. Only the cache would be removed and would get rebuilt automatically from the installed plugins. -Vincent ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Demandez à ceux qui savent sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
On 10/16/06, Vincent Massol <[EMAIL PROTECTED]> wrote: Another option is to clean the cache by default upon installation. One simple way of doing it would be to add a marker file named after the version. If there's no file with the current version then maven would clean the cache when it runs and create such a marker file. This will be very helpful, but should 'clear' only plugins provided by maven distro so users do not have to reinstall 3-rd party plugins. Regards, Tomek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 1.1 RC1 SNAPSHOT needs testers
Nice idea Vincent. I'll implement it before the RC1. It will avoid us to have to many errors due to the cache not correctly deleted. Thx. Arnaud vmassol wrote: > > Hi Arnaud, > >> -Original Message- >> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] >> Sent: lundi 16 octobre 2006 09:34 >> To: users@maven.apache.org >> Subject: Re: Maven 1.1 RC1 SNAPSHOT needs testers >> >> >> I hate these errors ! ;-) >> We'll add a note to ask to the users to manually remove the cache >> before the >> upgrade. > > Another option is to clean the cache by default upon installation. One > simple way of doing it would be to add a marker file named after the > version. If there's no file with the current version then maven would > clean > the cache when it runs and create such a marker file. > > -Vincent > > > >> Dion Gillard-2 wrote: >> > >> > Looks like a bad cache/install. I reinstalled, removing the cache and >> > maven directory in the repo and this error went away. >> > >> > On 10/16/06, Dion Gillard <[EMAIL PROTECTED]> wrote: >> >> Doesn't work for me. I get a stacktrace on starting: >> >> >> >> __ __ >> >> | \/ |__ _Apache__ ___ >> >> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ >> >> |_| |_\__,_|\_/\___|_||_| v. 1.1-RC1-SNAPSHOT >> >> >> >> Directory C:\Documents and Settings\Dion Gillard\.maven\cache does >> not >> >> exist. At >> >> tempting to create. >> >> Plugin cache will be regenerated >> >> org.apache.maven.project.Model: method >> >> setModelEncoding(Ljava/lang/String;)V not >> >> found >> >> Exception stack traces : >> >> java.lang.NoSuchMethodError: org.apache.maven.project.Model: method >> >> setModelEnco >> >> ding(Ljava/lang/String;)V not found >> >> at >> >> >> org.apache.maven.project.io.dom4j.MavenDom4jReader.parseModel(MavenDo >> >> m4jReader.java:1263) >> >> at >> >> >> org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea >> >> der.java:2617) >> >> at >> >> >> org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea >> >> der.java:2628) >> >> at org.apache.maven.project.Project.(Project.java:151) >> >> at >> >> org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:194) >> >> at >> org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) >> >> at >> >> >> org.apache.maven.plugin.JellyScriptHousing.getProject(JellyScriptHous >> >> ing.java:109) >> >> at >> >> >> org.apache.maven.plugin.PluginManager.createPluginHousing(PluginManag >> >> er.java:349) >> >> at >> >> >> org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag >> >> er.java:240) >> >> at >> >> >> org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 >> >> 11) >> >> at >> >> >> org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja >> >> va:205) >> >> at >> >> org.apache.maven.MavenSession.initialize(MavenSession.java:172) >> >> at org.apache.maven.cli.App.doMain(App.java:543) >> >> at org.apache.maven.cli.App.main(App.java:1411) >> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >> Method) >> >> at >> >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >> >> java:79) >> >> at >> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >> >> sorImpl.java:41) >> >> at java.lang.reflect.Method.invoke(Method.java:386) >> >> at com.werken.forehead.Forehead.run(Forehead.java:551) >> >> at com.werken.forehead.Forehead.main(Forehead.java:581) >> >> >> >> On 10/10/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: >> >> > Hi everybody, >> >> > >> >> > We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This >> version >> >> > incorporates 2 important changes and we would like to have your >> >> feedback : >> >>
RE: Maven 1.1 RC1 SNAPSHOT needs testers
Hi Arnaud, > -Original Message- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: lundi 16 octobre 2006 09:34 > To: users@maven.apache.org > Subject: Re: Maven 1.1 RC1 SNAPSHOT needs testers > > > I hate these errors ! ;-) > We'll add a note to ask to the users to manually remove the cache > before the > upgrade. Another option is to clean the cache by default upon installation. One simple way of doing it would be to add a marker file named after the version. If there's no file with the current version then maven would clean the cache when it runs and create such a marker file. -Vincent > Dion Gillard-2 wrote: > > > > Looks like a bad cache/install. I reinstalled, removing the cache and > > maven directory in the repo and this error went away. > > > > On 10/16/06, Dion Gillard <[EMAIL PROTECTED]> wrote: > >> Doesn't work for me. I get a stacktrace on starting: > >> > >> __ __ > >> | \/ |__ _Apache__ ___ > >> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > >> |_| |_\__,_|\_/\___|_||_| v. 1.1-RC1-SNAPSHOT > >> > >> Directory C:\Documents and Settings\Dion Gillard\.maven\cache does > not > >> exist. At > >> tempting to create. > >> Plugin cache will be regenerated > >> org.apache.maven.project.Model: method > >> setModelEncoding(Ljava/lang/String;)V not > >> found > >> Exception stack traces : > >> java.lang.NoSuchMethodError: org.apache.maven.project.Model: method > >> setModelEnco > >> ding(Ljava/lang/String;)V not found > >> at > >> > org.apache.maven.project.io.dom4j.MavenDom4jReader.parseModel(MavenDo > >> m4jReader.java:1263) > >> at > >> > org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea > >> der.java:2617) > >> at > >> > org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea > >> der.java:2628) > >> at org.apache.maven.project.Project.(Project.java:151) > >> at > >> org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:194) > >> at > org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) > >> at > >> > org.apache.maven.plugin.JellyScriptHousing.getProject(JellyScriptHous > >> ing.java:109) > >> at > >> > org.apache.maven.plugin.PluginManager.createPluginHousing(PluginManag > >> er.java:349) > >> at > >> > org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag > >> er.java:240) > >> at > >> > org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 > >> 11) > >> at > >> > org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja > >> va:205) > >> at > >> org.apache.maven.MavenSession.initialize(MavenSession.java:172) > >> at org.apache.maven.cli.App.doMain(App.java:543) > >> at org.apache.maven.cli.App.main(App.java:1411) > >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > >> at > >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > >> java:79) > >> at > >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > >> sorImpl.java:41) > >> at java.lang.reflect.Method.invoke(Method.java:386) > >> at com.werken.forehead.Forehead.run(Forehead.java:551) > >> at com.werken.forehead.Forehead.main(Forehead.java:581) > >> > >> On 10/10/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > >> > Hi everybody, > >> > > >> > We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This > version > >> > incorporates 2 important changes and we would like to have your > >> feedback : > >> > > >> >- MAVEN-1755 : We fixed the last main backward incompability > with > >> >maven 1.0.x, this new version supports XML entities in the POM. > >> >- MAVEN-1789 : The default repository is now > >> http://repo1.maven.org/maven/ > >> > > >> > > >> > ( These two issues aren't yet closed because we have to update > the > >> > documentation and we are waiting for your feedback ;-) ) > >> > > >> > Be careful, that to use this snapshot version, you'll certainly > have > >> to >
Re: Maven 1.1 RC1 SNAPSHOT needs testers
I hate these errors ! ;-) We'll add a note to ask to the users to manually remove the cache before the upgrade. Thanks Dion. Arnaud Dion Gillard-2 wrote: > > Looks like a bad cache/install. I reinstalled, removing the cache and > maven directory in the repo and this error went away. > > On 10/16/06, Dion Gillard <[EMAIL PROTECTED]> wrote: >> Doesn't work for me. I get a stacktrace on starting: >> >> __ __ >> | \/ |__ _Apache__ ___ >> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ >> |_| |_\__,_|\_/\___|_||_| v. 1.1-RC1-SNAPSHOT >> >> Directory C:\Documents and Settings\Dion Gillard\.maven\cache does not >> exist. At >> tempting to create. >> Plugin cache will be regenerated >> org.apache.maven.project.Model: method >> setModelEncoding(Ljava/lang/String;)V not >> found >> Exception stack traces : >> java.lang.NoSuchMethodError: org.apache.maven.project.Model: method >> setModelEnco >> ding(Ljava/lang/String;)V not found >> at >> org.apache.maven.project.io.dom4j.MavenDom4jReader.parseModel(MavenDo >> m4jReader.java:1263) >> at >> org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea >> der.java:2617) >> at >> org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea >> der.java:2628) >> at org.apache.maven.project.Project.(Project.java:151) >> at >> org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:194) >> at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) >> at >> org.apache.maven.plugin.JellyScriptHousing.getProject(JellyScriptHous >> ing.java:109) >> at >> org.apache.maven.plugin.PluginManager.createPluginHousing(PluginManag >> er.java:349) >> at >> org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag >> er.java:240) >> at >> org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 >> 11) >> at >> org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja >> va:205) >> at >> org.apache.maven.MavenSession.initialize(MavenSession.java:172) >> at org.apache.maven.cli.App.doMain(App.java:543) >> at org.apache.maven.cli.App.main(App.java:1411) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >> java:79) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >> sorImpl.java:41) >> at java.lang.reflect.Method.invoke(Method.java:386) >> at com.werken.forehead.Forehead.run(Forehead.java:551) >> at com.werken.forehead.Forehead.main(Forehead.java:581) >> >> On 10/10/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: >> > Hi everybody, >> > >> > We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This version >> > incorporates 2 important changes and we would like to have your >> feedback : >> > >> >- MAVEN-1755 : We fixed the last main backward incompability with >> >maven 1.0.x, this new version supports XML entities in the POM. >> >- MAVEN-1789 : The default repository is now >> http://repo1.maven.org/maven/ >> > >> > >> > ( These two issues aren't yet closed because we have to update the >> > documentation and we are waiting for your feedback ;-) ) >> > >> > Be careful, that to use this snapshot version, you'll certainly have >> to >> > define the following set of remote repositories to download >> dependencies. >> > maven.repo.remote = >> > >> http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/ >> > >> > These version includes severals plugins [4] updated since the beta 3, >> and >> > particularly the fix for MPARTIFACT-71 to avoid the error about the >> rejected >> > key of the host if you use the scp or the sftp protocols to deploy your >> > artifacts. >> > >> > The more feedbacks we'll have, the more stable will be the RC1 !! >> > >> > Thanks for your help... >> > >> > Cheers, >> > >> > The maven team. >> > >> > [1] >> > >> http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20061009/ >> > [2] http://jira.codehaus.org/browse/MAVEN-1755 >> > [3] http://jira.codehaus.org/browse/MAVEN-1789 >> > [4] http://jira.codehaus.org/browse/MAVEN-1769 >> > >> > >> >> >> -- >> http://www.multitask.com.au/people/dion/ >> Rule of Acquisition #91: Hear all, trust nothing. >> > > > -- > http://www.multitask.com.au/people/dion/ > Rule of Acquisition #91: Hear all, trust nothing. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Maven-1.1-RC1-SNAPSHOT-needs-testers-tf2413198.html#a6829699 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additi
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Hi Manfred. There's no reason, to add a report for maven-xdoc-plugin. And more precisely there's no report defined in the xdoc plugin ;-) Did you try to remove your cache directory ? C:/Documents and Settings/manfred/.maven/cache Arnaud Manfred Moser-3 wrote: > > Hi! > > I gave this a spin with my build. I changed over to have my reports in > project.xml like this > > > maven-pmd-plugin > maven-junit-report-plugin > maven-javadoc-plugin > maven-license-plugin > maven-changelog-plugin > maven-checkstyle-plugin > maven-file-activity-plugin > maven-jxr-plugin > maven-jdepend-plugin > maven-java-plugin > maven-linkcheck-plugin > maven-developer-activity-plugin > maven-tasklist-plugin > maven-xdoc-plugin > maven-cobertura-plugin > > > For some reason without the xdoc plugin my xdocs located in /xdocs were > not copied. And now with the xdoc plugin i get the following error. > > BUILD FAILED > File.. file:/C:/Documents and > Settings/manfred/.maven/cache/maven-xdoc-plugin-1.10.1-SNAPSHOT/plugin.jelly > Element... attainGoal > Line.. 1153 > Column 48 > No goal [maven-xdoc-plugin:register] > Total time : 4 seconds > Finished at : Friday, October 13, 2006 2:52:24 PM PDT > > I am sure I am missing something trivial.. but what? > > manfred > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Maven-1.1-RC1-SNAPSHOT-needs-testers-tf2413198.html#a6829661 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Looks like a bad cache/install. I reinstalled, removing the cache and maven directory in the repo and this error went away. On 10/16/06, Dion Gillard <[EMAIL PROTECTED]> wrote: Doesn't work for me. I get a stacktrace on starting: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-RC1-SNAPSHOT Directory C:\Documents and Settings\Dion Gillard\.maven\cache does not exist. At tempting to create. Plugin cache will be regenerated org.apache.maven.project.Model: method setModelEncoding(Ljava/lang/String;)V not found Exception stack traces : java.lang.NoSuchMethodError: org.apache.maven.project.Model: method setModelEnco ding(Ljava/lang/String;)V not found at org.apache.maven.project.io.dom4j.MavenDom4jReader.parseModel(MavenDo m4jReader.java:1263) at org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea der.java:2617) at org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea der.java:2628) at org.apache.maven.project.Project.(Project.java:151) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:194) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.plugin.JellyScriptHousing.getProject(JellyScriptHous ing.java:109) at org.apache.maven.plugin.PluginManager.createPluginHousing(PluginManag er.java:349) at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag er.java:240) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 11) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja va:205) at org.apache.maven.MavenSession.initialize(MavenSession.java:172) at org.apache.maven.cli.App.doMain(App.java:543) at org.apache.maven.cli.App.main(App.java:1411) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:41) at java.lang.reflect.Method.invoke(Method.java:386) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) On 10/10/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > Hi everybody, > > We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This version > incorporates 2 important changes and we would like to have your feedback : > >- MAVEN-1755 : We fixed the last main backward incompability with >maven 1.0.x, this new version supports XML entities in the POM. >- MAVEN-1789 : The default repository is now http://repo1.maven.org/maven/ > > > ( These two issues aren't yet closed because we have to update the > documentation and we are waiting for your feedback ;-) ) > > Be careful, that to use this snapshot version, you'll certainly have to > define the following set of remote repositories to download dependencies. > maven.repo.remote = > http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/ > > These version includes severals plugins [4] updated since the beta 3, and > particularly the fix for MPARTIFACT-71 to avoid the error about the rejected > key of the host if you use the scp or the sftp protocols to deploy your > artifacts. > > The more feedbacks we'll have, the more stable will be the RC1 !! > > Thanks for your help... > > Cheers, > > The maven team. > > [1] > http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20061009/ > [2] http://jira.codehaus.org/browse/MAVEN-1755 > [3] http://jira.codehaus.org/browse/MAVEN-1789 > [4] http://jira.codehaus.org/browse/MAVEN-1769 > > -- http://www.multitask.com.au/people/dion/ Rule of Acquisition #91: Hear all, trust nothing. -- http://www.multitask.com.au/people/dion/ Rule of Acquisition #91: Hear all, trust nothing. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Doesn't work for me. I get a stacktrace on starting: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-RC1-SNAPSHOT Directory C:\Documents and Settings\Dion Gillard\.maven\cache does not exist. At tempting to create. Plugin cache will be regenerated org.apache.maven.project.Model: method setModelEncoding(Ljava/lang/String;)V not found Exception stack traces : java.lang.NoSuchMethodError: org.apache.maven.project.Model: method setModelEnco ding(Ljava/lang/String;)V not found at org.apache.maven.project.io.dom4j.MavenDom4jReader.parseModel(MavenDo m4jReader.java:1263) at org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea der.java:2617) at org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea der.java:2628) at org.apache.maven.project.Project.(Project.java:151) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:194) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.plugin.JellyScriptHousing.getProject(JellyScriptHous ing.java:109) at org.apache.maven.plugin.PluginManager.createPluginHousing(PluginManag er.java:349) at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag er.java:240) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 11) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja va:205) at org.apache.maven.MavenSession.initialize(MavenSession.java:172) at org.apache.maven.cli.App.doMain(App.java:543) at org.apache.maven.cli.App.main(App.java:1411) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:41) at java.lang.reflect.Method.invoke(Method.java:386) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) On 10/10/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: Hi everybody, We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This version incorporates 2 important changes and we would like to have your feedback : - MAVEN-1755 : We fixed the last main backward incompability with maven 1.0.x, this new version supports XML entities in the POM. - MAVEN-1789 : The default repository is now http://repo1.maven.org/maven/ ( These two issues aren't yet closed because we have to update the documentation and we are waiting for your feedback ;-) ) Be careful, that to use this snapshot version, you'll certainly have to define the following set of remote repositories to download dependencies. maven.repo.remote = http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/ These version includes severals plugins [4] updated since the beta 3, and particularly the fix for MPARTIFACT-71 to avoid the error about the rejected key of the host if you use the scp or the sftp protocols to deploy your artifacts. The more feedbacks we'll have, the more stable will be the RC1 !! Thanks for your help... Cheers, The maven team. [1] http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20061009/ [2] http://jira.codehaus.org/browse/MAVEN-1755 [3] http://jira.codehaus.org/browse/MAVEN-1789 [4] http://jira.codehaus.org/browse/MAVEN-1769 -- http://www.multitask.com.au/people/dion/ Rule of Acquisition #91: Hear all, trust nothing. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Hi! I gave this a spin with my build. I changed over to have my reports in project.xml like this maven-pmd-plugin maven-junit-report-plugin maven-javadoc-plugin maven-license-plugin maven-changelog-plugin maven-checkstyle-plugin maven-file-activity-plugin maven-jxr-plugin maven-jdepend-plugin maven-java-plugin maven-linkcheck-plugin maven-developer-activity-plugin maven-tasklist-plugin maven-xdoc-plugin maven-cobertura-plugin For some reason without the xdoc plugin my xdocs located in /xdocs were not copied. And now with the xdoc plugin i get the following error. BUILD FAILED File.. file:/C:/Documents and Settings/manfred/.maven/cache/maven-xdoc-plugin-1.10.1-SNAPSHOT/plugin.jelly Element... attainGoal Line.. 1153 Column 48 No goal [maven-xdoc-plugin:register] Total time : 4 seconds Finished at : Friday, October 13, 2006 2:52:24 PM PDT I am sure I am missing something trivial.. but what? manfred - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 1.1 RC1 SNAPSHOT needs testers
Arnaud, I've had no issues with this snapshot so I'd be keen to see a 1.1 final version based on it James -Original Message- From: Dion Gillard [mailto:[EMAIL PROTECTED] Sent: Friday, October 13, 2006 6:04 AM To: Maven Users List Subject: Re: Maven 1.1 RC1 SNAPSHOT needs testers Arnaud, we are also on Maven 1.1 and would love a release. I'm on holidays and unable to do a complete test, but I will do so early next week. Is that ok? On 10/12/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > Thanks James for your feedback. > We'll add a note about plugin dependencies in projects. > > Nobody else is interested by maven 1.1 ? > > Should we continue to try to release a final version 1.1 ? > Everybody moved to maven 2 or your existing maven 1.x satisfy you ? > > Arnaud > > On 10/10/06, Shute, James <[EMAIL PROTECTED]> wrote: > > > > You're quite correct - I had put an explicit dependency on scm-1.5 > > in my project.xml a while back when we were on 1.0.2 and I wanted to > > force people up to the later version of the plugin. Taking that out > > fixes things. > > > > thanks very much > > > > James > > > > -Original Message----- > > From: Lukas Theussl [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, October 10, 2006 11:45 AM > > To: Maven Users List > > Subject: Re: Maven 1.1 RC1 SNAPSHOT needs testers > > > > This seems to be the cause indeed, the scm:status goal was only > > added in version 1.6 of the scm plugin. You don't have a dependency > > on 1.5 by any chance? Try to remove the > > .maven/cache/maven-scm-plugin-1.5/ directory and see what happens.. > > > > -Lukas > > > > > > Shute, James wrote: > > > Arnaud, > > > > > > I've succesfully been using 1.1b2 for a while so thought I'd give > > > this > > > > > a spin. I'm having trouble with the scm:prepare-release goal. > > > I've included the output when running with -X below. > > > > > > I'm no expert but it looks a bit suspicious that the version of > > > maven-scm-plugin mentioned in the 2nd line below is 1.6, but in > > > the BUILD FAILED section is 1.5. > > > > > > Is this a known issue? I'm running on WinXP SP2 with the 1.5.0_05 > > > JDK > > > > > if that helps in any way. I also cleaned out the cache before > > > starting so it's not that causing the problem. > > > > > > thanks > > > > > > James > > > > > > Output from maven -X scm:prepare-release: > > > > > > ... > > > Reinstalling: > > > source = C:\Temp\.maven\cache\maven-scm-plugin-1.6\plugin.jelly > > > project = null > > > script = null > > > Caching Taglib Uri --> scm:transform Caching Taglib Uri --> > > > changes:transform Caching Taglib Uri --> scm Caching Taglib Uri > > > --> scm:transform Caching Taglib Uri --> changes:transform Caching > > > Taglib Uri --> scm popping off > > > [EMAIL PROTECTED] for > > > [EMAIL PROTECTED] in > > > com.lehman.fid:Jdialtone > > > > > > > > > BUILD FAILED > > > File.. > > > file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly > > > Element... scm:status > > > Line.. 192 > > > Column 158 > > > org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/s > > > cm/r > > > ep > > > ository/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apach > > > e/ maven/scm/command/status/StatusScmResult; > > > org.apache.maven.werkz.UnattainableGoalException: Unable to obtain > > > goal [scm:prepare-release] -- > > > file:/C:/Temp/.maven/cache/maven-scm-plugin > > > -1.5/plugin.jelly:192:158: > > > org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/s > > > cm/r > > > ep > > > ository/ScmRepository;Lorg/a > > > pache/maven/scm/ScmFileSet;)Lorg/apache/maven/scm/command/status/S > > > tatu > > > sS > > > cmResult; > > > at org.apache.maven.werkz.Goal.fire(Goal.java:654) > > > at org.apache.maven.werkz.Goal.attain(Goal.java:582) > > > at > > > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.ja > > > va:7 > > > 11 > > > ) > > > at > > > org.apache.maven.MavenSession.attainGoals(MavenSession.java:264) > > > at org.apache.maven.cli.App.doMa
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Yes, Dion it's good. I'm not surprised to not have some real feedbacks before some weeks. Everybody have differents priorities and generally in our projects, the build isn't the first one :-) I was more surprised to have few replies to this email. There were so much users who critised maven 1.1 which didn't allow to use entities like in m1.0, that I though we'll have more happy users with this announce. Thanks for your help Dion, Have a nice holidays ... Arnaud Dion Gillard-2 wrote: > > Arnaud, > > we are also on Maven 1.1 and would love a release. > > I'm on holidays and unable to do a complete test, but I will do so > early next week. Is that ok? > > On 10/12/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: >> Thanks James for your feedback. >> We'll add a note about plugin dependencies in projects. >> >> Nobody else is interested by maven 1.1 ? >> >> Should we continue to try to release a final version 1.1 ? >> Everybody moved to maven 2 or your existing maven 1.x satisfy you ? >> >> Arnaud >> >> On 10/10/06, Shute, James <[EMAIL PROTECTED]> wrote: >> > >> > You're quite correct - I had put an explicit dependency on scm-1.5 in >> my >> > project.xml a while back when we were on 1.0.2 and I wanted to force >> > people up to the later version of the plugin. Taking that out fixes >> > things. >> > >> > thanks very much >> > >> > James >> > >> > -Original Message- >> > From: Lukas Theussl [mailto:[EMAIL PROTECTED] >> > Sent: Tuesday, October 10, 2006 11:45 AM >> > To: Maven Users List >> > Subject: Re: Maven 1.1 RC1 SNAPSHOT needs testers >> > >> > This seems to be the cause indeed, the scm:status goal was only added >> in >> > version 1.6 of the scm plugin. You don't have a dependency on 1.5 by >> any >> > chance? Try to remove the .maven/cache/maven-scm-plugin-1.5/ directory >> > and see what happens.. >> > >> > -Lukas >> > >> > >> > Shute, James wrote: >> > > Arnaud, >> > > >> > > I've succesfully been using 1.1b2 for a while so thought I'd give >> this >> > >> > > a spin. I'm having trouble with the scm:prepare-release goal. I've >> > > included the output when running with -X below. >> > > >> > > I'm no expert but it looks a bit suspicious that the version of >> > > maven-scm-plugin mentioned in the 2nd line below is 1.6, but in the >> > > BUILD FAILED section is 1.5. >> > > >> > > Is this a known issue? I'm running on WinXP SP2 with the 1.5.0_05 >> JDK >> > >> > > if that helps in any way. I also cleaned out the cache before >> > > starting so it's not that causing the problem. >> > > >> > > thanks >> > > >> > > James >> > > >> > > Output from maven -X scm:prepare-release: >> > > >> > > ... >> > > Reinstalling: >> > > source = C:\Temp\.maven\cache\maven-scm-plugin-1.6\plugin.jelly >> > > project = null >> > > script = null >> > > Caching Taglib Uri --> scm:transform >> > > Caching Taglib Uri --> changes:transform Caching Taglib Uri --> scm >> > > Caching Taglib Uri --> scm:transform Caching Taglib Uri --> >> > > changes:transform Caching Taglib Uri --> scm popping off >> > > [EMAIL PROTECTED] for >> > > [EMAIL PROTECTED] in >> > > com.lehman.fid:Jdialtone >> > > >> > > >> > > BUILD FAILED >> > > File.. >> > > file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly >> > > Element... scm:status >> > > Line.. 192 >> > > Column 158 >> > > >> org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/r >> > > ep >> > > ository/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apache/ >> > > maven/scm/command/status/StatusScmResult; >> > > org.apache.maven.werkz.UnattainableGoalException: Unable to obtain >> > > goal [scm:prepare-release] -- >> > > file:/C:/Temp/.maven/cache/maven-scm-plugin >> > > -1.5/plugin.jelly:192:158: >> > > >> org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/r >> > > ep >> > > ository/ScmRepository;Lorg/a >> > &g
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Arnaud, we are also on Maven 1.1 and would love a release. I'm on holidays and unable to do a complete test, but I will do so early next week. Is that ok? On 10/12/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: Thanks James for your feedback. We'll add a note about plugin dependencies in projects. Nobody else is interested by maven 1.1 ? Should we continue to try to release a final version 1.1 ? Everybody moved to maven 2 or your existing maven 1.x satisfy you ? Arnaud On 10/10/06, Shute, James <[EMAIL PROTECTED]> wrote: > > You're quite correct - I had put an explicit dependency on scm-1.5 in my > project.xml a while back when we were on 1.0.2 and I wanted to force > people up to the later version of the plugin. Taking that out fixes > things. > > thanks very much > > James > > -Original Message- > From: Lukas Theussl [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 10, 2006 11:45 AM > To: Maven Users List > Subject: Re: Maven 1.1 RC1 SNAPSHOT needs testers > > This seems to be the cause indeed, the scm:status goal was only added in > version 1.6 of the scm plugin. You don't have a dependency on 1.5 by any > chance? Try to remove the .maven/cache/maven-scm-plugin-1.5/ directory > and see what happens.. > > -Lukas > > > Shute, James wrote: > > Arnaud, > > > > I've succesfully been using 1.1b2 for a while so thought I'd give this > > > a spin. I'm having trouble with the scm:prepare-release goal. I've > > included the output when running with -X below. > > > > I'm no expert but it looks a bit suspicious that the version of > > maven-scm-plugin mentioned in the 2nd line below is 1.6, but in the > > BUILD FAILED section is 1.5. > > > > Is this a known issue? I'm running on WinXP SP2 with the 1.5.0_05 JDK > > > if that helps in any way. I also cleaned out the cache before > > starting so it's not that causing the problem. > > > > thanks > > > > James > > > > Output from maven -X scm:prepare-release: > > > > ... > > Reinstalling: > > source = C:\Temp\.maven\cache\maven-scm-plugin-1.6\plugin.jelly > > project = null > > script = null > > Caching Taglib Uri --> scm:transform > > Caching Taglib Uri --> changes:transform Caching Taglib Uri --> scm > > Caching Taglib Uri --> scm:transform Caching Taglib Uri --> > > changes:transform Caching Taglib Uri --> scm popping off > > [EMAIL PROTECTED] for > > [EMAIL PROTECTED] in > > com.lehman.fid:Jdialtone > > > > > > BUILD FAILED > > File.. > > file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly > > Element... scm:status > > Line.. 192 > > Column 158 > > org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/r > > ep > > ository/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apache/ > > maven/scm/command/status/StatusScmResult; > > org.apache.maven.werkz.UnattainableGoalException: Unable to obtain > > goal [scm:prepare-release] -- > > file:/C:/Temp/.maven/cache/maven-scm-plugin > > -1.5/plugin.jelly:192:158: > > org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/r > > ep > > ository/ScmRepository;Lorg/a > > pache/maven/scm/ScmFileSet;)Lorg/apache/maven/scm/command/status/Statu > > sS > > cmResult; > > at org.apache.maven.werkz.Goal.fire(Goal.java:654) > > at org.apache.maven.werkz.Goal.attain(Goal.java:582) > > at > > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:7 > > 11 > > ) > > at > > org.apache.maven.MavenSession.attainGoals(MavenSession.java:264) > > at org.apache.maven.cli.App.doMain(App.java:556) > > at org.apache.maven.cli.App.main(App.java:1411) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j > > av > > a:39) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess > > or > > Impl.java:25) > > at java.lang.reflect.Method.invoke(Method.java:585) > > at com.werken.forehead.Forehead.run(Forehead.java:551) > > at com.werken.forehead.Forehead.main(Forehead.java:581) > > Caused by: org.apache.commons.jelly.JellyTagException: > > file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly:192:158: > > or > > g.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/rep > > os > > ito
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Thanks Gisbert. Do not hesitate to ask us some help. If there's some backward incompatibilities, we'll try to fix them. Arnaud On 10/12/06, Gisbert Amm <[EMAIL PROTECTED]> wrote: Arnaud HERITIER wrote: > Thanks James for your feedback. > We'll add a note about plugin dependencies in projects. > > Nobody else is interested by maven 1.1 ? > > Should we continue to try to release a final version 1.1 ? > Everybody moved to maven 2 or your existing maven 1.x satisfy you ? We are indeed interested in Maven 1.1 since more than 200 of our existing builds are currently using Maven 1.1 beta 2 and will definitely not be migrated to Maven 2. However, we simply haven't got the time to test Maven 1.1 at the moment since we're fiddling with Maven 2 to probably make it the default for all future builds. I shortly switched the live build system to Maven 1.1 beta 3 when it came out (beginning of last week, IIRC), but got some errors I haven't had the time to further investigate yet (most of them probably incompatibilities with our home grown plugins, I guess). So I switched back to Maven 1.1 beta 2 until I got a bit more time (only touch a running system when you got time to fix it afterwords). I think I can give the RC1 a try next week. -Gisbert Amm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Arnaud HERITIER wrote: Thanks James for your feedback. We'll add a note about plugin dependencies in projects. Nobody else is interested by maven 1.1 ? Should we continue to try to release a final version 1.1 ? Everybody moved to maven 2 or your existing maven 1.x satisfy you ? We are indeed interested in Maven 1.1 since more than 200 of our existing builds are currently using Maven 1.1 beta 2 and will definitely not be migrated to Maven 2. However, we simply haven't got the time to test Maven 1.1 at the moment since we're fiddling with Maven 2 to probably make it the default for all future builds. I shortly switched the live build system to Maven 1.1 beta 3 when it came out (beginning of last week, IIRC), but got some errors I haven't had the time to further investigate yet (most of them probably incompatibilities with our home grown plugins, I guess). So I switched back to Maven 1.1 beta 2 until I got a bit more time (only touch a running system when you got time to fix it afterwords). I think I can give the RC1 a try next week. -Gisbert Amm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Thanks James for your feedback. We'll add a note about plugin dependencies in projects. Nobody else is interested by maven 1.1 ? Should we continue to try to release a final version 1.1 ? Everybody moved to maven 2 or your existing maven 1.x satisfy you ? Arnaud On 10/10/06, Shute, James <[EMAIL PROTECTED]> wrote: You're quite correct - I had put an explicit dependency on scm-1.5 in my project.xml a while back when we were on 1.0.2 and I wanted to force people up to the later version of the plugin. Taking that out fixes things. thanks very much James -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 10, 2006 11:45 AM To: Maven Users List Subject: Re: Maven 1.1 RC1 SNAPSHOT needs testers This seems to be the cause indeed, the scm:status goal was only added in version 1.6 of the scm plugin. You don't have a dependency on 1.5 by any chance? Try to remove the .maven/cache/maven-scm-plugin-1.5/ directory and see what happens.. -Lukas Shute, James wrote: > Arnaud, > > I've succesfully been using 1.1b2 for a while so thought I'd give this > a spin. I'm having trouble with the scm:prepare-release goal. I've > included the output when running with -X below. > > I'm no expert but it looks a bit suspicious that the version of > maven-scm-plugin mentioned in the 2nd line below is 1.6, but in the > BUILD FAILED section is 1.5. > > Is this a known issue? I'm running on WinXP SP2 with the 1.5.0_05 JDK > if that helps in any way. I also cleaned out the cache before > starting so it's not that causing the problem. > > thanks > > James > > Output from maven -X scm:prepare-release: > > ... > Reinstalling: > source = C:\Temp\.maven\cache\maven-scm-plugin-1.6\plugin.jelly > project = null > script = null > Caching Taglib Uri --> scm:transform > Caching Taglib Uri --> changes:transform Caching Taglib Uri --> scm > Caching Taglib Uri --> scm:transform Caching Taglib Uri --> > changes:transform Caching Taglib Uri --> scm popping off > [EMAIL PROTECTED] for > [EMAIL PROTECTED] in > com.lehman.fid:Jdialtone > > > BUILD FAILED > File.. > file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly > Element... scm:status > Line.. 192 > Column 158 > org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/r > ep > ository/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apache/ > maven/scm/command/status/StatusScmResult; > org.apache.maven.werkz.UnattainableGoalException: Unable to obtain > goal [scm:prepare-release] -- > file:/C:/Temp/.maven/cache/maven-scm-plugin > -1.5/plugin.jelly:192:158: > org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/r > ep > ository/ScmRepository;Lorg/a > pache/maven/scm/ScmFileSet;)Lorg/apache/maven/scm/command/status/Statu > sS > cmResult; > at org.apache.maven.werkz.Goal.fire(Goal.java:654) > at org.apache.maven.werkz.Goal.attain(Goal.java:582) > at > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:7 > 11 > ) > at > org.apache.maven.MavenSession.attainGoals(MavenSession.java:264) > at org.apache.maven.cli.App.doMain(App.java:556) > at org.apache.maven.cli.App.main(App.java:1411) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j > av > a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess > or > Impl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.werken.forehead.Forehead.run(Forehead.java:551) > at com.werken.forehead.Forehead.main(Forehead.java:581) > Caused by: org.apache.commons.jelly.JellyTagException: > file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly:192:158: > or > g.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/rep > os > itory/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apache/ma > ven/scm/command/status/StatusScmResult; > at > org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java > :1 > 93) > at > org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java > :1 > 02) > at > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag > .j > ava:82) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.perform > Ac > tion(MavenGoalTag.java:115) > at org.apache.maven.werkz.Goal.fire(Goal.java:647) > ... 11 more > Cause
RE: Maven 1.1 RC1 SNAPSHOT needs testers
You're quite correct - I had put an explicit dependency on scm-1.5 in my project.xml a while back when we were on 1.0.2 and I wanted to force people up to the later version of the plugin. Taking that out fixes things. thanks very much James -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 10, 2006 11:45 AM To: Maven Users List Subject: Re: Maven 1.1 RC1 SNAPSHOT needs testers This seems to be the cause indeed, the scm:status goal was only added in version 1.6 of the scm plugin. You don't have a dependency on 1.5 by any chance? Try to remove the .maven/cache/maven-scm-plugin-1.5/ directory and see what happens.. -Lukas Shute, James wrote: > Arnaud, > > I've succesfully been using 1.1b2 for a while so thought I'd give this > a spin. I'm having trouble with the scm:prepare-release goal. I've > included the output when running with -X below. > > I'm no expert but it looks a bit suspicious that the version of > maven-scm-plugin mentioned in the 2nd line below is 1.6, but in the > BUILD FAILED section is 1.5. > > Is this a known issue? I'm running on WinXP SP2 with the 1.5.0_05 JDK > if that helps in any way. I also cleaned out the cache before > starting so it's not that causing the problem. > > thanks > > James > > Output from maven -X scm:prepare-release: > > ... > Reinstalling: > source = C:\Temp\.maven\cache\maven-scm-plugin-1.6\plugin.jelly > project = null > script = null > Caching Taglib Uri --> scm:transform > Caching Taglib Uri --> changes:transform Caching Taglib Uri --> scm > Caching Taglib Uri --> scm:transform Caching Taglib Uri --> > changes:transform Caching Taglib Uri --> scm popping off > [EMAIL PROTECTED] for > [EMAIL PROTECTED] in > com.lehman.fid:Jdialtone > > > BUILD FAILED > File.. > file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly > Element... scm:status > Line.. 192 > Column 158 > org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/r > ep > ository/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apache/ > maven/scm/command/status/StatusScmResult; > org.apache.maven.werkz.UnattainableGoalException: Unable to obtain > goal [scm:prepare-release] -- > file:/C:/Temp/.maven/cache/maven-scm-plugin > -1.5/plugin.jelly:192:158: > org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/r > ep > ository/ScmRepository;Lorg/a > pache/maven/scm/ScmFileSet;)Lorg/apache/maven/scm/command/status/Statu > sS > cmResult; > at org.apache.maven.werkz.Goal.fire(Goal.java:654) > at org.apache.maven.werkz.Goal.attain(Goal.java:582) > at > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:7 > 11 > ) > at > org.apache.maven.MavenSession.attainGoals(MavenSession.java:264) > at org.apache.maven.cli.App.doMain(App.java:556) > at org.apache.maven.cli.App.main(App.java:1411) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j > av > a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess > or > Impl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.werken.forehead.Forehead.run(Forehead.java:551) > at com.werken.forehead.Forehead.main(Forehead.java:581) > Caused by: org.apache.commons.jelly.JellyTagException: > file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly:192:158: > or > g.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/rep > os > itory/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apache/ma > ven/scm/command/status/StatusScmResult; > at > org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java > :1 > 93) > at > org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java > :1 > 02) > at > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag > .j > ava:82) > at > org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.perform > Ac > tion(MavenGoalTag.java:115) > at org.apache.maven.werkz.Goal.fire(Goal.java:647) > ... 11 more > Caused by: java.lang.NoSuchMethodError: > org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/r > ep > ository/ScmRepository;Lorg/a > pache/maven/scm/ScmFileSet;)Lorg/apache/maven/scm/command/status/Statu > sS > cmResult; > at > org.apache.maven.plugins.sc
Re: Maven 1.1 RC1 SNAPSHOT needs testers
This seems to be the cause indeed, the scm:status goal was only added in version 1.6 of the scm plugin. You don't have a dependency on 1.5 by any chance? Try to remove the .maven/cache/maven-scm-plugin-1.5/ directory and see what happens.. -Lukas Shute, James wrote: Arnaud, I've succesfully been using 1.1b2 for a while so thought I'd give this a spin. I'm having trouble with the scm:prepare-release goal. I've included the output when running with -X below. I'm no expert but it looks a bit suspicious that the version of maven-scm-plugin mentioned in the 2nd line below is 1.6, but in the BUILD FAILED section is 1.5. Is this a known issue? I'm running on WinXP SP2 with the 1.5.0_05 JDK if that helps in any way. I also cleaned out the cache before starting so it's not that causing the problem. thanks James Output from maven -X scm:prepare-release: ... Reinstalling: source = C:\Temp\.maven\cache\maven-scm-plugin-1.6\plugin.jelly project = null script = null Caching Taglib Uri --> scm:transform Caching Taglib Uri --> changes:transform Caching Taglib Uri --> scm Caching Taglib Uri --> scm:transform Caching Taglib Uri --> changes:transform Caching Taglib Uri --> scm popping off [EMAIL PROTECTED] for [EMAIL PROTECTED] in com.lehman.fid:Jdialtone BUILD FAILED File.. file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly Element... scm:status Line.. 192 Column 158 org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/rep ository/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apache/ maven/scm/command/status/StatusScmResult; org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [scm:prepare-release] -- file:/C:/Temp/.maven/cache/maven-scm-plugin -1.5/plugin.jelly:192:158: org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/rep ository/ScmRepository;Lorg/a pache/maven/scm/ScmFileSet;)Lorg/apache/maven/scm/command/status/StatusS cmResult; at org.apache.maven.werkz.Goal.fire(Goal.java:654) at org.apache.maven.werkz.Goal.attain(Goal.java:582) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:711 ) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:264) at org.apache.maven.cli.App.doMain(App.java:556) at org.apache.maven.cli.App.main(App.java:1411) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: org.apache.commons.jelly.JellyTagException: file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly:192:158: or g.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/repos itory/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apache/ma ven/scm/command/status/StatusScmResult; at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:1 93) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:1 02) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.j ava:82) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAc tion(MavenGoalTag.java:115) at org.apache.maven.werkz.Goal.fire(Goal.java:647) ... 11 more Caused by: java.lang.NoSuchMethodError: org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/rep ository/ScmRepository;Lorg/a pache/maven/scm/ScmFileSet;)Lorg/apache/maven/scm/command/status/StatusS cmResult; at org.apache.maven.plugins.scm.ScmStatusBean.status(ScmStatusBean.java:47) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:1 80) ... 16 more Final Memory : 3M/7M -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Monday, October 09, 2006 11:20 PM To: Maven Users List Subject: Maven 1.1 RC1 SNAPSHOT needs testers Hi everybody, We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This version incorporates 2 important changes and we would like to have your feedback : - MAVEN-1755 : We fixed the last main backward incompability with maven 1.0.x, this new version supports XML entities in the POM. - MAVEN-1789 : The default repository is now http://repo1.maven.org/maven/ ( These two issues a
RE: Maven 1.1 RC1 SNAPSHOT needs testers
Arnaud, I've succesfully been using 1.1b2 for a while so thought I'd give this a spin. I'm having trouble with the scm:prepare-release goal. I've included the output when running with -X below. I'm no expert but it looks a bit suspicious that the version of maven-scm-plugin mentioned in the 2nd line below is 1.6, but in the BUILD FAILED section is 1.5. Is this a known issue? I'm running on WinXP SP2 with the 1.5.0_05 JDK if that helps in any way. I also cleaned out the cache before starting so it's not that causing the problem. thanks James Output from maven -X scm:prepare-release: ... Reinstalling: source = C:\Temp\.maven\cache\maven-scm-plugin-1.6\plugin.jelly project = null script = null Caching Taglib Uri --> scm:transform Caching Taglib Uri --> changes:transform Caching Taglib Uri --> scm Caching Taglib Uri --> scm:transform Caching Taglib Uri --> changes:transform Caching Taglib Uri --> scm popping off [EMAIL PROTECTED] for [EMAIL PROTECTED] in com.lehman.fid:Jdialtone BUILD FAILED File.. file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly Element... scm:status Line.. 192 Column 158 org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/rep ository/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apache/ maven/scm/command/status/StatusScmResult; org.apache.maven.werkz.UnattainableGoalException: Unable to obtain goal [scm:prepare-release] -- file:/C:/Temp/.maven/cache/maven-scm-plugin -1.5/plugin.jelly:192:158: org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/rep ository/ScmRepository;Lorg/a pache/maven/scm/ScmFileSet;)Lorg/apache/maven/scm/command/status/StatusS cmResult; at org.apache.maven.werkz.Goal.fire(Goal.java:654) at org.apache.maven.werkz.Goal.attain(Goal.java:582) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:711 ) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:264) at org.apache.maven.cli.App.doMain(App.java:556) at org.apache.maven.cli.App.main(App.java:1411) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: org.apache.commons.jelly.JellyTagException: file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly:192:158: or g.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/repos itory/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;)Lorg/apache/ma ven/scm/command/status/StatusScmResult; at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:1 93) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:1 02) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.j ava:82) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAc tion(MavenGoalTag.java:115) at org.apache.maven.werkz.Goal.fire(Goal.java:647) ... 11 more Caused by: java.lang.NoSuchMethodError: org.apache.maven.scm.manager.ScmManager.status(Lorg/apache/maven/scm/rep ository/ScmRepository;Lorg/a pache/maven/scm/ScmFileSet;)Lorg/apache/maven/scm/command/status/StatusS cmResult; at org.apache.maven.plugins.scm.ScmStatusBean.status(ScmStatusBean.java:47) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:1 80) ... 16 more Final Memory : 3M/7M -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Monday, October 09, 2006 11:20 PM To: Maven Users List Subject: Maven 1.1 RC1 SNAPSHOT needs testers Hi everybody, We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This version incorporates 2 important changes and we would like to have your feedback : - MAVEN-1755 : We fixed the last main backward incompability with maven 1.0.x, this new version supports XML entities in the POM. - MAVEN-1789 : The default repository is now http://repo1.maven.org/maven/ ( These two issues aren't yet closed because we have to update the documentation and we are waiting for your feedback ;-) ) Be careful, that to use this snapshot version, you'll certainly have to define the following set of remote repositories to download dependencies. maven.repo.remote = http
