[
https://issues.apache.org/jira/browse/MPLUGIN-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527357#comment-15527357
]
Guillaume Boué commented on MPLUGIN-314:
----------------------------------------
Thanks for the report. I reproduced the issue and tracked this down to a bug
inside the qdox library, that the plugin uses to parse the Java sources and
generate the report. I made a bug report here:
https://github.com/paul-hammant/qdox/issues/13.
Waiting for feedback, the work-arounds are to remove the import (which is
actually unused), or don't use the fully qualified class name for the field's
type.
> invalid requirement role generated in plugin.xml
> ------------------------------------------------
>
> Key: MPLUGIN-314
> URL: https://issues.apache.org/jira/browse/MPLUGIN-314
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
> Affects Versions: 3.4, 3.5
> Reporter: Jimmy Praet
> Attachments: plugin-bug.zip
>
>
> I ran into this issue when attempting to build a fork of the
> versions-maven-plugin:
> In the plugin.xml the following is generated:
> {code:xml}
> <requirements>
> <requirement>
> <role>org$apache$maven$artifact$resolver$ArtifactResolver</role>
> <field-name>resolver</field-name>
> </requirement>
> </requirements>
> {code}
> The $ should be dots.
> This only seems to happen when your field is declared with a fully qualified
> classname, and the class is also imported. If I remove the import or the
> fully qualified classname, the problem disappears.
> {code:java}
> package plugin.bug;
> import org.apache.maven.plugin.AbstractMojo;
> import org.apache.maven.plugin.MojoExecutionException;
> import org.apache.maven.plugin.MojoFailureException;
> import org.apache.maven.artifact.resolver.ArtifactResolver;
> /**
> * @goal foo
> */
> public class FooMojo extends AbstractMojo {
> /**
> * @component
> */
> private org.apache.maven.artifact.resolver.ArtifactResolver resolver;
> public void execute() throws MojoExecutionException,
> MojoFailureException {
> }
> }
> {code}
> It works in version 3.3.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
