ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Pfeiffer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IVYDE-326) Support for variables in the retrieve pattern
Date Thu, 01 Nov 2012 14:27:13 GMT

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

Carsten Pfeiffer updated IVYDE-326:
-----------------------------------

    Description: 
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.

  was:
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
${env_var:SOME_HOME}/lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]

Doing this relative to the project e.g. with ../../../lib/[organisation]/[artifact]-[revision](-[classifier]).[ext]
would be too fragile as it would break as soon as a project is moved in the directory hierarchy.

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

Mime
View raw message