I have switched Jenkins on ares to use Maven 3.3.9.
I also switched the GeoServer nightly builds to use Maven 3.3.9 for deplay (a hardcoded path in the script) and change the nightlies to use the workspace of their respective main builds (all were using using geoserver-master).
I have kicked the GeoServer nightly builds.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
Switching builds was more fiddly than expected because Maven versions were explicitly selected. I had to select maven-3.3.9 in all the dropdowns in all the builds. I have done this for all GeoTools and GeoServer builds. I have not yet looked at the release scripts.
Kind regards,
Ben.
On 28/03/16 10:00, Ben Caradoc-Davies wrote:
I have switched Jenkins on ares to use Maven 3.3.9.
I also switched the GeoServer nightly builds to use Maven 3.3.9 for
deplay (a hardcoded path in the script) and change the nightlies to use
the workspace of their respective main builds (all were using using
geoserver-master).I have kicked the GeoServer nightly builds.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
I set a Jenkins global environment variable M2_HOME of /opt/apache-maven-3.3.9 and added $M2_HOME/bin to PATH in all the (working = non-jira) release job scripts. This should override the Maven 3.0.4 in the system-level PATH on ares and cause the release job scripts to run Maven 3.3.9. Please let me know if you see any release job failures.
On 28/03/16 10:29, Ben Caradoc-Davies wrote:
I have not yet looked at the release scripts.
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand