[
https://issues.apache.org/jira/browse/IVY-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145732#comment-13145732
]
Marc Guenther edited comment on IVY-1319 at 11/7/11 7:50 PM:
-------------------------------------------------------------
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:
{code}<ivysettings>
<properties environment="env"/>
</ivysettings>{code}
into the files:
{{~/.ivy2/ivysettings.properties}}
and
{{~/.ivy2/ivysettings.xml}}
but it didn't help. Did I miss something?
EDIT:
Maybe this is more an issue of the grails-maven-plugin? At least that is the
one picking up that value and feeding it into Ivy. It should probably also tell
it how to resolve {{env.}} variables?
was (Author: marc.guenther):
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:
{code}<ivysettings>
<properties environment="env"/>
</ivysettings>{code}
into the files:
{{~/.ivy2/ivysettings.properties}}
and
{{~/.ivy2/ivysettings.xml}}
but it didn't help. Did I miss something?
> environment variables are not expanded for local maven repo settings
> --------------------------------------------------------------------
>
> Key: IVY-1319
> URL: https://issues.apache.org/jira/browse/IVY-1319
> 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:
> http://jira.grails.org/browse/MAVEN-18
> So this effectively blocks me from using that Maven setting at all.
> I have filed a similar report for Grails:
> http://jira.grails.org/browse/MAVEN-160
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
