[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-222) Environment variables are not replaced when using ParsedPomFile.getProperties()
[
https://issues.jboss.org/browse/SHRINKRES-222?page=com.atlassian.jira.plu...
]
Matous Jobanek commented on SHRINKRES-222:
------------------------------------------
Hi, I guess that you are trying to resolve pom.xml file that is not in your project
directory, is it right? In this case, SWR doesn't replace the environments, that's
right - I can have a look if it is possible to implement it.
If the pom.xml file is in your project directory, I would recommend not to use the
original file, but the generated one in the {{/target}} directory. There the pom.xml files
should be generated with and the properties should be replaced.
Environment variables are not replaced when using
ParsedPomFile.getProperties()
-------------------------------------------------------------------------------
Key: SHRINKRES-222
URL: https://issues.jboss.org/browse/SHRINKRES-222
Project: ShrinkWrap Resolvers
Issue Type: Bug
Components: maven
Affects Versions: 2.1.1
Environment: Windows 7 x64
Reporter: Falko M.
In Maven you can define properties using environment variables, e.g.:
{{<someProp>$\{env.SOME_ENV\}<someProp>}}
See also:
http://books.sonatype.com/mvnref-book/reference/resource-filtering-sect-p...
On the command line, those placeholders a replaced as expected. This can be checked via
{{mvn help:effective-pom}}.
Unfortunately, {{ParsedPomFile.getProperties()}} does *not* replace those placeholders.
It returns them "as is" (e.g. {{"$\{env.SOME_ENV\}"}}).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)