[
http://jira.codehaus.org/browse/MPLUGIN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190798#action_190798
]
Benjamin Bentmann commented on MPLUGIN-160:
-------------------------------------------
Could you provide a minimal example project that
a) allows us to reproduce the issue and
b) serves us as basis to create an integration test
?
> PluginDescriptorGenerator doesn't generate component requirements for
> MojoDescriptor.getRequirements()
> ------------------------------------------------------------------------------------------------------
>
> Key: MPLUGIN-160
> URL: http://jira.codehaus.org/browse/MPLUGIN-160
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: API
> Affects Versions: 2.5
> Reporter: Stefan Grinsted
> Priority: Minor
> Attachments: patch.txt
>
>
> The part that generates the <requirements> section for a mojo in
> PluginDescriptorGenerator, only includes requirements for components, if they
> are specified via a parameter with expression=${component.*}, not if it is
> actually specified as a required component using the <components> element.
> I have created a patch, which includes the ComponentRequirements as
> requirements when generating the <requirements> element.
> Until released, the following workaround can be used in the module.mojos.xml,
> to get the required component in the plugin.xml:
> <parameter>
> <name>workaroundForPathTransformer</name>
> <required>true</required>
>
> <expression>${component.org.apache.maven.project.path.PathTranslator}</expression>
> <type>org.apache.maven.project.path.PathTranslator</type>
> <description>This is a workaround to get the PathTransformer as a
> Requirement in the plugin.xml.</description>
> </parameter>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
