Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-29 Thread Geoffrey Wiseman 
On Fri, Aug 29, 2008 at 11:25 AM, John Casey <[EMAIL PROTECTED]> wrote:

> If you can't reproduce this problem using version 2.0.9, but can reproduce
> it (a couple times) using RC11, please file a jira issue:
>
> http://jira.codehaus.org/browse/MNG


That's the situation, yeah -- it's fine in 2.0.9 repeatedly, but not in RC11
repeatedly (either the error I sent in, or a frozen build).  I tried to
produce a simplified version of the build for an hour or two, but it's tied
up somewhere in the related internal projects -- when I take them out, the
build works.  I'm guessing it would be a fair amount of work to track it
down further, so ... I'm not going to.

I'm not hung up on this; this is an older project (currently in maintenance
rather than active development), so even if it won't build on Maven 2.0.10
or Maven 2.1, it may not be the end of the world.  Of course, it'd be *
better* if it worked in new versions of Maven, but it's not pressing for me.

http://jira.codehaus.org/browse/MNG-3736

  - Geoffrey
-- 
Geoffrey Wiseman

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-29 Thread John Casey 
If you can't reproduce this problem using version 2.0.9, but can 
reproduce it (a couple times) using RC11, please file a jira issue:


http://jira.codehaus.org/browse/MNG

I'll need you to re-run the build using RC11 and the -X command-line 
option, to produce debug output, then capture that output to a file and 
attach the file to the JIRA issue. This sort of command should work for 
capturing:


mvn blah > console.txt

