You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2010/01/27 22:48:55 UTC

[jira] Updated: (MANTRUN-126) Antrun plugin should follow the more common pattern groupId:artifactId:classifier:type pattern for dependency properties.

     [ http://jira.codehaus.org/browse/MANTRUN-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated MANTRUN-126:
------------------------------

    Fix Version/s: 1.4
         Assignee: Paul Gier

> Antrun plugin should follow the more common pattern groupId:artifactId:classifier:type pattern for dependency properties.
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MANTRUN-126
>                 URL: http://jira.codehaus.org/browse/MANTRUN-126
>             Project: Maven 2.x Antrun Plugin
>          Issue Type: Improvement
>            Reporter: Paul Gier
>            Assignee: Paul Gier
>             Fix For: 1.4
>
>
> Currently Maven dependencies can be accessed in the antrun plugin using the pattern "maven.dependency.my.group.id:my.artifact.id:classifier:jar.path".  This naming scheme is too complicated, and could be improved by using the more common pattern "groupId:artifactId:classifier:type" to identify project dependencies.
> The current naming scheme should be deprecated.

-- 
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