[
https://issues.jboss.org/browse/SHRINKRES-222?page=com.atlassian.jira.plu...
]
Falko M. updated SHRINKRES-222:
-------------------------------
Description:
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\}}"}).
was:
In Maven you can define properties using environment variables, e.g.:
{{<someProp>$\{env.SOME_ENV\}<someProp>}}
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\}}"}).
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)