]
Nick Boldt updated ERT-531:
---------------------------
Sprint: devex #141 December 2017
Maven 3.3.1 doesn't pick up the customized Toolchain for the WTP
build [EBZ#472084]
-----------------------------------------------------------------------------------
Key: ERT-531
URL:
https://issues.jboss.org/browse/ERT-531
Project: Eclipse Release Train
Issue Type: Task
Components: Community
Reporter: Friendly Jira Robot
Assignee: Nick Boldt
Priority: Critical
Labels: Hudson, bzira
A few WTP plugins need to build with the old JDK and a WTP toolchains.xml is set up. It
works fine with Maven 3.2.5 but fails with Maven 3.3.1.
The current investigation showed that instead of using the WTP specific toolchains.xml
which is defined in the Hudson build configuration, a common toolchains
/opt/public/common/maven-toolchains.xml is linked as the user toolchains.
genie.gef ~> ll ~/.m2
[....]
lrwxrwxrwx 1 genie.gef tools.gef 37 23 févr. 04:05 settings.xml ->
/opt/public/common/maven-settings.xml
lrwxrwxrwx 1 genie.gef tools.gef 39 23 févr. 04:05 toolchains.xml ->
/opt/public/common/maven-toolchains.xml
I wonder how Maven 3.2.5 can pick up the customized toolchains but not 3.3.1. It would be
great if Maven 3.3.1 can pick up the customized toolchains as 3.2.5.
At the same time, I wonder whether the common toolchains file can be changed to support
IBM JDK 1.4. Its current JDK 1.4 points to the Sun's which is broken and generates
compile errors.
<toolchain>
<type>jdk</type>
<provides>
<id>J2SE-1.4</id>
</provides>
<configuration>
<jdkHome>/shared/webtools/apps/IBMJava2-142-SR13FP10/jre</jdkHome>
</configuration>
</toolchain>