Hi Andrii,
Thank you for letting us know. It's good to hear from downstream
communities.
Andy
On 12/01/2021 09:21, Andrii Berezovskyi wrote:
Dear Andy, Aaron,
Thank you for a prompt reply!
If there are concerns, please link to the reports. There has been some
scuttlebutt, indeed
It's also worth noting that from a security perspective continuing to support
Java 8 is increasingly going to become a problem for end users. In my $dayjob
we see a lot of concern about outdated software versions, even and especially
so, as we move to a more containerised model. A lot of
Dear Andy, Aaron,
Thank you for a prompt reply!
If there are concerns, please link to the reports. There has been some
scuttlebutt, indeed FUD, about RDF*.
Thank you and apologies for unintentional participation in the FUD-spreading!
I'd be interested in understanding the situation here - for
>
> > Are you switching libs or did Titanium drop JDK 8?
Titanium never supported JDK 8. It uses the java.net.http.HttpClient that
is part of JDK 11.
> So this is really a choice point - keep to long lived legacy
> compatibility, which might be very long, or keep to some of up-to-date
>
Hi Andrii,
On 11/01/2021 12:59, Andrii Berezovskyi wrote:
Hello,
Just noticed that the discussion went really fast.
The discussion started on the dev@jena list.
It isn't a done deal - no release yet.
I am a maintainer for Eclipse Lyo and as an integration SDK, we ship JDK 8
library
+1 to bumping version number, it is clearly a breaking change.
Dave
On 11/01/2021 12:59, Andrii Berezovskyi wrote:
Hello,
Just noticed that the discussion went really fast. I am a maintainer for
Eclipse Lyo and as an integration SDK, we ship JDK 8 library builds for wide
compat (with Jena
Hello,
Just noticed that the discussion went really fast. I am a maintainer for
Eclipse Lyo and as an integration SDK, we ship JDK 8 library builds for wide
compat (with Jena dependency). Our GH Actions build matrix succeeds on JDK 8,
11, 15, 16-ea, and 17-ea but this change will be breaking
The Jena build has been switched to produce Java11 bytecode.
Nothing else in the codebase has been changed so this is easily
reversible at the moment.
Using SNAPSHOT artifacts will get you Java11 bytecode.
There is currently some problems producing javadoc
One problem is [1] on early Java11
On 06/01/2021 08:40, Dave Reynolds wrote:
tl;dr It'd be inconvenient but we could cope.
As you say, there is likely to remain a bimodal distribution.
We currently remain with the java 8 runtime (increasingly using AWS
Corretto). Mostly this is due to the time cost of qualifying and
The javax dependency is in my code. This was just a modest warning in
case other folks use JAXB and Jena together.
On 1/6/2021 7:59 AM, Andy Seaborne wrote:
Steve -
Useful information - but I' not sure what the effect is here - I am a
complete non-user of OSGi so I'm afraid someone will
I have had no problem using Jena with OSGi on Java 11 (Apache Karaf). You
need one of the more recent releases of Karaf, but IIRC I didn't need to do
anything unusual.
Are there particular errors you are encountering with OSGi and Jena in a
Java 11 JRE? Perhaps we can take up the details in a
Steve -
Useful information - but I' not sure what the effect is here - I am a
complete non-user of OSGi so I'm afraid someone will have to spell it
out for me.
The package in artifact javax.xml.bind:jaxb-api is javax.xml.bind --
where does com.sun.xml.bind.v2 fit in?
Jena OSGi does not
The issue has something to do with class loading the context, which
apparently is done differently in an osgi bundle. See, e.g.,
http://www.descher.at/descher-vu/2019/01/java-11-jaxb-and-osgi/
On 1/6/2021 7:11 AM, Andy Seaborne wrote:
On 05/01/2021 22:46, Steve Vestal wrote:
Support for
On 05/01/2021 22:46, Steve Vestal wrote:
Support for JAXB was removed from Java11. For those using that and Jena
in osgi bundles (e.g., Eclipse plugins), my impression from some initial
experimenting and searching is that a bit of wizardry is needed to add
that on the side and get it
tl;dr It'd be inconvenient but we could cope.
As you say, there is likely to remain a bimodal distribution.
We currently remain with the java 8 runtime (increasingly using AWS
Corretto). Mostly this is due to the time cost of qualifying and
updating an increasingly large number of different
Support for JAXB was removed from Java11. For those using that and Jena
in osgi bundles (e.g., Eclipse plugins), my impression from some initial
experimenting and searching is that a bit of wizardry is needed to add
that on the side and get it working. I could not find a clean and
simple
Currently, Jena is compiled to run on any JVM from Java8 onwards.
Java8 was released March 2014.
Java11 (Sept 2018) is LTS (long term support)
Java17 (due Sept 2021) is probably going to be LTS.
Should Jena switch to Java11 going forward?
This message is to ask:
Are there deployments that do
17 matches
Mail list logo
