On 11 Mar 2013, at 21:28, Thomas Koch wrote:
> Stuart McCulloch:
>> Perhaps you could post a link to your re-packaging build so people can
>> recreate the issue? There's not enough information here to debug the
>> problem remotely.
>
> http://anonscm.debian.org/gitweb/?p=pkg-java/maven-plugin-
>
Stuart McCulloch:
> Perhaps you could post a link to your re-packaging build so people can
> recreate the issue? There's not enough information here to debug the
> problem remotely.
http://anonscm.debian.org/gitweb/?p=pkg-java/maven-plugin-
tools.git;a=tree;hb=refs/heads/update_to_3.2
The build w
On 8 Mar 2013, at 16:54, Thomas Koch wrote:
> Thomas Koch:
>> [DEBUG] Using 0 mojo extractors.
>
> I could track down the problem. The field "mojoDescriptorExtractors" in the
> DefaultMojoScanner class is not filed by plexus with the available extractors
> although they should be available on
Martin Gainty:
> Thomas
>
> I can see public DefaultMojoScanner( Map
> extractors ) in maven-plugin-tools-api v3.2
> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.maven.plugin-to
> ols/maven-plugin-tools-api/3.2/org/apache/maven/tools/plugin/scanner/Defaul
> tMojoScanner.java#Defaul
: No mojo definitions were found for plugin
> Date: Fri, 8 Mar 2013 17:54:27 +0100
>
> Thomas Koch:
> > [DEBUG] Using 0 mojo extractors.
>
> I could track down the problem. The field "mojoDescriptorExtractors" in the
> DefaultMojoScanner class is not fi
Thomas Koch:
> [DEBUG] Using 0 mojo extractors.
I could track down the problem. The field "mojoDescriptorExtractors" in the
DefaultMojoScanner class is not filed by plexus with the available extractors
although they should be available on the classpath.
Now I don't know how to debug this issue
ing plugin descriptor: 'No mojo definitions were found for
plugin: org.apache.maven.plugins:maven-plugin-plugin.'
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error extracting
plugin
