You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 23:02:18 UTC

[jira] (MAVEN-1619) [PATCH] New tag

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

Michael Osipov closed MAVEN-1619.
---------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> [PATCH] New tag <maven:getPath>
> -------------------------------
>
>                 Key: MAVEN-1619
>                 URL: https://jira.codehaus.org/browse/MAVEN-1619
>             Project: Maven 1
>          Issue Type: New Feature
>          Components: jelly/ant integration
>            Reporter: Felipe Leme
>         Attachments: GetTag.patch, MJT5-metadata.patch
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> We have a tag that can be used to add a new path element to an existing one (<maven:addPath). That tag is great, but in some cases it's necessary to know in advance if the path that is being added is not already in the other path.
> One way would be to change the <maven:addPath> behaviour so it does not add a path that it's already there; the other way would be to create a new tag which could be used to get a path - for now, I'm providing a patch for such new tag (which could be reused in other circunstances).
> -- Felipe 
> PS: I'm assuming I don't have write access to the jelly-tags module, so the patch...



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)