<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
On 02/01/2016 20:32, John Patrick wrote:<br>
<blockquote
cite="mid:CAH9u10nkXdvdWBkpoqia8VeLEZW-OEsUnP=NOtNEUwje2rUcRw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>evening,<br>
<br>
</div>
Does anyone know how to override the java.version
field?<br>
<br>
</div>
<div><span class=""><span></span></span>Wanting to help
out with getting JDK 9 ready, using it and building
projects with it.<br>
<br>
Most patches I've submitted so far as simply bumping
which is the min java version being used from 1.5 to
1.6.<br>
<br>
</div>
<div>One issue that I can't figure a work around for
java.version. I'm getting the following error from
maven-javadoc-plugin.<br>
<br>
<span class=""><span>[WARNING] Unable to find the
javadoc version: Unrecognized version of Javadoc:
'java version "9-ea"<br>
Java(TM) SE Runtime Environment (build 9-ea+<a
moz-do-not-send="true"
href="http://99-2015-12-23-184955.javare.4146.nc">99-2015-12-23-184955.javare.4146.nc</a>)<br>
Java HotSpot(TM) 64-Bit Server VM (build 9-ea+<a
moz-do-not-send="true"
href="http://99-2015-12-23-184955.javare.4146.nc">99-2015-12-23-184955.javare.4146.nc</a>,
mixed mode)<br>
' near index 37<br>
(?s).*?([0-9]+\.[0-9]+)(\.([0-9]+))?.*<br>
^<br>
[WARNING] Using the Java the version instead of,
i.e. 0.0<br>
[WARNING] -quiet option is not supported on Java
version < 1.4. Ignore this option.<br>
<br>
<br>
</span></span></div>
<div><span class=""><span>My question is should maven
and every other project accept 9-ea as a valid
java.version string, or could build 100 plus tweak
the java.version string to something else that is
considered valid.<br>
</span></span></div>
<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
In a recent mail to jigsaw-dev [1], Robert Scholte mentioned that
the new version-string scheme may be problematic for some Maven
plugins. He mentions the plexus-archiver specifically and that seems
to have a patch already. If the maven-javadoc-plugin needs updates
too then it's best to get a bug submitted so that it's on someone's
radar.<br>
<br>
-Alan<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-December/005885.html">http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-December/005885.html</a><br>
</body>
</html>