Also, if you have a sample project (a mock project, not a real one from 
your work unless it's open source), this could be critical to allowing 
me to reproduce the problem in the minimum amount of time. I work on OS 
X, so it'll be difficult enough to debug this issue using a remote 
Windows VM instance, and the test project could be a real blessing.


This looks like a file-locking or permissions issue in Windows, but I 
really can't tell for sure one way or the other without more 
information. If you'd like this issue solved, I'm happy to go to the 
effort to debug and fix it, but I need your help to give me a starting 
point.


Thanks,

-john

Geoffrey Wiseman wrote:

On Mon, Aug 25, 2008 at 4:15 PM, John Casey <[EMAIL PROTECTED]> 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.



Don't know the cause of this, but with RC-11, I get this error on invocation
of the shade plugin

[INFO] Replacing
C:\dev\work\X-multiproject\console\target\X-console-2.2-SNAPSHOT.jar with
C:\dev\work\X-multiproject\console\target\X-console-2.2-SNAPSHOT-shaded.jar
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error creating shaded jar.

Embedded error:
C:\dev\work\X-multiproject\console\target\dependency-reduced-pom.xml (Access
is denied)

This isn't true on 2.0.9.

  - Geoffrey


--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-28 Thread John Casey 
Hudson is actually the use case for which I wrote that warning. The 
problem is, the DefaultLifecycleExecutor component was modified in the 
latest round of development, and now has a couple new component 
dependencies, or requirements. Since Hudson extends this component 
implementation directly instead of providing its own, its component 
definition is out of date now, and leads to weird errors when using the 
latest release candidates.


I've compensated for such use cases in the new Maven code, but I wanted 
to make it clear that the Hudson extension to this component needs to be 
adjusted. I'll clean up the message to make it clear that the 
implementor needs to adjust, not the user.


-john

Ravi Luthra wrote:

Yes it was inside Hudson. I just tested in Netbeans using external Maven,
and the warnings are not there.

On Thu, Aug 28, 2008 at 7:37 AM, John Casey <[EMAIL PROTECTED]> wrote:


Are you running this build in hudson, or in some sort of modified maven
environment?

Ravi Luthra wrote:


I don't know what this means:

[WARNING]
 WARNING 

This Maven runtime contains a LifecycleExecutor component with an
incomplete configuration.

LifecycleExecutor class:
org.apache.maven.lifecycle.LifecycleExecutorInterceptor
Missing component requirement:
org.apache.maven.project.MavenProjectBuilder


[WARNING]
 WARNING 

This Maven runtime contains a LifecycleExecutor component with an
incomplete configuration.

LifecycleExecutor class:
org.apache.maven.lifecycle.LifecycleExecutorInterceptor
Missing component requirement:
org.apache.maven.project.interpolation.ModelInterpolator

But I get that on all my builds. Is there some POM problem this could
indicate?


On Mon, Aug 25, 2008 at 1:15 PM, John Casey <[EMAIL PROTECTED]>
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/
<
http://people.apache.org/%7Ejdcasey/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

--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-28 Thread Geoffrey Wiseman 
On Mon, Aug 25, 2008 at 4:15 PM, John Casey <[EMAIL PROTECTED]> 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.
>

Don't know the cause of this, but with RC-11, I get this error on invocation
of the shade plugin

[INFO] Replacing
C:\dev\work\X-multiproject\console\target\X-console-2.2-SNAPSHOT.jar with
C:\dev\work\X-multiproject\console\target\X-console-2.2-SNAPSHOT-shaded.jar
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error creating shaded jar.

Embedded error:
C:\dev\work\X-multiproject\console\target\dependency-reduced-pom.xml (Access
is denied)

This isn't true on 2.0.9.

  - Geoffrey
-- 
Geoffrey Wiseman

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-28 Thread Ravi Luthra 
Yes it was inside Hudson. I just tested in Netbeans using external Maven,
and the warnings are not there.

On Thu, Aug 28, 2008 at 7:37 AM, John Casey <[EMAIL PROTECTED]> wrote:

> Are you running this build in hudson, or in some sort of modified maven
> environment?
>
> Ravi Luthra wrote:
>
>> I don't know what this means:
>>
>> [WARNING]
>>  WARNING 
>>
>> This Maven runtime contains a LifecycleExecutor component with an
>> incomplete configuration.
>>
>> LifecycleExecutor class:
>> org.apache.maven.lifecycle.LifecycleExecutorInterceptor
>> Missing component requirement:
>> org.apache.maven.project.MavenProjectBuilder
>>
>>
>> [WARNING]
>>  WARNING 
>>
>> This Maven runtime contains a LifecycleExecutor component with an
>> incomplete configuration.
>>
>> LifecycleExecutor class:
>> org.apache.maven.lifecycle.LifecycleExecutorInterceptor
>> Missing component requirement:
>> org.apache.maven.project.interpolation.ModelInterpolator
>>
>> But I get that on all my builds. Is there some POM problem this could
>> indicate?
>>
>>
>> On Mon, Aug 25, 2008 at 1:15 PM, John Casey <[EMAIL PROTECTED]>
>> 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/
>>> <
>>> http://people.apache.org/%7Ejdcasey/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
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-28 Thread John Casey 
Are you running this build in hudson, or in some sort of modified maven 
environment?


Ravi Luthra wrote:

I don't know what this means:

[WARNING]
 WARNING 

This Maven runtime contains a LifecycleExecutor component with an
incomplete configuration.

LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
Missing component requirement: org.apache.maven.project.MavenProjectBuilder


[WARNING]
 WARNING 

This Maven runtime contains a LifecycleExecutor component with an
incomplete configuration.

LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
Missing component requirement:
org.apache.maven.project.interpolation.ModelInterpolator

But I get that on all my builds. Is there some POM problem this could indicate?


On Mon, Aug 25, 2008 at 1:15 PM, John Casey <[EMAIL PROTECTED]> 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

--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-27 Thread Stephen Coy 

Hi there,

Our multimodule reactor builds seem to build fine with RC11. The builds
include:

1. conventional J2EE jar/ejb/war/ear composition;
2. OSGI bundles via the maven-bundle-plugin;
3. Assembly of eclipse RCP applications

Cheers

Steve C
-- 
View this message in context: 
http://www.nabble.com/-PLEASE-TEST--Maven-2.0.10-RC11-tp19150906p19192050.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-27 Thread Ravi Luthra 
I don't know what this means:

[WARNING]
 WARNING 

This Maven runtime contains a LifecycleExecutor component with an
incomplete configuration.

LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
Missing component requirement: org.apache.maven.project.MavenProjectBuilder


[WARNING]
 WARNING 

This Maven runtime contains a LifecycleExecutor component with an
incomplete configuration.

LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
Missing component requirement:
org.apache.maven.project.interpolation.ModelInterpolator

But I get that on all my builds. Is there some POM problem this could indicate?


On Mon, Aug 25, 2008 at 1:15 PM, John Casey <[EMAIL PROTECTED]> 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
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-27 Thread Henrique Prange 

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

2008-08-27 Thread Henrique Prange 

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

2008-08-26 Thread John Casey 

Great to hear. Thanks for checking.

-john

Peter Horlock wrote:

Well, my issue concerning the compiler seems to have been solved with RC11 -
the entire build is working now.
Maybe it had something to do with the fact that I am setting the compiler
version by using a property:

maven-compiler-plugin

${javaVersion}
${javaVersion}



Cheers,

Peter

2008/8/25 John Casey <[EMAIL PROTECTED]>


Well, looks like I lost track of a few issues that came up with RC10. I'll
work on addressing those issues, and probably follow up with an RC12 if we
find bugs.

-john


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



--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-26 Thread Daniel Kulp 


RC11 is looking pretty good to me.   I've built several things with it, 
re-setup my eclipse workspaces from fresh checkouts (eclipse:eclipse), etc...   
Haven't done a deploy yet (that's next), but everything else is looking 
pretty good to me.

Performance is also excellent.   My test case that used to take 32 seconds now 
takes about 24 second.   Other similar actions are showing similar gains.  

Dan


On Monday 25 August 2008 4:15:32 pm 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



-- 
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-26 Thread Peter Horlock 
Well, my issue concerning the compiler seems to have been solved with RC11 -
the entire build is working now.
Maybe it had something to do with the fact that I am setting the compiler
version by using a property:

maven-compiler-plugin

${javaVersion}
${javaVersion}



Cheers,

Peter

2008/8/25 John Casey <[EMAIL PROTECTED]>

> Well, looks like I lost track of a few issues that came up with RC10. I'll
> work on addressing those issues, and probably follow up with an RC12 if we
> find bugs.
>
> -john
>
>
> 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
>>
>>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [PLEASE TEST] Maven 2.0.10-RC11

2008-08-25 Thread John Casey 
Well, looks like I lost track of a few issues that came up with RC10. 
I'll work on addressing those issues, and probably follow up with an 
RC12 if we find bugs.


-john

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



--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[PLEASE TEST] Maven 2.0.10-RC11

2008-08-25 Thread John Casey 

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

--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]