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/>
<
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]
