You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Hervé Boutemy <hb...@apache.org> on 2014/11/15 01:55:38 UTC
[ANN] Apache Maven Toolchains Plugin 1.1 Released
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Apache Maven Toolchains Plugin 1.1 Released
Posted by he...@free.fr.
no, there is no feature like this: in general, toolchains configuration is static
in your case, using a variable like this makes the configuration ambiguous, since the jdk 1.6 and 1.7 point to the same location: I'm not sur it's a good idea.
But perhaps it can be useful to others.
We are working on toolchains enhancements for next Maven version [1]
Please open a Jira issue to track the feature request and discussion about doing it or not
Regards,
Hervé
[1] http://jira.codehaus.org/browse/MNG-3891
----- Mail original -----
De: "Bruce Albrecht" <br...@zuhause.org>
À: "Maven Users List" <us...@maven.apache.org>
Envoyé: Samedi 15 Novembre 2014 19:59:49
Objet: Re: [ANN] Apache Maven Toolchains Plugin 1.1 Released
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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Apache Maven Toolchains Plugin 1.1 Released
Posted by Bruce Albrecht <br...@zuhause.org>.
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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Apache Maven Toolchains Plugin 1.1 Released
Posted by Hervé BOUTEMY <he...@free.fr>.
ok, last time, I added it in the wrong location, then it was removed during
next site publication
I just added the file in the right place [1]
it won't disappear any more :)
Regards,
Hervé
[1] http://svn.apache.org/r1639847
Le vendredi 14 novembre 2014 23:33:45 tibor17 a écrit :
> The toolchain.xsd schema seems to be unaccessible according to header and
> xsd storage on maven-apache.
> http://maven.apache.org/ref/3.1.1/maven-core/toolchains.html
> http://maven.apache.org/xsd/
>
>
>
> -----
> BR, tibor17
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/ANN-Apache-Maven-Toolchains-Plugin-1-1-Rel
> eased-tp5814209p5814245.html Sent from the Maven Developers mailing list
> archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Apache Maven Toolchains Plugin 1.1 Released
Posted by tibor17 <ti...@lycos.com>.
The toolchain.xsd schema seems to be unaccessible according to header and xsd
storage on maven-apache.
http://maven.apache.org/ref/3.1.1/maven-core/toolchains.html
http://maven.apache.org/xsd/
-----
BR, tibor17
--
View this message in context: http://maven.40175.n5.nabble.com/ANN-Apache-Maven-Toolchains-Plugin-1-1-Released-tp5814209p5814245.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org