ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Guenther (Commented) (JIRA)" <>
Subject [jira] [Commented] (IVY-1319) environment variables are not expanded for local maven repo settings
Date Mon, 07 Nov 2011 19:44:51 GMT


Marc Guenther commented on IVY-1319:

Sorry, but I don't see how this would help me with my problem.

The maven setting is global for all jobs running on the slave. But that ivy setting you are
talking about seems to be project specific. At least from reading the docs I have found no
way to use a global ivysettings.xml file, like ~/.ivy2/ivysettings.xml. And changing dozens
of projects is not really an option, and I have no control over that anyway.

I have tried to put this:
    <properties environment="env"/>
into the files:

but it didn't help. Did I miss something?

> environment variables are not expanded for local maven repo settings
> --------------------------------------------------------------------
>                 Key: IVY-1319
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.2.0
>            Reporter: Marc Guenther
>            Assignee: Maarten Coene
>            Priority: Minor
> On my Jenkins slave, I have this setting in my {{~/.m2/settings.xml}}:
> {{<localRepository>$\{env.WORKSPACE}/.repository</localRepository>}}
> The {{env.WORKSPACE}} is set by Jenkins.
> When running Grails from within a build, Ivy complains with the following error:
> {quote}java.lang.IllegalArgumentException: ivy pattern must be absolute: $\{env.WORKSPACE}/.repository/[organisation]/[module]/[revision]/[module]-[revision](-[classifier]).pom
> {quote}
> It seems the environment variable is not expanded.
> Unfortunately it is not possible to tell grails to ignore the local maven repo:
> So this effectively blocks me from using that Maven setting at all.
> I have filed a similar report for Grails:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message