[
https://issues.apache.org/jira/browse/MTOOLCHAINS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124997#comment-16124997
]
Karl Heinz Marbaise commented on MTOOLCHAINS-18:
------------------------------------------------
Maybe I misunderstand a thing but if you use an environment variable why not
using {{JAVA_HOME}} ? Otherwise from my point of view the usage of
{{toolchains.xml}} does not make sense?
> toolchain.xml file should support environment variables
> -------------------------------------------------------
>
> Key: MTOOLCHAINS-18
> URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-18
> Project: Maven Toolchains Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> Environment: Windows 7 64bit
> Reporter: Nicolas Radde
> Priority: Minor
>
> When the toolchain.xml file is configured as follow :
> {code:xml}
> <toolchain>
> <type>jdk</type>
> <provides>
> <version>1.8</version>
> <vendor>sun</vendor>
> </provides>
> <configuration>
> <jdkHome>${env.JDK_HOME_8}</jdkHome>
> </configuration>
> </toolchain>
> {code}
> The execution of a maven compile fail with the following error :
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-toolchains-plugin:
> 1.1:toolchain (default) on project monitoring-mq-web: Misconfigured
> toolchains.
> Non-existing JDK home configuration at
> L:\test-monitoring-mq\${env.JDK_HOME_8} -> [Help 1]
> {noformat}
> While the environment variable *JDK_HOME_8* exist.
> Using environment variable is a very convenient way to have the same
> toolchain.xml file for all developers or jenkins slaves and would be a nice
> addition to the plugin.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
