[jira] [Resolved] (IVYDE-326) Support for variables in the retrieve pattern

["Nicolas Lalevée (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IVYDE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalevée resolved IVYDE-326.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: trunk
         Assignee: Nicolas Lalevée

Patch applied in trunk. I have added some buttons to help put variables and patterns.
Thank you for your contribution.
                
> Support for variables in the retrieve pattern
> ---------------------------------------------
>
>                 Key: IVYDE-326
>                 URL: https://issues.apache.org/jira/browse/IVYDE-326
>             Project: IvyDE
>          Issue Type: Wish
>          Components: classpath container
>    Affects Versions: 2.2.0.beta1
>            Reporter: Carsten Pfeiffer
>            Assignee: Nicolas Lalevée
>              Labels: patch
>             Fix For: trunk
>
>         Attachments: retrievePattern-variable-substitution.patch
>
>
> The retrieve pattern for the classpath container appears to be strictly relative to the project.
> In Ivy/ant, it is possible to specify something like 
> {code}
> ${some.dir}/lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
> {code}
> We would like to use the same in IvyDE, e.g. utilizing Eclipse variable substitution mechanism so that you could use
> {code}
> ${env_var:SOME_HOME}/lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
> {code}
> Doing this relative to the project e.g. with 
> {code}
> ../../../lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
> {code}
> would be too fragile as it would break as soon as a project is moved in the directory hierarchy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira