You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Julien Stern <ju...@cryptolog.com> on 2008/10/14 10:45:36 UTC
Strange Maven error...
Hi list,
on a few development machines (but not all), we are starting to see the
error below. It seems that it happens mostly to "new" developpers, e.g.
those starting with an empty ${HOME}/.m2 directory.
The error happens with 2.0.7, 2.0.8 and 2.0.9.
If anyone has an hint on where to look at, that would be appreciated.
Thanks.
--
Julien
Error:
[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar': Unable to find
the mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the
plugin 'org.apache.maven.plugins:maven-javadoc-plugin'
Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-javadoc-plugin:2.3:jar.
Stack Trace:
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
in the plugin manager executing goal
'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar': Unable to find
the mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the
plugin 'org.apache.maven.plugins:maven-javadoc-plugin'
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
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:597)
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.PluginManagerException: Unable to
find the mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in
the plugin 'org.apache.maven.plugins:maven-javadoc-plugin'
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:575)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:425)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-javadoc-plugin:2.3:jar.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:312)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:566)
... 18 more
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Strange Maven error... [Semi-solved]
Posted by Julien Stern <ju...@cryptolog.com>.
We believe we have found the source of the issue (altough we no dot
fully understand why it happens and when).
The source of the issue is probably one of our (homemade) plugin which
_depends_ (in the dependency sense) on maven-javadoc-plugin 2.3.
What I assume is happening is that in some configurations, a more recent
version of the maven-javadoc-plugin is used, and that somehow when our
plugin attemps to find the 2.3 version, it cannot because both are in
the same classloader (well, something like that). This is why we saw
seemingly inconsistent results depending on the version of the plugin
that was used (or even possibly depending on the order, as I believe the
first plugin that is loaded sets the version for the whole build).
Does that make any sense ? :)
If that is so, we will attempt to simply remove the dependency (at the
price of a minor code duplication) to solve the issue.
--
Julien
Julien Stern wrote:
> Brett Porter wrote:
>> This is usually because of a bad POM or other corrupted download. Are you
>> all using a repository manager that might have an incorrect version of
>> the
>> javadoc plugin?
>
> It does not appear so.
> I checked the maven-javadoc-plugin in my local repo (which works) with
> the maven-javadoc-plugin in our central repo (archiva) and they are the
> same.
>
> Actually, I have to slightly correct what I said before: on my machine,
> it works with Maven 2.0.7, but fails with 2.0.8, 2.0.9 and 2.10-M1.
>
> On an other machine (same central repo), it works with 2.0.7 and 2.0.8
> but fails with 2.0.9 and 2.10-M1...
>
> Really weird...
>
> --
> Julien
>
>> 2008/10/14 Julien Stern <ju...@cryptolog.com>
>>
>>> Hi list,
>>>
>>> on a few development machines (but not all), we are starting to see the
>>> error below. It seems that it happens mostly to "new" developpers, e.g.
>>> those starting with an empty ${HOME}/.m2 directory.
>>>
>>> The error happens with 2.0.7, 2.0.8 and 2.0.9.
>>>
>>> If anyone has an hint on where to look at, that would be appreciated.
>>>
>>> Thanks.
>>>
>>> --
>>> Julien
>>>
>>> Error:
>>>
>>> [INFO] Internal error in the plugin manager executing goal
>>> 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar': Unable to
>>> find the
>>> mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the
>>> plugin
>>> 'org.apache.maven.plugins:maven-javadoc-plugin'
>>> Component descriptor cannot be found in the component repository:
>>> org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-javadoc-plugin:2.3:jar.
>>>
>>>
>>> Stack Trace:
>>>
>>> [DEBUG] Trace
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Internal
>>> error in
>>> the plugin manager executing goal
>>> 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar': Unable to
>>> find the
>>> mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the
>>> plugin
>>> 'org.apache.maven.plugins:maven-javadoc-plugin'
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543)
>>>
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
>>>
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
>>>
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>>>
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>>>
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>>>
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
>>> 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:597)
>>> 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.PluginManagerException: Unable to
>>> find
>>> the mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the
>>> plugin 'org.apache.maven.plugins:maven-javadoc-plugin'
>>> at
>>> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:575)
>>>
>>> at
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:425)
>>>
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>>>
>>> ... 16 more
>>> Caused by:
>>> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
>>>
>>> Component descriptor cannot be found in the component repository:
>>> org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-javadoc-plugin:2.3:jar.
>>>
>>> at
>>> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
>>>
>>> at
>>> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:312)
>>>
>>> at
>>> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
>>>
>>> at
>>> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:566)
>>>
>>> ... 18 more
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Strange Maven error...
Posted by Julien Stern <ju...@cryptolog.com>.
Brett Porter wrote:
> This is usually because of a bad POM or other corrupted download. Are you
> all using a repository manager that might have an incorrect version of the
> javadoc plugin?
It does not appear so.
I checked the maven-javadoc-plugin in my local repo (which works) with
the maven-javadoc-plugin in our central repo (archiva) and they are the
same.
Actually, I have to slightly correct what I said before: on my machine,
it works with Maven 2.0.7, but fails with 2.0.8, 2.0.9 and 2.10-M1.
On an other machine (same central repo), it works with 2.0.7 and 2.0.8
but fails with 2.0.9 and 2.10-M1...
Really weird...
--
Julien
> 2008/10/14 Julien Stern <ju...@cryptolog.com>
>
>> Hi list,
>>
>> on a few development machines (but not all), we are starting to see the
>> error below. It seems that it happens mostly to "new" developpers, e.g.
>> those starting with an empty ${HOME}/.m2 directory.
>>
>> The error happens with 2.0.7, 2.0.8 and 2.0.9.
>>
>> If anyone has an hint on where to look at, that would be appreciated.
>>
>> Thanks.
>>
>> --
>> Julien
>>
>> Error:
>>
>> [INFO] Internal error in the plugin manager executing goal
>> 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar': Unable to find the
>> mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the plugin
>> 'org.apache.maven.plugins:maven-javadoc-plugin'
>> Component descriptor cannot be found in the component repository:
>> org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-javadoc-plugin:2.3:jar.
>>
>> Stack Trace:
>>
>> [DEBUG] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in
>> the plugin manager executing goal
>> 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar': Unable to find the
>> mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the plugin
>> 'org.apache.maven.plugins:maven-javadoc-plugin'
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
>> 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:597)
>> 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.PluginManagerException: Unable to find
>> the mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the
>> plugin 'org.apache.maven.plugins:maven-javadoc-plugin'
>> at
>> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:575)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:425)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>> ... 16 more
>> Caused by:
>> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
>> Component descriptor cannot be found in the component repository:
>> org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-javadoc-plugin:2.3:jar.
>> at
>> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
>> at
>> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:312)
>> at
>> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:566)
>> ... 18 more
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Strange Maven error...
Posted by Brett Porter <br...@apache.org>.
This is usually because of a bad POM or other corrupted download. Are you
all using a repository manager that might have an incorrect version of the
javadoc plugin?
2008/10/14 Julien Stern <ju...@cryptolog.com>
> Hi list,
>
> on a few development machines (but not all), we are starting to see the
> error below. It seems that it happens mostly to "new" developpers, e.g.
> those starting with an empty ${HOME}/.m2 directory.
>
> The error happens with 2.0.7, 2.0.8 and 2.0.9.
>
> If anyone has an hint on where to look at, that would be appreciated.
>
> Thanks.
>
> --
> Julien
>
> Error:
>
> [INFO] Internal error in the plugin manager executing goal
> 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar': Unable to find the
> mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the plugin
> 'org.apache.maven.plugins:maven-javadoc-plugin'
> Component descriptor cannot be found in the component repository:
> org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-javadoc-plugin:2.3:jar.
>
> Stack Trace:
>
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in
> the plugin manager executing goal
> 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar': Unable to find the
> mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the plugin
> 'org.apache.maven.plugins:maven-javadoc-plugin'
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> 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:597)
> 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.PluginManagerException: Unable to find
> the mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.3:jar' in the
> plugin 'org.apache.maven.plugins:maven-javadoc-plugin'
> at
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:575)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:425)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by:
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Component descriptor cannot be found in the component repository:
> org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-javadoc-plugin:2.3:jar.
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:312)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
> at
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:566)
> ... 18 more
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Brett Porter
http://blogs.exist.com/bporter/