You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2014/04/27 14:15:10 UTC
[jira] (MPLUGIN-238) HelpMojo phases fails when using
java-annotations
[ https://jira.codehaus.org/browse/MPLUGIN-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345412#comment-345412 ]
Herve Boutemy commented on MPLUGIN-238:
---------------------------------------
this is known and documented http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html
do you have an idea on how to make things more clear?
> HelpMojo phases fails when using java-annotations
> -------------------------------------------------
>
> Key: MPLUGIN-238
> URL: https://jira.codehaus.org/browse/MPLUGIN-238
> Project: Maven Plugin Tools
> Issue Type: Bug
> Affects Versions: 3.2
> Reporter: Daniel Godfrey
> Priority: Minor
> Attachments: test-maven-plugin.zip
>
>
> When using the java-annotations to specify the mojo metadata, the HelpMojo generating goal fails if {code:java} <skipErrorNoDescriptorsFound>true</skipErrorNoDescriptorsFound>{code} isn't specified.
> The helpmojo goal needs to execute during generate-sources phase, otherwise the generated java file isn't compiled in the compile phase. However, when using the java-annotations, there isn't any metadata to scan at that point, it is only available after the compile phase.
> So, can the helpmojo goal only generate the helpmojo.java and not scan for any metadata. The descriptor phase already does this anyway, including generating plugin-help.xml.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)