You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2011/08/12 19:27:42 UTC

[jira] Updated: (ARCHETYPE-378) Remove the parameter goalPrefix (and corresponding code) from the archetype:add-archetype-metadata mojo

     [ https://jira.codehaus.org/browse/ARCHETYPE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated ARCHETYPE-378:
-----------------------------------

    Fix Version/s: 2.1
         Assignee: Olivier Lamy

> Remove the parameter goalPrefix (and corresponding code) from the archetype:add-archetype-metadata mojo
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ARCHETYPE-378
>                 URL: https://jira.codehaus.org/browse/ARCHETYPE-378
>             Project: Maven Archetype
>          Issue Type: Task
>          Components: Plugin
>    Affects Versions: 2.0
>            Reporter: Benjamin Bentmann
>            Assignee: Olivier Lamy
>            Priority: Trivial
>             Fix For: 2.1
>
>
> As questioned in [Archtypes and plugin prefix|http://www.mail-archive.com/dev@maven.apache.org/msg89617.html], it appears the parameter {{goalName}} of the {{add-archetype-metadata}} mojo exists merely due to copy&paste but has no real use in the context of archetypes. As such the parameter and its backing code should be removed to reduce confusion for end users and to keep the group-level metadata free from bogus plugin prefix mappings for archetypes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira