[
https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu...
]
Thomas SEGISMONT edited comment on SHRINKRES-105 at 1/21/13 5:03 AM:
---------------------------------------------------------------------
In SHRINKRES-42, the fix makes possible to resolve variables if the user specifies a
particular settings file. But for default settings XML file, the Maven
{code:java}SettingsBuildingRequest{code} is built in
{code:java}org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder{code}
not in {code:java}org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl{code}
was (Author: tsegismont):
In SHRINKRES-42, the fix makes possible to resolve variables if the user specifies a
particular settings file. But for default settings XML file, the Maven
{code:java}SettingsBuildingRequest{code} is built in
{code:java}org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder{code}
not {code:java}org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl{code}
Support resolution of variables in Maven settings file
------------------------------------------------------
Key: SHRINKRES-105
URL:
https://issues.jboss.org/browse/SHRINKRES-105
Project: ShrinkWrap Resolvers
Issue Type: Enhancement
Components: impl-maven
Affects Versions: 1.0.0-beta-7
Reporter: Thomas SEGISMONT
Assignee: Karel Piwko
Labels: maven, resolver
Variables in Maven settings file are not resolved.
For instance if you have this node in your settings :
{code:xml}
<localRepository>${user.home}/.m2/repository</localRepository>
{code}
then Shrinkwrap will create a _$\{user.home\}/.m2/repository_ in the project directory
and use it as local repository.
--
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