version of Maven required to build Java development branches

[Ian Young]

If you build our Java development (master) branches from source, be advised that in the interests of build consistency we will be adding an enforcement rule to ensure that the version of Maven used is at least 3.5.3. This change will be made on Friday this week (2019-03-22).

If your development environment includes a version of Maven older than 3.5.3 (released a little more than a year ago on 2018-03-08) then you will need to update in order to continue building the following projects:

	java-parent-project 11
	java-support 8
	spring-extensions 6
	java-opensaml 4
	java-identity-provider 4
	java-metadata-aggregator 0.10

Note that this applies to any "mvn" you invoke from the command line, as well as anything called from an IDE. The version of Maven bundled with current versions of Eclipse, for example, is 3.5.3 (although it is possible to configure it to use an external Maven installation instead of the embedded one).

We expect to move the ball forwards on this front on a regular basis in the future, with the current 3.6.0 becoming our requirement within a few months. We probably won't make announcements about such incremental changes, but felt that the number of years we're moving forwards with this particular change (our previous requirement was 3.3.1, from 2015) warranted a mention.

    -- Ian




-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3870 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/dev/attachments/20190318/223d208f/attachment.p7s>