Fixed, and in case you come across this in other situations:
maven-plugin-javadoc now ignores
Instead, there is .
This does not seem to be mentioned anywhere, at least I could not find
except buried deep inside JIRA.
https://issues.apache.org/jira/browse/MJAVADOC-511
I don't understand
Done, Elephas has an override for surefire (see other email).
The build-java9 job has been re-activated and set to run once a day.
It runs "mvn clean verify -Pdev" (no javadoc).
Elsewhere, the normal development build test is unhappy about javadoc in
jena-iri (no source changes). But it is
Nope, not using anything from Java 9, myself.
But I haven't looked that carefully at library changes. (I am looking forward
to private members on interfaces.) I don't personally know anyone using Jigsaw
(the new module system), and to my (low level of) understanding, it isn't
really meant for
Works for me. I think it's good to take as many steps as we can to do this (=
make each one as small as we can).
ajs6f
> On Feb 6, 2018, at 8:00 AM, Andy Seaborne wrote:
>
> Would there be any problems if the plugin settings for a building wither
> Java9 were put into
Would there be any problems if the plugin settings for a building wither
Java9 were put into master? (not building _for_ java9).
One thing needed is a minimum version of maven of 3.5.0 (3.5.2 is the
current latest).
If that's OK, the Jenkins job can be activated to build for java8 with
I'm not sure how that helps:
[INFO] org.apache.jena:jena-elephas-common:jar:3.7.0-SNAPSHOT
[INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.0:provided
[INFO] | +- org.apache.hadoop:hadoop-annotations:jar:2.7.0:provided
[INFO] | | \- jdk.tools:jdk.tools:jar:1.8:system
It still depends on a
It may be worth bumping the default HDFS version to 2.7.0 as that is the most
prevalent in the popular distributions currently
Rob
On 02/02/2018, 18:03, "Andy Seaborne" wrote:
JENA-1475
I've managed to the build working with java9, outputting java8
Well, I read about this some time ago and was wondering how many people
are really aware of the fact that no more security updates will be
delivered 6 month after the release of a new version. Most people in our
group are still working on Java 8, if not necessary probably nobody here
will upgrade
Ditto (haven't been paying much attention).
A six month cycle is pretty fast, in some ways. At least it will be if we have
to do a lot of work for each version.
ajs6f
> On Feb 5, 2018, at 11:34 AM, Andy Seaborne wrote:
>
> I hadn't grok'ed (or, to be honest, paid attention
I hadn't grok'ed (or, to be honest, paid attention to) the details:
http://blog.joda.org/2018/02/java-9-has-six-weeks-to-live.html
Java 8 LTS -> Java 11 LTS (Sep 2018)
then only four months until end of LTS for Java8.
Andy
On 02/02/18 18:02, Andy Seaborne wrote:
2/Full build, jaavdoc
javadoc fails at jena-core (despite it compiled). The problem is
java.xml.bind - it looks to me like the javadoc is running in "java9"
mode and I haven't found out how to override that.
java.xml.bind is not an available module
Thanks for finding that out. Some trickery to get a java8 tools.jar
available might work but would be awfully unstable, needing path names.
Andy
Warning - switching build for java9, not just build with java9 for
java8, crashed Eclipse for me in such a way I had to delete the
workspace
The Hadoop libs, even the latest major release version 3.0.0, are still
based on Java 7 resp. Java 8, see [1]
Thus, it could be a blocker.
Cheers,
Lorenz
[1]
http://central.maven.org/maven2/org/apache/hadoop/hadoop-annotations/3.0.0/hadoop-annotations-3.0.0.pom
On 02.02.2018 19:02, Andy
13 matches
Mail list logo