The release process ocumentation says "You must use maven3. Ideally, the
latest maven release." so puttingin a test for that seemed like a good idea.
IIRC early 3.x weren't reliable for me; 3.3 is over a year old. 3.3.5
is "known to work" and buig fixes on 3.3 (I'm using 3.3.9 which is over
a year old)
As for fixes, its the plugins and keeping versions in step.
Andy
On 06/12/16 09:57, Rob Vesse wrote:
Was 3.3.5 chosen for a particular reason? Is there a fix/feature that we rely
on that needs that as a minimum?
On 05/12/2016 22:24, "[email protected]" <[email protected]> wrote:
prerequisites.maven
Project: http://git-wip-us.apache.org/repos/asf/jena/repo
Commit: http://git-wip-us.apache.org/repos/asf/jena/commit/90855b83
Tree: http://git-wip-us.apache.org/repos/asf/jena/tree/90855b83
Diff: http://git-wip-us.apache.org/repos/asf/jena/diff/90855b83
Branch: refs/heads/master
Commit: 90855b8395a761b5d8c775787c3b8853ff25b343
Parents: 2546889
Author: Andy Seaborne <[email protected]>
Authored: Mon Dec 5 22:23:26 2016 +0000
Committer: Andy Seaborne <[email protected]>
Committed: Mon Dec 5 22:23:26 2016 +0000
----------------------------------------------------------------------
pom.xml | 4 ++++
1 file changed, 4 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/jena/blob/90855b83/pom.xml
----------------------------------------------------------------------
diff --git a/pom.xml b/pom.xml
index 8c0c22f..932fee3 100644
--- a/pom.xml
+++ b/pom.xml
@@ -33,6 +33,10 @@
<version>18</version>
</parent>
+ <prerequisites>
+ <maven>3.3.5</maven>
+ </prerequisites>
+
<licenses>
<license>
<name>The Apache Software License, Version 2.0</name>
