Can the toolchain.xml file contain Maven properties including references
to system environment variables using ${env.VARIABLE}?  My company is
using several versions of Websphere and I was wondering if I could have
something like:

<?xml version="1.0" encoding="UTF8"?>
<toolchains>
  <!-- JDK toolchains -->
  <toolchain>
    <type>jdk</type>
    <provides>
      <version>1.5</version>
      <vendor>ibm</vendor>
    </provides>
    <configuration>
      <jdkHome>${env.WAS_HOME}/java</jdkHome>
    </configuration>
  </toolchain>
  <toolchain>
    <type>jdk</type>
    <provides>
      <version>1.6</version>
      <vendor>IBM</vendor>
    </provides>
    <configuration>
      <jdkHome>${env.WAS_HOME}</jdkHome>
    </configuration>
  </toolchain>
  <toolchain>
    <type>jdk</type>
    <provides>
      <version>1.7</version>
      <vendor>IBM</vendor>
    </provides>
    <configuration>
      <jdkHome>${env.WAS_HOME}</jdkHome>
    </configuration>
  </toolchain>
</toolchains>

Also, does it fail if the toolchain plugin is specified but the
toolchain.xml file is missing? 

I think that the toolchain plugin documentation should specify that the
toolchain.xml file belongs in the$user.home/.m2 directory, as it only
mentions this in the guide to using toolchains.

On 11/14/14 18:55, Hervé Boutemy wrote:
> The Maven team is pleased to announce the release of the Apache Maven 
> Toolchains Plugin, version 1.1
>
> The Toolchains Plugins allows to share configuration across plugins. For 
> example to make sure the plugins like compiler, surefire, javadoc, webstart 
> etc. all use the same JDK for execution.
>
> http://maven.apache.org/plugins/maven-toolchains-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-toolchains-plugin</artifactId>
>   <version>1.1</version>
> </plugin>
>
>
> Release Notes - Apache Maven Toolchains Plugin - Version 1.1
>
> Bug
> * [MTOOLCHAINS-6] Cannot create custom toolchain type
>
> Improvement
> * [MTOOLCHAINS-11] Double check toolchain type to protect against core bug 
> MNG-5716
> * [MTOOLCHAINS-10] Improve plugin output
> * [MTOOLCHAINS-1] Document how to create new toolchains
>
> Task
> * [MTOOLCHAINS-9] Upgrade to Maven 2.2.1 compatiblity
> * [MTOOLCHAINS-8] improve code and javadoc
> * [MTOOLCHAINS-7] add an IT to check that the plugin works as expected
> * [MTOOLCHAINS-4] use maven-plugin-tools' java 5 annotations
>
>
> Enjoy,
>
> -The Maven team
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to