You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by John Casey <jd...@commonjava.org> on 2008/08/23 01:27:18 UTC
[PLEASE TEST] Maven 2.0.10-RC10
Hi again everyone,
I wanted to announce the availability of the latest release candidate,
2.0.10-RC10. You can grab it here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC10/org/apache/maven/apache-maven/2.0.10-RC10
I've closed the few issues that came out of RC9, and improved
performance a great deal, so please give it a spin and let me know what
you think.
Also, while I know we've been talking on the dev list about releasing
this code as Maven 2.1.0 (with the current trunk code now pushing toward
a 3.0 release), I'm just going to keep referring to this as 2.0.10-RCxx
until we finalize the direction with a vote. Everyone knows about this
release candidate series by now, so it's as much to reduce possible
confusion as anything else.
Happy testing!
-john
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by John Casey <jd...@commonjava.org>.
See MNG-3724
John Casey wrote:
> I've got the fix on my machine, just testing to see what it does to
> performance numbers.
>
> -john
>
> Daniel Kulp wrote:
>> John,
>>
>> Performance is looking very good. My testcase that runs in 32secs
>> on 2.0.9 runs in 26sec with this RC. Very nice job.
>>
>> However, there seems to be a problem with it and the eclipse plugin in
>> a reactor build. With the CXF build, run:
>>
>> mvn test-compile eclipse:eclipse -Pnochecks -o
>>
>> and check the api/.classpath file.
>>
>> With 2.0.9, there is a line:
>> <classpathentry kind="src" path="target/generated/src/test/java"
>> output="target/test-classes"/>
>> which is correct. With 2.0.10, that line is not there which makes it
>> not compile in eclipse.
>>
>> If I run the same command in the api directory, the .classpath file is
>> fine.
>>
>>
>>
>> Dan
>>
>>
>>
>> On Friday 22 August 2008 7:27:18 pm John Casey wrote:
>>> Hi again everyone,
>>>
>>> I wanted to announce the availability of the latest release candidate,
>>> 2.0.10-RC10. You can grab it here:
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC10/org/apache
>>>
>>> /maven/apache-maven/2.0.10-RC10
>>>
>>> I've closed the few issues that came out of RC9, and improved
>>> performance a great deal, so please give it a spin and let me know what
>>> you think.
>>>
>>> Also, while I know we've been talking on the dev list about releasing
>>> this code as Maven 2.1.0 (with the current trunk code now pushing toward
>>> a 3.0 release), I'm just going to keep referring to this as 2.0.10-RCxx
>>> until we finalize the direction with a vote. Everyone knows about this
>>> release candidate series by now, so it's as much to reduce possible
>>> confusion as anything else.
>>>
>>> Happy testing!
>>>
>>> -john
>>
>>
>>
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by John Casey <jd...@commonjava.org>.
I've got the fix on my machine, just testing to see what it does to
performance numbers.
-john
Daniel Kulp wrote:
> John,
>
> Performance is looking very good. My testcase that runs in 32secs on 2.0.9
> runs in 26sec with this RC. Very nice job.
>
> However, there seems to be a problem with it and the eclipse plugin in a
> reactor build. With the CXF build, run:
>
> mvn test-compile eclipse:eclipse -Pnochecks -o
>
> and check the api/.classpath file.
>
> With 2.0.9, there is a line:
> <classpathentry kind="src" path="target/generated/src/test/java"
> output="target/test-classes"/>
> which is correct. With 2.0.10, that line is not there which makes it not
> compile in eclipse.
>
> If I run the same command in the api directory, the .classpath file is fine.
>
>
>
> Dan
>
>
>
> On Friday 22 August 2008 7:27:18 pm John Casey wrote:
>> Hi again everyone,
>>
>> I wanted to announce the availability of the latest release candidate,
>> 2.0.10-RC10. You can grab it here:
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC10/org/apache
>> /maven/apache-maven/2.0.10-RC10
>>
>> I've closed the few issues that came out of RC9, and improved
>> performance a great deal, so please give it a spin and let me know what
>> you think.
>>
>> Also, while I know we've been talking on the dev list about releasing
>> this code as Maven 2.1.0 (with the current trunk code now pushing toward
>> a 3.0 release), I'm just going to keep referring to this as 2.0.10-RCxx
>> until we finalize the direction with a vote. Everyone knows about this
>> release candidate series by now, so it's as much to reduce possible
>> confusion as anything else.
>>
>> Happy testing!
>>
>> -john
>
>
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by Paul Benedict <pb...@apache.org>.
Peter,
The Maven team isn't asking for your source code. The request is to
provide a project -- any project -- that demonstrates the failure.
Just create a mock project that helps rear the head of the ugly error.
Paul
On Tue, Aug 26, 2008 at 1:24 AM, Peter Horlock
<pe...@googlemail.com> wrote:
> 1.5 and 1.5, and yes, it's working with Maven 2.09.
>
> Sorry, the code of my company is classified, I can't provide a testcase.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by Peter Horlock <pe...@googlemail.com>.
1.5 and 1.5, and yes, it's working with Maven 2.09.
Sorry, the code of my company is classified, I can't provide a testcase.
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by John Casey <jd...@commonjava.org>.
What's your <target> and <source> set to in the compiler plugin
configuration? Are you certain the exact same POM is working in 2.0.9?
-john
Peter Horlock wrote:
> Using RC10, the following fails, which was working with 2.0.9:
> (seems like it doesn't like enums?!)
>
> mvn clean tomcat:deploy -o
> [INFO]
> NOTE: Maven is executing in offline mode. Any artifacts not already in your
> local
> repository will be inaccessible.
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'tomcat'.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building webclient
> [INFO] task-segment: [clean, tomcat:deploy]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [clean:clean]
> [INFO] Deleting directory target
> [INFO] Preparing tomcat:deploy
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Compiling 57 source files to target\classes
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Compilation failure
>
> MyClass.java:[22,1] annotations are not supported in -source 1.3
> (try -source 1.5 to enable annotations)
> @SuppressWarnings("nls")
>
> *MyEnum.java:[17,7] 'class' or 'interface' expected*
>
> [...other, similar errors...]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.BuildFailureException: Compilation failure
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:338)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189)
> 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)
> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
> failure
> at
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
> at
> org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682)
> ... 20 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 3 seconds
> [INFO] Finished at: Mon Aug 25 13:32:46 CEST 2008
> [INFO] Final Memory: 11M/20M
> [INFO] -----------------------------------------------------
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by John Casey <jd...@commonjava.org>.
Can you provide a failing test case we could use as a basis for an
integration test? Something that would help us debug your specific use
case would be very helpful.
Thanks,
-john
Peter Horlock wrote:
>> It seems that you don't have the maven-compiler-plugin configured
>> correctly. You must set the source as 1.5 to use Enums. See [1] for more
>> information.
>>
>> [1]http://maven.apache.org/general.html#Compiling-J2SE-5
>
>
>
> Nope, I have that configured - and as I said, it's working with Maven
> 2.09...
>
>
> Peter
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by Peter Horlock <pe...@googlemail.com>.
>
> It seems that you don't have the maven-compiler-plugin configured
> correctly. You must set the source as 1.5 to use Enums. See [1] for more
> information.
>
> [1]http://maven.apache.org/general.html#Compiling-J2SE-5
Nope, I have that configured - and as I said, it's working with Maven
2.09...
Peter
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by Henrique Prange <hp...@gmail.com>.
Hi Peter,
It seems that you don't have the maven-compiler-plugin configured
correctly. You must set the source as 1.5 to use Enums. See [1] for more
information.
[1]http://maven.apache.org/general.html#Compiling-J2SE-5
Cheers,
Henrique
Peter Horlock wrote:
> Using RC10, the following fails, which was working with 2.0.9:
> (seems like it doesn't like enums?!)
>
> mvn clean tomcat:deploy -o
> [INFO]
> NOTE: Maven is executing in offline mode. Any artifacts not already in your
> local
> repository will be inaccessible.
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'tomcat'.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building webclient
> [INFO] task-segment: [clean, tomcat:deploy]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [clean:clean]
> [INFO] Deleting directory target
> [INFO] Preparing tomcat:deploy
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Compiling 57 source files to target\classes
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Compilation failure
>
> MyClass.java:[22,1] annotations are not supported in -source 1.3
> (try -source 1.5 to enable annotations)
> @SuppressWarnings("nls")
>
> *MyEnum.java:[17,7] 'class' or 'interface' expected*
>
> [...other, similar errors...]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.BuildFailureException: Compilation failure
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:338)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189)
> 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)
> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
> failure
> at
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
> at
> org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682)
> ... 20 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 3 seconds
> [INFO] Finished at: Mon Aug 25 13:32:46 CEST 2008
> [INFO] Final Memory: 11M/20M
> [INFO] -----------------------------------------------------
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by Peter Horlock <pe...@googlemail.com>.
Using RC10, the following fails, which was working with 2.0.9:
(seems like it doesn't like enums?!)
mvn clean tomcat:deploy -o
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your
local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'tomcat'.
[INFO]
------------------------------------------------------------------------
[INFO] Building webclient
[INFO] task-segment: [clean, tomcat:deploy]
[INFO]
------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory target
[INFO] Preparing tomcat:deploy
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 57 source files to target\classes
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure
MyClass.java:[22,1] annotations are not supported in -source 1.3
(try -source 1.5 to enable annotations)
@SuppressWarnings("nls")
*MyEnum.java:[17,7] 'class' or 'interface' expected*
[...other, similar errors...]
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:338)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189)
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)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
at
org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682)
... 20 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Mon Aug 25 13:32:46 CEST 2008
[INFO] Final Memory: 11M/20M
[INFO] -----------------------------------------------------
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by Daniel Kulp <dk...@apache.org>.
John,
Performance is looking very good. My testcase that runs in 32secs on 2.0.9
runs in 26sec with this RC. Very nice job.
However, there seems to be a problem with it and the eclipse plugin in a
reactor build. With the CXF build, run:
mvn test-compile eclipse:eclipse -Pnochecks -o
and check the api/.classpath file.
With 2.0.9, there is a line:
<classpathentry kind="src" path="target/generated/src/test/java"
output="target/test-classes"/>
which is correct. With 2.0.10, that line is not there which makes it not
compile in eclipse.
If I run the same command in the api directory, the .classpath file is fine.
Dan
On Friday 22 August 2008 7:27:18 pm John Casey wrote:
> Hi again everyone,
>
> I wanted to announce the availability of the latest release candidate,
> 2.0.10-RC10. You can grab it here:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC10/org/apache
>/maven/apache-maven/2.0.10-RC10
>
> I've closed the few issues that came out of RC9, and improved
> performance a great deal, so please give it a spin and let me know what
> you think.
>
> Also, while I know we've been talking on the dev list about releasing
> this code as Maven 2.1.0 (with the current trunk code now pushing toward
> a 3.0 release), I'm just going to keep referring to this as 2.0.10-RCxx
> until we finalize the direction with a vote. Everyone knows about this
> release candidate series by now, so it's as much to reduce possible
> confusion as anything else.
>
> Happy testing!
>
> -john
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by Daniel Kulp <dk...@apache.org>.
John,
Performance is looking very good. My testcase that runs in 32secs on 2.0.9
runs in 26sec with this RC. Very nice job.
However, there seems to be a problem with it and the eclipse plugin in a
reactor build. With the CXF build, run:
mvn test-compile eclipse:eclipse -Pnochecks -o
and check the api/.classpath file.
With 2.0.9, there is a line:
<classpathentry kind="src" path="target/generated/src/test/java"
output="target/test-classes"/>
which is correct. With 2.0.10, that line is not there which makes it not
compile in eclipse.
If I run the same command in the api directory, the .classpath file is fine.
Dan
On Friday 22 August 2008 7:27:18 pm John Casey wrote:
> Hi again everyone,
>
> I wanted to announce the availability of the latest release candidate,
> 2.0.10-RC10. You can grab it here:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC10/org/apache
>/maven/apache-maven/2.0.10-RC10
>
> I've closed the few issues that came out of RC9, and improved
> performance a great deal, so please give it a spin and let me know what
> you think.
>
> Also, while I know we've been talking on the dev list about releasing
> this code as Maven 2.1.0 (with the current trunk code now pushing toward
> a 3.0 release), I'm just going to keep referring to this as 2.0.10-RCxx
> until we finalize the direction with a vote. Everyone knows about this
> release candidate series by now, so it's as much to reduce possible
> confusion as anything else.
>
> Happy testing!
>
> -john
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by John Casey <jd...@commonjava.org>.
Please file a JIRA issue in http://jira.codehaus.org/browse/MNG and
attach a failing test project, if possible, that we could use to verify
the problem. The information below is far too little to diagnose the
problem.
Thanks,
-john
TM wrote:
> Multi-module project fails with NPE on assembly:assembly (assembly plugin
> used 2.2-beta-1; command used was "mvn clean install assembly:assembly
> eclipse:eclipse"). Same configuration works with Maven 2.0.9. Below you will
> find relevant excerpt from the build trace.
>
> Best regards,
> Thorsten
>
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building OSIRIS Next
> [INFO] task-segment: [assembly:assembly] (aggregator-style)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Preparing assembly:assembly
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building OSIRIS Next
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [enforcer:enforce {execution: enforce-maven}]
> [INFO] [tools:copy-legal-files {execution: install-legal-files}]
> [INFO] [site:attach-descriptor]
> [INFO] Preparing source:jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1426)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:410)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1032)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:274)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189)
> 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]
> ------------------------------------------------------------------------
> [INFO] Total time: 55 minutes 18 seconds
> [INFO] Finished at: Mon Aug 25 17:18:11 CEST 2008
> [INFO] Final Memory: 36M/126M
> [INFO]
> ------------------------------------------------------------------------
>
>
>
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC10
Posted by TM <Th...@unibas.ch>.
Multi-module project fails with NPE on assembly:assembly (assembly plugin
used 2.2-beta-1; command used was "mvn clean install assembly:assembly
eclipse:eclipse"). Same configuration works with Maven 2.0.9. Below you will
find relevant excerpt from the build trace.
Best regards,
Thorsten
[INFO]
------------------------------------------------------------------------
[INFO] Building OSIRIS Next
[INFO] task-segment: [assembly:assembly] (aggregator-style)
[INFO]
------------------------------------------------------------------------
[INFO] Preparing assembly:assembly
[INFO]
------------------------------------------------------------------------
[INFO] Building OSIRIS Next
[INFO]
------------------------------------------------------------------------
[INFO] [enforcer:enforce {execution: enforce-maven}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] null
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1426)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:410)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1037)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:546)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1194)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1032)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:634)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:529)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:377)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:274)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:189)
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]
------------------------------------------------------------------------
[INFO] Total time: 55 minutes 18 seconds
[INFO] Finished at: Mon Aug 25 17:18:11 CEST 2008
[INFO] Final Memory: 36M/126M
[INFO]
------------------------------------------------------------------------
--
View this message in context: http://www.nabble.com/-PLEASE-TEST--Maven-2.0.10-RC10-tp19117054p19146039.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org