Re: [VOTE] Release Maven 2.0.7
+1 our builds run fine. Thanks, Stéphane On 6/13/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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.7
On 6/13/07, Stephane Nicoll [EMAIL PROTECTED] wrote: +1 our builds run fine. +1 same here J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7
+1 Emmanuel Jason van Zyl a écrit : Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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.7
Hi tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells me following in one case: RUN ABORTED java.lang.LinkageError org.apache.maven.surefire.Runner An exception or error caused a run to abort. Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints running with -e gives me: org.apache.maven.lifecycle.LifecycleExecutionException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: There are test failures. at org.apache.maven.test.SurefirePlugin.execute (SurefirePlugin.java:389) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:539) ... 16 more I have seen this error before on 2.0.6 which refrained me from using it. 2.0.5 works fine though. Any idea? Do ot let me hold up the release, I am sure it is a config error on my side, but if you have a hint, let me know. Regards Mark Donszelmann On Jun 12, 2007, at 10:12 PM, Jason van Zyl wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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]
What class performs mojo parameter injection?
I'm looking to create a custom converted that saves a plexus configuration instance for delayed object configuration. I'm wondering what the class is that provides the default mojo instance parameter expression handling and injection? Please :-) --jason - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What class performs mojo parameter injection?
Jason Dillon wrote: I'm looking to create a custom converted that saves a plexus configuration instance for delayed object configuration. I'm wondering what the class is that provides the default mojo instance parameter expression handling and injection? org.apache.maven.plugin.PluginParameterExpressionEvaluator org.apache.maven.plugin.DefaultPluginManager Max. signature.asc Description: OpenPGP digital signature
Re: [VOTE] Release Maven 2.0.7
+1 Runs fine on a multiple-parent, 40-module project. Cheers Jo On 6/13/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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.7
+1 (Non-binding) I used it today in various projects and found no problems, apart from that which are already known and related to other stuff. -- Besides, manipulating elections is under penalty of law, resulting in a preventative effect against manipulating elections. The german government justifying the use of electronic voting machines and obviously believing that we don't need a police, because all illegal actions are forbidden. http://dip.bundestag.de/btd/16/051/1605194.pdf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Artifact filtering in DefaultArtifactCollector
Mark Hobson wrote: Hi Brett, On 06/06/07, Mark Hobson [EMAIL PROTECTED] wrote: On 06/06/07, Brett Porter [EMAIL PROTECTED] wrote: My recollection would be that some artifacts are filtered out but their transitive dependencies still needed to be taken into consideration for version calculations, so this could be the reason for this. If an artifact is filtered out then why would it's transitive dependencies impact upon the resolved artifacts? The filtering performed by DefaultArtifactCollector.filterTrail appears to snip the branch at any filtered artifact. Any insight into this? I feel the artifacts should be filtered during DefaultArtifactCollector.recurse. AFAIK filtering is only used to filter out core artifacts (so that plugins don't get ClassCastexceptions etc), but I'm not entirely sure. If that's the case, then indeed I don't see the need to apply filtering after the resolution, unless there are plugins that transitively depend on artifacts through core artifacts that aren't shaded. If filtering is used for other purposes than to filter core artifacts then maybe transitive resolution needs to take place before filtering. I can think of one such example, being the excludes tag (or exclusions; I always mix them up) in dependencies. If they mean don't include this artifact anywhere in the transitive dependency trails, then filtering needs to take place after resolution. If they mean don't include this artifact AND it's dependencies anywhere in the transitive dependency trails, then filtering can occur before resolution. btw, which one is it? I need to doc that in the wiki [1]. Cheers, Kenney [1] http://docs.codehaus.org/display/MAVEN/Maven+2.1+Artifact+Resolution+Specification Cheers, Mark - 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.7 - surefire problem
Hi, can you find the surefire plugin version you're using? I've fixed this problem in the latest snapshots. Only the snapshots were faulty, latest release should be fine. If that one is broken too, can you try one of the latest snapshots (2.4-snapshot or 2.3.1-snapshot), so we can determine wheter it's a fault in surefire or in maven 2.0.7? Thanks, Kenney Mark Donszelmann wrote: Hi tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells me following in one case: RUN ABORTED java.lang.LinkageError org.apache.maven.surefire.Runner An exception or error caused a run to abort. Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints running with -e gives me: org.apache.maven.lifecycle.LifecycleExecutionException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: There are test failures. at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:389) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more I have seen this error before on 2.0.6 which refrained me from using it. 2.0.5 works fine though. Any idea? Do ot let me hold up the release, I am sure it is a config error on my side, but if you have a hint, let me know. Regards Mark Donszelmann On Jun 12, 2007, at 10:12 PM, Jason van Zyl wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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]
maven-dependency-tree changes for 1.1
Hi there, I've been working on dependency tree diagnostic tools and as a consequence have made substantial changes to maven-dependency-tree. A brief synopsis of changes are: - support for node states: included, omitted for conflict, etc. - node filter API and various implementations for pruning the tree - node visitor API and various implementations for processing the tree (esp. serializing visitor for pretty printing the tree, complete with ascii art :) There's a few API changes for the better, but I assume that's okay. So the question is: can this be submitted as a big patch, or must I painstakingly reverse engineer each change into a set of accumulative patches.. (hint: big patch) Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7
Jason van Zyl wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ +1, works for me. -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7
+1 (non-binding) The following worked without incident: * 30+ project multi-level (4 levels) reactor build which uses some custom plugins * 3 project reactor build consisting of plugins and a parent * Environment: MacBook Pro running OS X 10.4.9 under the MacOS Runtime for Java 5 Christian. On Jun 13, 2007, at 1:12 AM, Jason van Zyl wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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] christian gruber + [EMAIL PROTECTED] + mob 410.900.0796 + mob2 416.998.6023 process coach and architect + ISRÁFÍL CONSULTING SERVICES - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7
+1 - my builds are working fine with it. Dan On Wednesday 13 June 2007 01:12, Jason van Zyl wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7
(non-binding) +1 On 6/13/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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.7 - surefire problem
Hi Kenney, I was using 2.1.3 for surefire. Changed it to 2.3, and still get error (slightly different): java.lang.NullPointerException at org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter( SurefirePlugin.java:594) at org.apache.maven.plugin.surefire.SurefirePlugin.execute (SurefirePlugin.java:391) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) My pom (fragment): plugin artifactIdmaven-surefire-plugin/artifactId version2.3/version configuration forkModepertest/forkMode includes include**/*TestSuite.java/include /includes excludes exclude**/TestSuite.java/exclude /excludes /configuration /plugin Could not test SNAPSHOTs yet. Regards Mark Donszelmann On Jun 13, 2007, at 6:18 AM, Kenney Westerhof wrote: Hi, can you find the surefire plugin version you're using? I've fixed this problem in the latest snapshots. Only the snapshots were faulty, latest release should be fine. If that one is broken too, can you try one of the latest snapshots (2.4-snapshot or 2.3.1-snapshot), so we can determine wheter it's a fault in surefire or in maven 2.0.7? Thanks, Kenney Mark Donszelmann wrote: Hi tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells me following in one case: RUN ABORTED java.lang.LinkageError org.apache.maven.surefire.Runner An exception or error caused a run to abort. Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints running with -e gives me: org.apache.maven.lifecycle.LifecycleExecutionException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java: 255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: There are test failures. at
Re: [VOTE] Release Maven 2.0.7
Tested it on 3 more projects. All with multiple hierarchy levels and lots of modules. They all build fine, no issues to report. However, sometimes SNAPSHOT dependencies are included with the timestamp suffix, instead of 2.2-SNAPSHOT.. But this was the same as in previous maven releases.. Environment: Maven version: 2.0.7 Java version: 1.4.2_14 OS name: linux version: 2.6.20-16-generic arch: i386 Cheers Jo On 6/13/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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.7
(non-binding) -1 I just tried to prepare a release in a multi-module project. Usually, the release:prepare failed (because Maven does not find released dependent artifact). An easy fix was to run mvn install and then mvn release:prepare again. The problem I have with maven-2.0.7 is release preparation was not stopped (build is successful). The exception was ignored, and the release is not safe (what happend when it is a serious error?) Here is the log : [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: [INFO] Checking dependencies and plugins for snapshots ... What is the release version for XXX? (X) 3.0.11: : What is the release version for ? () 3.0.11: : ... What is SCM release tag or label for X? (X) xx-3.0.11: : What is the new development version for XXX? (X) 3.0.12-SNAPSHOT: : What is the new development version for ? (YY) 3.0.12-SNAPSHOT: : ... [INFO] Transforming 'XXX'... [INFO] Transforming 'YYY'... ... [INFO] Executing preparation goals 'clean integration-test'... [INFO] Executing: mvn clean integration-test --no-plugin-updates [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] X [INFO] Y [INFO] ... [INFO] [INFO] Building [INFO]task-segment: [clean, integration-test] [INFO] [INFO] [clean:clean] [INFO] [INFO] Building YYY [INFO]task-segment: [clean, integration-test] [INFO] [INFO] [clean:clean] ... [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] No sources to compile [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [war:war] [INFO] Exploding webapp... [INFO] Assembling webapp YYY in D:\Projets\xxx\target\YY-3.0.11 [INFO] Copy webapp webResources to D:\Projets\xx\target\YY-3.0.11 [INFO] [ERROR] FATAL ERROR [INFO] [INFO] basedir C:\Documents and Settings\jhenry\.m2\repository\xxx\YY\3.0.11 does not exist [INFO] [INFO] Trace java.lang.IllegalStateException: basedir C:\Documents and Settings\jhenry\.m2\repository\x\Y\3.0.11 does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:542) at org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles(AbstractWarMojo.java:824) at org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:408) at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:518) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:347) at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:164) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
Re: [VOTE] Release Maven 2.0.7
Is this not a release plugin problem? If this error halted your build, was this with an older version of the release plugin? On 13 Jun 07, at 8:01 AM 13 Jun 07, Julien HENRY wrote: (non-binding) -1 I just tried to prepare a release in a multi-module project. Usually, the release:prepare failed (because Maven does not find released dependent artifact). An easy fix was to run mvn install and then mvn release:prepare again. The problem I have with maven-2.0.7 is release preparation was not stopped (build is successful). The exception was ignored, and the release is not safe (what happend when it is a serious error?) Here is the log : [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: [INFO] Checking dependencies and plugins for snapshots ... What is the release version for XXX? (X) 3.0.11: : What is the release version for ? () 3.0.11: : ... What is SCM release tag or label for X? (X) xx-3.0.11: : What is the new development version for XXX? (X) 3.0.12-SNAPSHOT: : What is the new development version for ? (YY) 3.0.12-SNAPSHOT: : ... [INFO] Transforming 'XXX'... [INFO] Transforming 'YYY'... ... [INFO] Executing preparation goals 'clean integration-test'... [INFO] Executing: mvn clean integration-test --no-plugin-updates [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] X [INFO] Y [INFO] ... [INFO] -- -- [INFO] Building [INFO]task-segment: [clean, integration-test] [INFO] -- -- [INFO] [clean:clean] [INFO] -- -- [INFO] Building YYY [INFO]task-segment: [clean, integration-test] [INFO] -- -- [INFO] [clean:clean] ... [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] No sources to compile [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [war:war] [INFO] Exploding webapp... [INFO] Assembling webapp YYY in D:\Projets\xxx\target\YY-3.0.11 [INFO] Copy webapp webResources to D:\Projets\xx\target \YY-3.0.11 [INFO] -- -- [ERROR] FATAL ERROR [INFO] -- -- [INFO] basedir C:\Documents and Settings\jhenry\.m2\repository\xxx \YY\3.0.11 does not exist [INFO] -- -- [INFO] Trace java.lang.IllegalStateException: basedir C:\Documents and Settings\jhenry\.m2\repository\x\Y \3.0.11 does not exist at org.codehaus.plexus.util.DirectoryScanner.scan (DirectoryScanner.java:542) at org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles (AbstractWarMojo.java:824) at org.apache.maven.plugin.war.AbstractWarMojo.copyResources (AbstractWarMojo.java:408) at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp (AbstractWarMojo.java:518) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp (AbstractWarMojo.java:347) at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:164) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif ecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand leFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at
Re: [VOTE] Release Maven 2.0.7
If you can try this with the latest snapshot of surefire that would be greatly appreciated. I know what the problem is inside Maven, but if Surefire is loading the same problem classes in a different way then we are going to have a problem. So if you can do a quick check using the snapshot of surefire then we can work from there to make them work together. Kenney can help you track it down and we'll fix the problem. If necessary we'll try to accelerate the release of Surefire and get that out before we push 2.0.7 into the wild. On 13 Jun 07, at 1:08 AM 13 Jun 07, Mark Donszelmann wrote: Hi tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells me following in one case: RUN ABORTED java.lang.LinkageError org.apache.maven.surefire.Runner An exception or error caused a run to abort. Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints running with -e gives me: org.apache.maven.lifecycle.LifecycleExecutionException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif ecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand leFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: There are test failures. at org.apache.maven.test.SurefirePlugin.execute (SurefirePlugin.java:389) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:539) ... 16 more I have seen this error before on 2.0.6 which refrained me from using it. 2.0.5 works fine though. Any idea? Do ot let me hold up the release, I am sure it is a config error on my side, but if you have a hint, let me know. Regards Mark Donszelmann On Jun 12, 2007, at 10:12 PM, Jason van Zyl wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7 - surefire problem
Mark Donszelmann wrote: Hi Kenney, Hi Mark, I was using 2.1.3 for surefire. Changed it to 2.3, and still get error (slightly different): Hi, this is fixed later on; i think you're missing a dependency on junit. Let me know if this is the case. Can't be due to 2.0.7 though, unless this works in 2.0.6? If there's no released version (2.3) that works for 2.0.7 then we need to release 2.3.1 asap. -- Kenney java.lang.NullPointerException at org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter(SurefirePlugin.java:594) at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:391) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) My pom (fragment): plugin artifactIdmaven-surefire-plugin/artifactId version2.3/version configuration forkModepertest/forkMode includes include**/*TestSuite.java/include /includes excludes exclude**/TestSuite.java/exclude /excludes /configuration /plugin Could not test SNAPSHOTs yet. Regards Mark Donszelmann On Jun 13, 2007, at 6:18 AM, Kenney Westerhof wrote: Hi, can you find the surefire plugin version you're using? I've fixed this problem in the latest snapshots. Only the snapshots were faulty, latest release should be fine. If that one is broken too, can you try one of the latest snapshots (2.4-snapshot or 2.3.1-snapshot), so we can determine wheter it's a fault in surefire or in maven 2.0.7? Thanks, Kenney Mark Donszelmann wrote: Hi tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells me following in one case: RUN ABORTED java.lang.LinkageError org.apache.maven.surefire.Runner An exception or error caused a run to abort. Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints running with -e gives me: org.apache.maven.lifecycle.LifecycleExecutionException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at
Re: [VOTE] Release Maven 2.0.7
+1 works here. -john On Jun 13, 2007, at 1:12 AM, Jason van Zyl wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john
RE: [VOTE] Release Maven 2.0.7
(non-binding) +1 (works fine on corporate builds). -- Olivier -Message d'origine- De : Jason van Zyl [mailto:[EMAIL PROTECTED] Envoyé : mercredi 13 juin 2007 07:13 À : Maven Developers List Objet : [VOTE] Release Maven 2.0.7 Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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] 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.7 - surefire problem
Hi Kenney, On Jun 13, 2007, at 8:12 AM, Kenney Westerhof wrote: Mark Donszelmann wrote: Hi Kenney, Hi Mark, I was using 2.1.3 for surefire. Changed it to 2.3, and still get error (slightly different): Hi, this is fixed later on; i think you're missing a dependency on junit. I had it in dependencyManagement. It did work with 2.1.3 (Surefire) and mvn 2.0.5. Moved it to dependencies, now works with surefire 2.3 and 2.0.7. VOTE +1 (non-binding). Regards Mark Let me know if this is the case. Can't be due to 2.0.7 though, unless this works in 2.0.6? If there's no released version (2.3) that works for 2.0.7 then we need to release 2.3.1 asap. -- Kenney java.lang.NullPointerException at org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBoot er(SurefirePlugin.java:594) at org.apache.maven.plugin.surefire.SurefirePlugin.execute (SurefirePlugin.java:391) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java: 255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) My pom (fragment): plugin artifactIdmaven-surefire-plugin/artifactId version2.3/version configuration forkModepertest/forkMode includes include**/*TestSuite.java/include /includes excludes exclude**/TestSuite.java/exclude /excludes /configuration /plugin Could not test SNAPSHOTs yet. Regards Mark Donszelmann On Jun 13, 2007, at 6:18 AM, Kenney Westerhof wrote: Hi, can you find the surefire plugin version you're using? I've fixed this problem in the latest snapshots. Only the snapshots were faulty, latest release should be fine. If that one is broken too, can you try one of the latest snapshots (2.4-snapshot or 2.3.1-snapshot), so we can determine wheter it's a fault in surefire or in maven 2.0.7? Thanks, Kenney Mark Donszelmann wrote: Hi tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells me following in one case: RUN ABORTED java.lang.LinkageError org.apache.maven.surefire.Runner An exception or error caused a run to abort. Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints running with -e gives me: org.apache.maven.lifecycle.LifecycleExecutionException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWith Lifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndH andleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegm ents(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at
Re: [VOTE] Release Maven 2.0.7
+1 working for me so far On 6/13/07, LAMY Olivier [EMAIL PROTECTED] wrote: (non-binding) +1 (works fine on corporate builds). -- Olivier -Message d'origine- De : Jason van Zyl [mailto:[EMAIL PROTECTED] Envoyé : mercredi 13 juin 2007 07:13 À : Maven Developers List Objet : [VOTE] Release Maven 2.0.7 Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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] 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] -- jesse mcconnell [EMAIL PROTECTED]
AW: [VOTE] Release Maven 2.0.7 - surefire problem
I got the same error just some hours ago, using maven 2.0.6 and the surefire-plugin 2.3 . And yes, adding a dependcy to junit solved the problem. Only thing is, I don't use any unit tests in that project (used only to build a Jboss SAR file), so this behaviour seems a bit strange to me It seems the test phase always requires the junit dependency (I don't call it explicitly in the POM). Cheers, Frank -Ursprüngliche Nachricht- Von: Kenney Westerhof [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 13. Juni 2007 17:13 An: Maven Developers List Betreff: Re: [VOTE] Release Maven 2.0.7 - surefire problem Mark Donszelmann wrote: Hi Kenney, Hi Mark, I was using 2.1.3 for surefire. Changed it to 2.3, and still get error (slightly different): Hi, this is fixed later on; i think you're missing a dependency on junit. Let me know if this is the case. Can't be due to 2.0.7 though, unless this works in 2.0.6? If there's no released version (2.3) that works for 2.0.7 then we need to release 2.3.1 asap. -- Kenney java.lang.NullPointerException at org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter(SurefirePlugin.java:594) at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:391) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) My pom (fragment): plugin artifactIdmaven-surefire-plugin/artifactId version2.3/version configuration forkModepertest/forkMode includes include**/*TestSuite.java/include /includes excludes exclude**/TestSuite.java/exclude /excludes /configuration /plugin Could not test SNAPSHOTs yet. Regards Mark Donszelmann On Jun 13, 2007, at 6:18 AM, Kenney Westerhof wrote: Hi, can you find the surefire plugin version you're using? I've fixed this problem in the latest snapshots. Only the snapshots were faulty, latest release should be fine. If that one is broken too, can you try one of the latest snapshots (2.4-snapshot or 2.3.1-snapshot), so we can determine wheter it's a fault in surefire or in maven 2.0.7? Thanks, Kenney Mark Donszelmann wrote: Hi tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells me following in one case: RUN ABORTED java.lang.LinkageError org.apache.maven.surefire.Runner An exception or error caused a run to abort. Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints running with -e gives me: org.apache.maven.lifecycle.LifecycleExecutionException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at
Working on Maven Ant Tasks 2.0.7
Herve, You going to be free anytime this weekend. I can make some time this weekend to work with you and apply all the patches you've put in with the goal of staging the release on Monday and try to make the tentative release date of next Wednesday. Let me know if that works for you. I can be available anytime this weekend as I'll be working on another batch of work in the embedder. Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: [VOTE] Release Maven 2.0.7 - surefire problem
Steinhauer, Frank wrote: I got the same error just some hours ago, using maven 2.0.6 and the surefire-plugin 2.3 . And yes, adding a dependcy to junit solved the problem. Yup, this is an old bug I remember fixing a while back. Only thing is, I don't use any unit tests in that project (used only to build a Jboss SAR file), so this behaviour seems a bit strange to me According to the old code, the surefirebooter is constructed if: - the 'test' parameter (-Dmaven.test.skip or from config) is not false, and - the testclassesdirectory exists, wheter it has testclasses or not. Testclassesdirectory (target/test-classes) is created by the compiler plugin, ONLY if the testsourceroot exists (src/test/java). So, remove your empty src/test/java/ directory and it's fixed. Or use the latest 2.3.1 or 2.4 snapshots for surefire. At least, this is not a problem that's due to maven-2.0.7. It seems the test phase always requires the junit dependency (I don't call it explicitly in the POM). Cheers, Frank -Ursprüngliche Nachricht- Von: Kenney Westerhof [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 13. Juni 2007 17:13 An: Maven Developers List Betreff: Re: [VOTE] Release Maven 2.0.7 - surefire problem Mark Donszelmann wrote: Hi Kenney, Hi Mark, I was using 2.1.3 for surefire. Changed it to 2.3, and still get error (slightly different): Hi, this is fixed later on; i think you're missing a dependency on junit. Let me know if this is the case. Can't be due to 2.0.7 though, unless this works in 2.0.6? If there's no released version (2.3) that works for 2.0.7 then we need to release 2.3.1 asap. -- Kenney java.lang.NullPointerException at org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter(SurefirePlugin.java:594) at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:391) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) My pom (fragment): plugin artifactIdmaven-surefire-plugin/artifactId version2.3/version configuration forkModepertest/forkMode includes include**/*TestSuite.java/include /includes excludes exclude**/TestSuite.java/exclude /excludes /configuration /plugin Could not test SNAPSHOTs yet. Regards Mark Donszelmann On Jun 13, 2007, at 6:18 AM, Kenney Westerhof wrote: Hi, can you find the surefire plugin version you're using? I've fixed this problem in the latest snapshots. Only the snapshots were faulty, latest release should be fine. If that one is broken too, can you try one of the latest snapshots (2.4-snapshot or 2.3.1-snapshot), so we can determine wheter it's a fault in surefire or in maven 2.0.7? Thanks, Kenney Mark Donszelmann wrote: Hi tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells me following in one case: RUN ABORTED java.lang.LinkageError org.apache.maven.surefire.Runner An exception or error caused a run to abort. Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints running with -e gives me: org.apache.maven.lifecycle.LifecycleExecutionException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at
Re: [VOTE] Release Maven 2.0.7
I don't really grok why this set of problems have come up now, but I don't agree with requiring a surefire plugin upgrade to upgrade to 2.0.7. We've been advocating pinning the version of plugins - that would be nastiness to have to go and change them. If 2.1.3 or 2.2 or 2.3 of surefire work with 2.0.6, then they should work with 2.0.7. Just take 2.3.1-SNAPSHOT and 2.4-SNAPSHOT right out of the equation. - Brett On 14/06/2007, at 1:08 AM, Jason van Zyl wrote: If you can try this with the latest snapshot of surefire that would be greatly appreciated. I know what the problem is inside Maven, but if Surefire is loading the same problem classes in a different way then we are going to have a problem. So if you can do a quick check using the snapshot of surefire then we can work from there to make them work together. Kenney can help you track it down and we'll fix the problem. If necessary we'll try to accelerate the release of Surefire and get that out before we push 2.0.7 into the wild. On 13 Jun 07, at 1:08 AM 13 Jun 07, Mark Donszelmann wrote: Hi tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells me following in one case: RUN ABORTED java.lang.LinkageError org.apache.maven.surefire.Runner An exception or error caused a run to abort. Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints running with -e gives me: org.apache.maven.lifecycle.LifecycleExecutionException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java: 255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: There are test failures. at org.apache.maven.test.SurefirePlugin.execute (SurefirePlugin.java:389) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:539) ... 16 more I have seen this error before on 2.0.6 which refrained me from using it. 2.0.5 works fine though. Any idea? Do ot let me hold up the release, I am sure it is a config error on my side, but if you have a hint, let me know. Regards Mark Donszelmann On Jun 12, 2007, at 10:12 PM, Jason van Zyl wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To
Re: [VOTE] Release Maven 2.0.7
It's possibly a problem in the windows batch file in 2.0.7 - I think it was changed and it may no longer be correctly propogating the error code. - Brett On 14/06/2007, at 1:07 AM, Jason van Zyl wrote: Is this not a release plugin problem? If this error halted your build, was this with an older version of the release plugin? On 13 Jun 07, at 8:01 AM 13 Jun 07, Julien HENRY wrote: (non-binding) -1 I just tried to prepare a release in a multi-module project. Usually, the release:prepare failed (because Maven does not find released dependent artifact). An easy fix was to run mvn install and then mvn release:prepare again. The problem I have with maven-2.0.7 is release preparation was not stopped (build is successful). The exception was ignored, and the release is not safe (what happend when it is a serious error?) Here is the log : [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: [INFO] Checking dependencies and plugins for snapshots ... What is the release version for XXX? (X) 3.0.11: : What is the release version for ? () 3.0.11: : ... What is SCM release tag or label for X? (X) xx-3.0.11: : What is the new development version for XXX? (X) 3.0.12-SNAPSHOT: : What is the new development version for ? (YY) 3.0.12-SNAPSHOT: : ... [INFO] Transforming 'XXX'... [INFO] Transforming 'YYY'... ... [INFO] Executing preparation goals 'clean integration-test'... [INFO] Executing: mvn clean integration-test --no-plugin-updates [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] X [INFO] Y [INFO] ... [INFO] - --- [INFO] Building [INFO]task-segment: [clean, integration-test] [INFO] - --- [INFO] [clean:clean] [INFO] - --- [INFO] Building YYY [INFO]task-segment: [clean, integration-test] [INFO] - --- [INFO] [clean:clean] ... [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] No sources to compile [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [war:war] [INFO] Exploding webapp... [INFO] Assembling webapp YYY in D:\Projets\xxx\target\YY-3.0.11 [INFO] Copy webapp webResources to D:\Projets\xx\target \YY-3.0.11 [INFO] - --- [ERROR] FATAL ERROR [INFO] - --- [INFO] basedir C:\Documents and Settings\jhenry\.m2\repository\xxx \YY\3.0.11 does not exist [INFO] - --- [INFO] Trace java.lang.IllegalStateException: basedir C:\Documents and Settings\jhenry\.m2\repository\x\Y \3.0.11 does not exist at org.codehaus.plexus.util.DirectoryScanner.scan (DirectoryScanner.java:542) at org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles (AbstractWarMojo.java:824) at org.apache.maven.plugin.war.AbstractWarMojo.copyResources (AbstractWarMojo.java:408) at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp (AbstractWarMojo.java:518) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp (AbstractWarMojo.java:347) at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java: 164) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
Re: [VOTE] Release Maven 2.0.7
Jason van Zyl wrote: tentative -1 for releasing as is: I found a serious bug in maven 2.0.6 and 2.0.7 (2.0.5 works fine): mvn clean deploy on plexus-utils fails (stacktrace and output below) due to a NoClassDefFound on IOUtil in plexus-utils. I'm using released versions of wagon and the deploy plugin (cleaned local repo). This happens inside the webdav wagon, of which there is no sign anywhere in the debug output. I think it's due to the fact tha wagon alpha-5 is used, instead of beta-2, which does not have the dep on p-u yet (in wagon-api). Anyway, we can't release this version without upgrading the deps to wagon, I think. Unless ofcourse there's something very nasty going on on my machine, which is likely because I really don't think that nobody did a deploy using 2.0.6. Can anybody confirm? Here's the output using 2.0.7: [DEBUG] org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:2.3:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime (selected for runtime) [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Adding managed dependencies for org.apache.maven:maven-core [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5 [DEBUG] org.apache.maven:maven-core:jar:2.0:runtime (selected for runtime) [DEBUG] Adding managed dependencies for unknown:maven-settings [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5 [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Adding managed dependencies for unknown:maven-plugin-parameter-documenter [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5 [DEBUG] org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG]
Re: [VOTE] Release Maven 2.0.7
Brett Porter wrote: I don't really grok why this set of problems have come up now, but I don't agree with requiring a surefire plugin upgrade to upgrade to 2.0.7. We've been advocating pinning the version of plugins - that would be nastiness to have to go and change them. If 2.1.3 or 2.2 or 2.3 of surefire work with 2.0.6, then they should work with 2.0.7. Just take 2.3.1-SNAPSHOT and 2.4-SNAPSHOT right out of the equation. Yup. We've established that 2.3 works fine with 2.0.7, though still contains very old bugs that have long been resolved. We can release 2.0.7 before surefire 2.3.1. - Brett On 14/06/2007, at 1:08 AM, Jason van Zyl wrote: If you can try this with the latest snapshot of surefire that would be greatly appreciated. I know what the problem is inside Maven, but if Surefire is loading the same problem classes in a different way then we are going to have a problem. So if you can do a quick check using the snapshot of surefire then we can work from there to make them work together. Kenney can help you track it down and we'll fix the problem. If necessary we'll try to accelerate the release of Surefire and get that out before we push 2.0.7 into the wild. On 13 Jun 07, at 1:08 AM 13 Jun 07, Mark Donszelmann wrote: Hi tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells me following in one case: RUN ABORTED java.lang.LinkageError org.apache.maven.surefire.Runner An exception or error caused a run to abort. Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints running with -e gives me: org.apache.maven.lifecycle.LifecycleExecutionException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: There are test failures. at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:389) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more I have seen this error before on 2.0.6 which refrained me from using it. 2.0.5 works fine though. Any idea? Do ot let me hold up the release, I am sure it is a config error on my side, but if you have a hint, let me know. Regards Mark Donszelmann On Jun 12, 2007, at 10:12 PM, Jason van Zyl wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at
Re: Sanity check the 2.0.7 release candidate
Happy to take it for a spin when I get up tomorrow, but one thing I've noticed is that the tests still don't pass in CI: testDependencyManagementOverridesTransitiveDependencyVersion (org.apache.maven.project.inheritance.t11.ProjectInheritanceTest) - Brett On 13/06/2007, at 3:04 PM, Jason van Zyl wrote: On 12 Jun 07, at 9:50 PM 12 Jun 07, Jason van Zyl wrote: If anyone has a few spare cycles if they could try the 2.0.7 release candidate I would appreciate it: http://people.apache.org/~jvanzyl/maven-2.0.7/ I've run the ITs with the distributions there and if a couple more people give it a whirl I'll put it up for a vote. Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7
I've successfully done deployments with 2.0.6 elsewhere, but I get the same problem on utils. I get different failures with dav in earlier versions so I think this is just a problem deploying p-utils and the container since they are in use and not properly separated. - Brett On 14/06/2007, at 2:32 AM, Kenney Westerhof wrote: Jason van Zyl wrote: tentative -1 for releasing as is: I found a serious bug in maven 2.0.6 and 2.0.7 (2.0.5 works fine): mvn clean deploy on plexus-utils fails (stacktrace and output below) due to a NoClassDefFound on IOUtil in plexus-utils. I'm using released versions of wagon and the deploy plugin (cleaned local repo). This happens inside the webdav wagon, of which there is no sign anywhere in the debug output. I think it's due to the fact tha wagon alpha-5 is used, instead of beta-2, which does not have the dep on p-u yet (in wagon-api). Anyway, we can't release this version without upgrading the deps to wagon, I think. Unless ofcourse there's something very nasty going on on my machine, which is likely because I really don't think that nobody did a deploy using 2.0.6. Can anybody confirm? Here's the output using 2.0.7: [DEBUG] org.apache.maven.plugins:maven-deploy-plugin:maven-plugin: 2.3:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-repository-metadata:jar: 2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0- alpha-8:runtime (selected for runtime) [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0- alpha-5:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Adding managed dependencies for org.apache.maven:maven-core [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0- alpha-5 [DEBUG] org.apache.maven:maven-core:jar:2.0:runtime (selected for runtime) [DEBUG] Adding managed dependencies for unknown:maven-settings [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0- alpha-5 [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0- alpha-5:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Adding managed dependencies for unknown:maven-plugin- parameter-documenter [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5 [DEBUG]
Re: [VOTE] Release Maven 2.0.7
On 14/06/2007, at 2:34 AM, Kenney Westerhof wrote: Brett Porter wrote: I don't really grok why this set of problems have come up now, but I don't agree with requiring a surefire plugin upgrade to upgrade to 2.0.7. We've been advocating pinning the version of plugins - that would be nastiness to have to go and change them. If 2.1.3 or 2.2 or 2.3 of surefire work with 2.0.6, then they should work with 2.0.7. Just take 2.3.1-SNAPSHOT and 2.4-SNAPSHOT right out of the equation. Yup. We've established that 2.3 works fine with 2.0.7, though still contains very old bugs that have long been resolved. We can release 2.0.7 before surefire 2.3.1. Cool. I'm all for hurrying to a 2.3.1 surefire release (its pretty much done - and it's next on my list, so a vote by end of week). Just didn't want to tie it to the maven release in any way. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
data converter somewhat complete
I've completed the database converter for both continuum and redback/ plexus-security databases. Anyone running an old trunk snapshot should be able to use this to backup to xml, and reimport into the new installations database. It can also be used for general backups to xml. The CLI should be self explanatory, but I'll cleanup and document at some point too. Though the infrastructure is in place, I've not set the models up for 1.0.3 - 1.1. We should look at that before a 1.1 final release. In addition, I've upgraded the maven zone continuum and will get that running regularly again. Any questions/thoughts? Cheers, Brett
Re: Sanity check the 2.0.7 release candidate
On 13 Jun 07, at 9:36 AM 13 Jun 07, Brett Porter wrote: Happy to take it for a spin when I get up tomorrow, but one thing I've noticed is that the tests still don't pass in CI: testDependencyManagementOverridesTransitiveDependencyVersion (org.apache.maven.project.inheritance.t11.ProjectInheritanceTest) Works now after switching back what the release plugin did to the tree. I've run it a million times now and all the tests pass. - Brett On 13/06/2007, at 3:04 PM, Jason van Zyl wrote: On 12 Jun 07, at 9:50 PM 12 Jun 07, Jason van Zyl wrote: If anyone has a few spare cycles if they could try the 2.0.7 release candidate I would appreciate it: http://people.apache.org/~jvanzyl/maven-2.0.7/ I've run the ITs with the distributions there and if a couple more people give it a whirl I'll put it up for a vote. Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7
+1, tested on my m2 projects Arnaud On 13/06/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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] -- .. Arnaud HERITIER .. OCTO Technology - [EMAIL PROTECTED] www.octo.com | blog.octo.com .. ASF - [EMAIL PROTECTED] www.apache.org | maven.apache.org ...
Re: Working on Maven Ant Tasks 2.0.7
Hi Jason, No problem for sunday (PM for me, AM for you) : there are only 2 Jira to commit, one of which is really important (and finally reduced to 1 line patch: MANTTASKS-18). Regards, Hervé Le mercredi 13 juin 2007, Jason van Zyl a écrit : Herve, You going to be free anytime this weekend. I can make some time this weekend to work with you and apply all the patches you've put in with the goal of staging the release on Monday and try to make the tentative release date of next Wednesday. Let me know if that works for you. I can be available anytime this weekend as I'll be working on another batch of work in the embedder. Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7
Brett Porter wrote: I've successfully done deployments with 2.0.6 elsewhere, but I get the same problem on utils. I get different failures with dav in earlier versions so I think this is just a problem deploying p-utils and the container since they are in use and not properly separated. Indeed. I can succesfully deploy other stuff. That's so weird, why does the artifact to be deployed end up in the plugin classpath? And where does the webdav provider come from? All that wagon stuff is downloaded, yet not present with -X. If it's in the core, and filtered out, why is it downloaded... Anyway, I'm revoking my -1 and changing it to +1, though not being able to deploy p-c-d or p-u is a serious drawback. But i guess it doesn't matter as 2.0.6 has the same problems so it's not worse ;) -- Kenney - Brett On 14/06/2007, at 2:32 AM, Kenney Westerhof wrote: Jason van Zyl wrote: tentative -1 for releasing as is: I found a serious bug in maven 2.0.6 and 2.0.7 (2.0.5 works fine): mvn clean deploy on plexus-utils fails (stacktrace and output below) due to a NoClassDefFound on IOUtil in plexus-utils. I'm using released versions of wagon and the deploy plugin (cleaned local repo). This happens inside the webdav wagon, of which there is no sign anywhere in the debug output. I think it's due to the fact tha wagon alpha-5 is used, instead of beta-2, which does not have the dep on p-u yet (in wagon-api). Anyway, we can't release this version without upgrading the deps to wagon, I think. Unless ofcourse there's something very nasty going on on my machine, which is likely because I really don't think that nobody did a deploy using 2.0.6. Can anybody confirm? Here's the output using 2.0.7: [DEBUG] org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:2.3:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime (selected for runtime) [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] Adding managed dependencies for org.apache.maven:maven-core [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5 [DEBUG] org.apache.maven:maven-core:jar:2.0:runtime (selected for runtime) [DEBUG] Adding managed dependencies for unknown:maven-settings [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5 [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG]
Re: Question regarding a Plugin
Try posting this question on the user group - you may get more of a response. Eric On 6/11/07, Adam Altemus [EMAIL PROTECTED] wrote: Hey everyone, We (MobilVox, http://www.mobilvox.com) are working on a Maven JavaScript Plugin. Possible goals are compression (already implemented), JSDoc generation, and JSUnit testing. My question is this: I have the Compression MOJO to the point where it will compress JS in the target directory and either create a second WAR w/ compressed JS or overwrite the existing. In the first case how do I get this WAR included so that when install and deploy run, the file and it's associated directory are sent to the correct repositories with the other artifacts? Thanks in advance, Adam Altemus -- Eric Redmond http://www.sonatype.com
Re: Sanity check the 2.0.7 release candidate
Looking at the latest build from there, it is still failing. On 14/06/2007, at 3:51 AM, Jason van Zyl wrote: On 13 Jun 07, at 9:36 AM 13 Jun 07, Brett Porter wrote: Happy to take it for a spin when I get up tomorrow, but one thing I've noticed is that the tests still don't pass in CI: testDependencyManagementOverridesTransitiveDependencyVersion (org.apache.maven.project.inheritance.t11.ProjectInheritanceTest) Works now after switching back what the release plugin did to the tree. I've run it a million times now and all the tests pass. - Brett On 13/06/2007, at 3:04 PM, Jason van Zyl wrote: On 12 Jun 07, at 9:50 PM 12 Jun 07, Jason van Zyl wrote: If anyone has a few spare cycles if they could try the 2.0.7 release candidate I would appreciate it: http://people.apache.org/~jvanzyl/maven-2.0.7/ I've run the ITs with the distributions there and if a couple more people give it a whirl I'll put it up for a vote. Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.7
+1, works fine for me though I wasn't able to test deploying Arnaud HERITIER wrote: +1, tested on my m2 projects Arnaud On 13/06/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=10500styleName=Htmlversion=13138 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/ Staging repository: http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/maven-2.0.7/ 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: Question regarding a Plugin
I found my answer so it's cool. BTW, we are getting ready to release an alpha version of it soon and I was curious as to how to go about it/best practices for doing so. Thanks. Adam On 6/13/07, Eric Redmond [EMAIL PROTECTED] wrote: Try posting this question on the user group - you may get more of a response. Eric On 6/11/07, Adam Altemus [EMAIL PROTECTED] wrote: Hey everyone, We (MobilVox, http://www.mobilvox.com) are working on a Maven JavaScript Plugin. Possible goals are compression (already implemented), JSDoc generation, and JSUnit testing. My question is this: I have the Compression MOJO to the point where it will compress JS in the target directory and either create a second WAR w/ compressed JS or overwrite the existing. In the first case how do I get this WAR included so that when install and deploy run, the file and it's associated directory are sent to the correct repositories with the other artifacts? Thanks in advance, Adam Altemus -- Eric Redmond http://www.sonatype.com -- Adam Altemus Home e-mail [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: some closed issues
ping... On 06/06/2007, at 4:40 PM, Brett Porter wrote: I have some questions about specific closed issues that might warrant reopening: On 05/06/2007, at 3:05 PM, Jason van Zyl (JIRA) wrote: Jason van Zyl closed MNG-5. --- Resolution: Fixed pretty resources addition - Was this really implemented, or was it intended to close won't fix? To my knowledge, we have no such feature. Jason van Zyl deleted MNG-3019: --- does commons-validator require the xml-apis dependency? --- Why delete the issue? Unless it was completely mistakenly filed, I think we should just close incomplete/won't fix otherwise it's impossible to get back and the information is lost. Jason van Zyl closed MNG-1830. -- Resolution: Won't Fix Bootstrap is entirely different now. Ant-based and it's not really a problem making sure you have the right Maven ... knowing from experience building it 20 times a day when applying patches for example. add a 'compiled on timestamp' label when maven 2 is invoked with --version option I think this would be a useful thing to add if the patch still applies (not just as part of the bootstrap, but as a check on the released version). Can we reopen? Jason van Zyl closed MNG-2522. -- Resolution: Fixed Regression for the Eclipse codestyle Wasn't really sure if this was fixed, or the patch just out of date. Is the eclipse code style on the site good now? Jason van Zyl closed MNG-728. - Don't re-open this until you have patches, test projects, and you have run the integration tests. I'm processing all patches to start a new way of accepting patches and test projects. I will be finished processing all the patches today and I'll make instructions on how to submit requests for updating Maven. I reopened this because there were patches and it was optional, non- default functionality. If the patches had a specific problem we should keep it open but unflag it until they are updated, right? Thanks, Brett - 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: Working on Maven Ant Tasks 2.0.7
On 13 Jun 07, at 11:06 AM 13 Jun 07, Hervé BOUTEMY wrote: Hi Jason, No problem for sunday (PM for me, AM for you) : there are only 2 Jira to commit, one of which is really important (and finally reduced to 1 line patch: MANTTASKS-18). Sounds good. I will get those applied and built so you can validate it works and then let's put it up for a vote on Monday. Regards, Hervé Le mercredi 13 juin 2007, Jason van Zyl a écrit : Herve, You going to be free anytime this weekend. I can make some time this weekend to work with you and apply all the patches you've put in with the goal of staging the release on Monday and try to make the tentative release date of next Wednesday. Let me know if that works for you. I can be available anytime this weekend as I'll be working on another batch of work in the embedder. Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
