[
https://issues.jboss.org/browse/JBIDE-25300?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-25300:
---------------------------------------
There was a followup ticket for maven installation on the nfs share:
https://redhat.service-now.com/surl.do?n=PNT0093635
That was done and verified a few weeks ago.
So maven3-latest in both Jenkins config (when you use a maven build step) and the nfs
share now point to maven 3.5.2.
So I guess now it's up to you, [~nickboldt], to make sure the jobs are updated to use
this and check that it actually works.
update jobs to use maven 3.5
----------------------------
Key: JBIDE-25300
URL:
https://issues.jboss.org/browse/JBIDE-25300
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.5.2.AM2
Jobs currently use mvn 3.3.9, unless pointed as "mvn3-latest", which was
recently updated to be a symlink to 3.5.0 instead of 3.3.9.
We should get 3.5.2 [1] installed and use that in the jobs as it supports JDK 9.
[1]
https://maven.apache.org/docs/3.5.2/release-notes.html
cc: [~psrna] [~mmalina]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)