You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2019/04/25 13:07:10 UTC
The state of jena+Java11
With the elephas change, I tried to build with java11 (producing java8
byte code).
We seem to be blocked by not being able to produce javadoc.
The error is for each module:
"""
The code being documented uses modules but the packages defined in
https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module.
"""
The block is:
https://bugs.openjdk.java.net/browse/JDK-8212233
and I haven't found a workaround that works. (I am using Ubuntu dist
java, 11.0.3 which is claimed to have a backport of the fix).
Anyone know anything about this?
Andy
Re: The state of jena+Java11
Posted by Andy Seaborne <an...@apache.org>.
It works for me locally; thanks Aaron.
The JDK11 job on Jenkins is currently failing for reasons that look
unrelated.
For jdk.version=11 it needs to be removed.
Andy
State of "jdk.version=11"
1/ "mvn clean install -Dmaven.javadoc.skip=true" works after the
maven-bundle-plugin is upgraded (#566) otherwise "mvn clean install
-Dmaven.javadoc.skip=true" fails with a NPE.
2/ Not skipping javadoc,
And then the build fails at the first module that has it's own
maven-javadoc-plugin setup; same error. That module ATM is jena-text
where it isn't needed, remove, -rf restart OK ... until the next one.
On 25/04/2019 22:12, Andy Seaborne wrote:
> Great - I thought I'd tried that and also using JDK12 which is supposed
> to have it fixed. But if it works for you, then I must have made a
> mistake. I'll try it ASAP.
>
> Andy
>
> On 25/04/2019 20:52, Aaron Coburn wrote:
>> I think this can be fixed by setting the javadoc configuration to use
>> Java
>> 8 as the source.
>> I submitted a PR to this effect here:
>> https://github.com/apache/jena/pull/565
>> but please give that branch a real test on your local system before
>> merging, I'm traveling at the moment and am not in a great position to
>> run
>> a full build. (Though running mvn javadoc:javadoc seems OK under JDK11)
>>
>> Aaron
>>
>> On Thu, Apr 25, 2019 at 9:07 AM Andy Seaborne <an...@apache.org> wrote:
>>
>>> With the elephas change, I tried to build with java11 (producing java8
>>> byte code).
>>>
>>> We seem to be blocked by not being able to produce javadoc.
>>>
>>> The error is for each module:
>>> """
>>> The code being documented uses modules but the packages defined in
>>> https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module.
>>> """
>>>
>>> The block is:
>>>
>>> https://bugs.openjdk.java.net/browse/JDK-8212233
>>>
>>> and I haven't found a workaround that works. (I am using Ubuntu dist
>>> java, 11.0.3 which is claimed to have a backport of the fix).
>>>
>>> Anyone know anything about this?
>>>
>>> Andy
>>>
>>
Re: The state of jena+Java11
Posted by Andy Seaborne <an...@apache.org>.
Great - I thought I'd tried that and also using JDK12 which is supposed
to have it fixed. But if it works for you, then I must have made a
mistake. I'll try it ASAP.
Andy
On 25/04/2019 20:52, Aaron Coburn wrote:
> I think this can be fixed by setting the javadoc configuration to use Java
> 8 as the source.
> I submitted a PR to this effect here:
> https://github.com/apache/jena/pull/565
> but please give that branch a real test on your local system before
> merging, I'm traveling at the moment and am not in a great position to run
> a full build. (Though running mvn javadoc:javadoc seems OK under JDK11)
>
> Aaron
>
> On Thu, Apr 25, 2019 at 9:07 AM Andy Seaborne <an...@apache.org> wrote:
>
>> With the elephas change, I tried to build with java11 (producing java8
>> byte code).
>>
>> We seem to be blocked by not being able to produce javadoc.
>>
>> The error is for each module:
>> """
>> The code being documented uses modules but the packages defined in
>> https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module.
>> """
>>
>> The block is:
>>
>> https://bugs.openjdk.java.net/browse/JDK-8212233
>>
>> and I haven't found a workaround that works. (I am using Ubuntu dist
>> java, 11.0.3 which is claimed to have a backport of the fix).
>>
>> Anyone know anything about this?
>>
>> Andy
>>
>
Re: The state of jena+Java11
Posted by Aaron Coburn <aa...@gmail.com>.
I think this can be fixed by setting the javadoc configuration to use Java
8 as the source.
I submitted a PR to this effect here:
https://github.com/apache/jena/pull/565
but please give that branch a real test on your local system before
merging, I'm traveling at the moment and am not in a great position to run
a full build. (Though running mvn javadoc:javadoc seems OK under JDK11)
Aaron
On Thu, Apr 25, 2019 at 9:07 AM Andy Seaborne <an...@apache.org> wrote:
> With the elephas change, I tried to build with java11 (producing java8
> byte code).
>
> We seem to be blocked by not being able to produce javadoc.
>
> The error is for each module:
> """
> The code being documented uses modules but the packages defined in
> https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module.
> """
>
> The block is:
>
> https://bugs.openjdk.java.net/browse/JDK-8212233
>
> and I haven't found a workaround that works. (I am using Ubuntu dist
> java, 11.0.3 which is claimed to have a backport of the fix).
>
> Anyone know anything about this?
>
> Andy
>