Re: Maven 3.0 and maven-metadata.xml download
Hi Arnaud, One more information. I've added the missing version declaration for plug-ins and now Maven 3 don't try to download those files. I think this is just a side effect for not solving Maven 3 warnings. Should I still create an issue? Cheers, Henrique 2010/8/18 Arnaud Héritier : > Can you open an issue with some logs showing the issue and the version you > are using > We already published severals alpha and 2 beta > > Thx > > Arnaud > > On Aug 19, 2010, at 12:21 AM, Henrique Prange wrote: > >> Hi all, >> >> Not a show stopper, but Maven 3 tries to download the same >> maven-metadata.xml files every time and for every module. It doesn't >> cause any problems, but it increases the build time a lot. >> >> Cheers, >> >> Henrique >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven 3.0 and maven-metadata.xml download
Hi all, Not a show stopper, but Maven 3 tries to download the same maven-metadata.xml files every time and for every module. It doesn't cause any problems, but it increases the build time a lot. Cheers, Henrique - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Compilation problem with Maven 3.0-beta-1
Hi Jason, On 01/05/10 13:54, Jason van Zyl wrote: On May 1, 2010, at 10:31 AM, Benjamin Bentmann wrote: Jason van Zyl wrote: Didn't Henrique just remove the packaging element from the component definition of the artifact handler to get this to work? In fact, I have also changed the plug-in implementation to not create the dummy woframework artifact. Cheers, Henrique Yes, to get the artifact handler to work with Maven 2 as originally intended. That's what I was saying we should ignore. If we ignored that packaging element in the component descriptor for the artifact handler Henrique would not have had to make any changes, yes? If that's the case we should just knock them out automatically for users. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Compilation problem with Maven 3.0-beta-1
Hi Benjamin, It did the trick. The solution worked for both Maven 2.2.1 and Maven 3, as you said. Just out of curiosity, will the definition of a lifecycle extension change after Maven 3 integration with Guice is complete? Thank you very much for your help. Cheers, Henrique On 30/04/10 10:47, Benjamin Bentmann wrote: Henrique Prange wrote: When building from the parent module using Maven 3, the following classpath entry has been produced: [...]/Wonder/Frameworks/Core/JavaWOExtensions/target/JavaWOExtensions-5.0.0-SNAPSHOT.woframework And the produced classpath entry for the same build using Maven 2.2.1: [...]/Wonder/Frameworks/Core/JavaWOExtensions/target/JavaWOExtensions-5.0.0-SNAPSHOT.jar Note the file extension is wrong. It should be .jar instead of .woframework. Yes, that's the relevant log demonstrating the discrepancy, thanks. So, is it a Maven 3 problem? Is it a problem in the 3rd party plug-in? There's a change in behavior between Maven 2 and 3 regarding the artifact handler being used for the project main artifact in combination with extension plugins. The project JavaWOExtensions uses woframework and the corresponding artifact handler definition from the maven-wolifecycle-plugin looks basically like this: woframework jar jar However, in Maven 2, this artifact handler is *not* used for the main artifact of JavaWOExtensions, because Maven looks for a matching artifact handler based on the handler's (which is "jar" here) instead of matching via the handler's . This opens the door for some oddities. The lookup via handler packaging is inconsistent with the way artifact handlers are determined for all the other plugin/dependency artifacts encountered in the build. Besides, having this kind of artifact handler lookup only happen in the presence of one or more extension plugins effectively means an ordinary project with packaging=jar and some extension plugin might end up using the artifact handler of type "test-jar" because this handler has the same packaging as the handler of type "jar". The same goes for projects with packaging "ejb" that non-deterministically chose from either the handler of type "ejb" or "ejb-client". The lucky incidence that those handlers have equal characteristics regarding file extension and class path handling made this internal oddity never show up to users. In the concrete case of the maven-wolifecycle-plugin, this yields to projects that produce/install/deploy artifacts named JavaWOExtensions-5.0.0-SNAPSHOT.woframework. However, projects with packaging=woframework are supposed to produce JARs and so the plugin authors worked around this by a) attaching their intended main artifact like JavaWOExtensions-5.0.0-SNAPSHOT.jar as an artifact of type "jar" b) took the thoroughness to document that the actual project main file *.woframework is unwanted garbage by writing this as its contents: "This is an empty file created beacuse of the Maven extension mechanism." After some chat with Brett about the selection of artifact handlers based on their packaging, we both agree that this is actually a bug in Maven 2 and the behavior of Maven 3 is correct. The only reason artifact handlers have a appears to be support for the legacy repository layout. Henrique, seeing that you're also a committer on the WOProject, I suggest you simply remove the field from all the custom artifact handlers defined in the components.xml of the maven-wolifecycle-plugin. defaults to so this effectively seems to only change the behavior of the problematic woframework handler. This change will make the artifact handler behave the same in Maven 2 and 3 and should allow you to produce the proper project output without the need of some attached artifact. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Compilation problem with Maven 3.0-beta-1
Hi all, I've tried to build a project with multiple modules using Maven 3.0-beta-1 unsuccessfully. I got some weird compilation problems on child modules when trying to build from the parent module. But if I try to build the child module directly, it works. Any thoughts if is it a bug or something am I doing wrong? By the way, it is an open source project and you can check the configuration here [1]. [1]https://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder Cheers, Henrique - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [2.0.11 RC] Please test - RC1
Hi Brett, I've been using the RC1 since your announcement with a couple of projects without any problems. Cheers, Henrique Brett Porter wrote: Hi, I have staged a first release candidate here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/2.0.11-RC1/ Here are the issues that have been fixed: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14118 in this version. Please test it out and let us know how it goes - particularly if you are currently using 2.0.9 or 2.0.10. Thanks, Brett - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [2.0.10 RC6] please test
Hi Brian, RC4 also works correctly. Cheers, Henrique Brian E. Fox wrote: Interesting, what about RC4? -Original Message- From: Henrique Prange [mailto:hpra...@gmail.com] Sent: Wednesday, December 17, 2008 12:54 PM To: Maven Developers List Cc: Maven Users List Subject: Re: [2.0.10 RC6] please test Hi Brian, RC6 - ERROR! RC5 - ERROR! RC3 - OK! Sorry for not detecting the problem in the RC5. I didn't find time to test this release candidate. :( Cheers, Henrique Brian E. Fox wrote: Henrique, could you also try with RC5 to see if it is a new issue in this RC? I'm betting it is related to the Modello change introduced in RC6. RC5 is at: http://people.apache.org/~brianf/RC-5/org/apache/maven/apache-maven/2.0. 10-RC5/ -Original Message----- From: Henrique Prange [mailto:hpra...@gmail.com] Sent: Wednesday, December 17, 2008 8:51 AM To: Maven Developers List Cc: Maven Users List Subject: Re: [2.0.10 RC6] please test Hi Brian, I found a problem while executing 'mvn clean install' in one of my projects. (See the error below) I verified and the build works with 2.0.9 and 2.1.0-M1 without problems. Cheers, Henrique [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.model.Extension.hashCode(Extension.java:147) at java.lang.Object.toString(Object.java:209) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuffer.append(StringBuffer.java:220) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(Defau ltLifecycleExecutor.java:157) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] Brian E. Fox wrote: Hello, Thanks everyone for sticking with us this far. I have high hopes of this being the last RC. This RC fixes MNG-3898 and updates the default plugin versions in the super pom. You can see the changes to the super pom and specific versions used here: http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.10-RC/m aven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?r 1=708789&r2=726765&diff_format=h Here's the list of issues fixed in 2.0.10 (updated to remove the wagon fixes that were rolled back): http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName =Html&projectId=10500&Create=Create And I've staged RC-6 here: http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/2.0.10-RC6/ Please try it out and see if we have any remaining regressions over 2.0.9. Thanks, Brian -- Brian Fox Apache Maven PMC http://blogs.sonatype.com/brian/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For addi
Re: [2.0.10 RC6] please test
Hi Brian, RC6 - ERROR! RC5 - ERROR! RC3 - OK! Sorry for not detecting the problem in the RC5. I didn't find time to test this release candidate. :( Cheers, Henrique Brian E. Fox wrote: Henrique, could you also try with RC5 to see if it is a new issue in this RC? I'm betting it is related to the Modello change introduced in RC6. RC5 is at: http://people.apache.org/~brianf/RC-5/org/apache/maven/apache-maven/2.0. 10-RC5/ -Original Message----- From: Henrique Prange [mailto:hpra...@gmail.com] Sent: Wednesday, December 17, 2008 8:51 AM To: Maven Developers List Cc: Maven Users List Subject: Re: [2.0.10 RC6] please test Hi Brian, I found a problem while executing 'mvn clean install' in one of my projects. (See the error below) I verified and the build works with 2.0.9 and 2.1.0-M1 without problems. Cheers, Henrique [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.model.Extension.hashCode(Extension.java:147) at java.lang.Object.toString(Object.java:209) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuffer.append(StringBuffer.java:220) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(Defau ltLifecycleExecutor.java:157) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] Brian E. Fox wrote: Hello, Thanks everyone for sticking with us this far. I have high hopes of this being the last RC. This RC fixes MNG-3898 and updates the default plugin versions in the super pom. You can see the changes to the super pom and specific versions used here: http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.10-RC/m aven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?r 1=708789&r2=726765&diff_format=h Here's the list of issues fixed in 2.0.10 (updated to remove the wagon fixes that were rolled back): http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName =Html&projectId=10500&Create=Create And I've staged RC-6 here: http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/2.0.10-RC6/ Please try it out and see if we have any remaining regressions over 2.0.9. Thanks, Brian -- Brian Fox Apache Maven PMC http://blogs.sonatype.com/brian/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [2.0.10 RC6] please test
Hi Brian, I found a problem while executing 'mvn clean install' in one of my projects. (See the error below) I verified and the build works with 2.0.9 and 2.1.0-M1 without problems. Cheers, Henrique [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.model.Extension.hashCode(Extension.java:147) at java.lang.Object.toString(Object.java:209) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuffer.append(StringBuffer.java:220) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:157) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) 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) [INFO] Brian E. Fox wrote: Hello, Thanks everyone for sticking with us this far. I have high hopes of this being the last RC. This RC fixes MNG-3898 and updates the default plugin versions in the super pom. You can see the changes to the super pom and specific versions used here: http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.10-RC/m aven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?r 1=708789&r2=726765&diff_format=h Here's the list of issues fixed in 2.0.10 (updated to remove the wagon fixes that were rolled back): http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName =Html&projectId=10500&Create=Create And I've staged RC-6 here: http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/2.0.10-RC6/ Please try it out and see if we have any remaining regressions over 2.0.9. Thanks, Brian -- Brian Fox Apache Maven PMC http://blogs.sonatype.com/brian/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [2.0.10 RC] Please test
Hi Brian, Brian E. Fox wrote: The version is correct but it does seem to have the wrong embedded version. There must be a property in the pom that the release plugin didn't update. On the wagon-ssh, I'm not having issues, can you give more info on how to reproduce it? Sure. It's an open source project. You can find the pom.xml here [1] and the project source here [2]. If you change the version of wagon-ssh to 1.0-beta-4 or remove the version tag, it doesn't work. Following is the snippet of my settings.xml with the server connection data. webobjects.mdimension.com/dist/snapshots myusername Does 2.1M1 work for you? (I ported back the exact fix from that branch) I've tried it again and it didn't work too. :( On both versions (2.1-M1 and 2.0.10-RC3), it only work with wagon-ssh-1.0-beta-2. I don't know why it have worked the first time. As I've cleaned my local repo, I can't reproduce the same environment I had at that time. :( [1]https://svn.objectstyle.org/repos/woproject/trunk/woproject/pom.xml [2]https://svn.objectstyle.org/repos/woproject/trunk/woproject/ Cheers, Henrique -----Original Message- From: Henrique Prange [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2008 5:04 PM To: Maven Users List Cc: dev@maven.apache.org Subject: Re: [2.0.10 RC] Please test Hi Brian, I've tried the RC3 but it seems to be the old RC2. I've downloaded distinct packages (tar.gz and zip) on different browsers (Safari and Firefox) to avoid any cache problems. :( Following is the mvn -v output: Maven version: 2.0.10-RC2 Java version: 1.5.0_16 OS name: "mac os x" version: "10.5.5" arch: "i386" Family: "unix" I've tested anyway and the wagon-ssh issue is still there. Are you sure the staged version is the right one? Cheers, Henrique Brian Fox wrote: Hello, This RC fixes the SCP wagon problem identified in RC2 (MNG-3717). No other issues where identified in RC2 so hopefully this will become the last RC. Here's the list of issues fixed in 2.0.10: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName =Html&projectId=10500&Create=Create And I've staged RC-3 here: http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/2.0.10-RC3/ Please try it out and see if we have any remaining regressions over 2.0.9. Thanks, Brian -- Brian Fox Apache Maven PMC http://blogs.sonatype.com/people/brian/ - 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]
Re: [2.0.10 RC] Please test
Hi Brian, I've tried the RC3 but it seems to be the old RC2. I've downloaded distinct packages (tar.gz and zip) on different browsers (Safari and Firefox) to avoid any cache problems. :( Following is the mvn -v output: Maven version: 2.0.10-RC2 Java version: 1.5.0_16 OS name: "mac os x" version: "10.5.5" arch: "i386" Family: "unix" I've tested anyway and the wagon-ssh issue is still there. Are you sure the staged version is the right one? Cheers, Henrique Brian Fox wrote: Hello, This RC fixes the SCP wagon problem identified in RC2 (MNG-3717). No other issues where identified in RC2 so hopefully this will become the last RC. Here's the list of issues fixed in 2.0.10: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName =Html&projectId=10500&Create=Create And I've staged RC-3 here: http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/2.0.10-RC3/ Please try it out and see if we have any remaining regressions over 2.0.9. Thanks, Brian -- Brian Fox Apache Maven PMC http://blogs.sonatype.com/people/brian/ - 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: [PLEASE TEST] 2.1.0-M1-RC12 of Maven (was: Maven 2.0.10-RC*)
Hi John, FYI, I've tried this RC with a couple of projects (including the plug-in project) and no problems found. Thank you very much. Cheers, Henrique John Casey wrote: Hi everyone, Sorry if the subject of this message is a little confusing, but we're in the process of relabeling the code in this release candidate to be part of a new version, a departure from the 2.0.x codebase. This release candidate contains some large modifications, even though it's meant to be backward compatible, and the risk that entails makes the relabeling appropriate. In any case, I'm anticipating one of a set of possible results from this relabeling discussion, and calling this RC 2.1.0-M1-RC12 (since it needs *some* name). You can find it here: http://people.apache.org/~jdcasey/stage/apache-maven/2.1.0-M1-RC12/org/apache/maven/apache-maven/2.1.0-M1-RC12/ Please give it a try when you have time. I think you'll find this the most stable of all our attempts so far, and possibly even the one we'll promote for a final release, whatever version it winds up having. Thanks, -john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC11
Hi John, I compared the contents of the artifacts generated by 2.0.9 and 2.0.10-RC11 and they are different. The latter doesn't have the Ant build file and has a different plug-in descriptor. Another difference is the version of maven-plugin-plugin. Maven 2.0.9 uses 2.4.1 and Maven 2.0.10-RC11 uses 2.4.2. I tried to fix the version in my pom to use 2.4.1 and rebuild with 2.0.10-RC11. I had the same problem though. :( Cheers, Henrique Henrique Prange wrote: Hi John, I found something, but I can't ensure it is caused by 2.0.10-RC11. I have a Maven plug-in that extends the lifecycle and adds a new kind of package. It also uses some Ant tasks. When I build the plug-in with 2.0.10-RC* (I tried with RC1, RC2 and RC11) the build works. But when I try to build a project that depends upon this plug-in and use my custom package, I get an "required goal not found" error (below is the entire exception message). I have no problems if I build the plug-in with 2.0.9. You can access the code of this plug-in on [1]. [1]https://svn.objectstyle.org/repos/woproject/trunk/woproject/maven2/maven-wolifecycle-plugin Cheers, Henrique [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Required goal not found: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:woframework in org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.16-SNAPSHOT [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Required goal not found: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:woframework in org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.16-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1820) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1295) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1259) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:516) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:369) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java: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) [INFO] John Casey wrote: Hi again, One bug was identified in 2.0.10-RC10 last Friday night. This release candidate addresses that issue. You can find it here: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/ Please give this a spin when you get a chance, and let us know if you find any problems. We'll file any issues in JIRA against version 2.0.10 for tracking purposes, and to give us a JIRA # to use when writing the integration test to verify the fix. Thanks, -john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC11
Hi John, I found something, but I can't ensure it is caused by 2.0.10-RC11. I have a Maven plug-in that extends the lifecycle and adds a new kind of package. It also uses some Ant tasks. When I build the plug-in with 2.0.10-RC* (I tried with RC1, RC2 and RC11) the build works. But when I try to build a project that depends upon this plug-in and use my custom package, I get an "required goal not found" error (below is the entire exception message). I have no problems if I build the plug-in with 2.0.9. You can access the code of this plug-in on [1]. [1]https://svn.objectstyle.org/repos/woproject/trunk/woproject/maven2/maven-wolifecycle-plugin Cheers, Henrique [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Required goal not found: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:woframework in org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.16-SNAPSHOT [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Required goal not found: org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:woframework in org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.16-SNAPSHOT at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1820) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1295) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1259) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:516) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:369) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java: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) [INFO] John Casey wrote: Hi again, One bug was identified in 2.0.10-RC10 last Friday night. This release candidate addresses that issue. You can find it here: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/ Please give this a spin when you get a chance, and let us know if you find any problems. We'll file any issues in JIRA against version 2.0.10 for tracking purposes, and to give us a JIRA # to use when writing the integration test to verify the fix. Thanks, -john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC6
Hi Jonh, I've tried RC6 for my projects on Hudson and I get the above exception for all projects. Building with RC6 from terminal works. Building with 2.0.9 or RC4 on Hudson also works. Cheers, Henrique [INFO] [clean:clean] [HUDSON] Archiving /Users/hprange/.hudson/jobs/pas/workspace/trunk/pom.xml to /Users/hprange/.hudson/jobs/pas/modules/moleque.pas$pas/builds/2008-08-11_15-21-09/archive/moleque.pas/pas/0.4-SNAPSHOT/pom.xml [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [DEBUG] Trace java.lang.NullPointerException at org.apache.maven.lifecycle.DefaultLifecycleExecutor.restoreDynamicState(DefaultLifecycleExecutor.java:779) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:636) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:533) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:364) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:325) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:42) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:133) at hudson.maven.MavenBuilder.call(MavenBuilder.java:129) at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:528) at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:474) at hudson.remoting.UserRequest.perform(UserRequest.java:69) at hudson.remoting.UserRequest.perform(UserRequest.java:23) at hudson.remoting.Request$2.run(Request.java:206) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:613) [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Mon Aug 11 15:21:18 BRT 2008 [INFO] Final Memory: 9M/16M [INFO] channel stopped finished: FAILURE John Casey wrote: Hi everyone, Well, I think I've finally managed to reduce the memory consumption and boost the speed of the RC5 build. In addition, I've fixed a couple of exceptions that came up - a NPE related to POM configuration interpolation, and a ClassCastException related to settings profiles without id's. The release notes for 2.0.10 (so far) are here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112 You can do a search for recently resolved in that Fix-For version to see what I resolved for this RC, though the summary above is a pretty accurate reflection. The distro is here: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC6/org/apache/maven/apache-maven/2.0.10-RC6 Please give it a spin and see what you think! And, have a good weekend. -john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC1
Hi John, I've tried Maven 2.0.10-RC1 with one of my projects and got a NullPointerException while resolving dependencies (below is the stack trace). It works using Maven 2.0.9. Should I file a bug on Jira with fix-for 2.0.10? Cheers, Henrique hprange:pas-human-resources-model hprange$ mvn clean install [INFO] Scanning for projects... [...] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.artifact.resolver.ResolutionNode.getKey(ResolutionNode.java:84) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:393) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:424) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:424) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:424) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1451) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:406) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:578) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:498) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:350) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:162) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:127) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java: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) John Casey wrote: Hi again, As promised, I've staged the first release candidate for Maven 2.0.10 here: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/ The issues resolved for this release (so far) are here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112 If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is still open. This is because one of the possible solutions to this issue - and the only one that the Maven project really has control over - depends on re-releasing a new version of commons-build-plugin that will depend on the eventual 2.0.10 version of maven-script-ant. Please, try out this release candidate and let me know what's broken! Once things stabilize, I'll kick it out to the users to have a go, then if it's still stable after that (or, whatever RC we find is stable at that point), I'll call a vote to release. At that point, I'll run a new build to generate artifacts without the RC# suffix in the version. Thanks! -john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
