yes, that sounds reasonable. good to be aware of the status here though

On Wed 19. Feb 2020 at 19:09, Rob Vesse <[email protected]> wrote:

> So that stack trace implies that ElasticSearch is violating some of the
> constraints imposed by newer JVMs which are all part of JPMS (Java Platform
> Module System) which is ultimately about making code more easily portable
> and trying to stop people doing “naughty” stuff with JVM internals that
> they shouldn’t
>
>
>
> The upshot of which is that this should be addressed by the ElasticSearch
> community
>
>
>
> It is possible that they already have addressed this and the Jena
> community needs to upgrade to a newer ElasticSearch, in which case
> contributions welcome
>
>
>
> Rob
>
>
>
> From: Marco Neumann <[email protected]>
> Reply to: <[email protected]>
> Date: Wednesday, 19 February 2020 at 18:57
> To: <[email protected]>
> Subject: Re: mvn build Apache Jena 3.15.0-SNAPSHOT
>
>
>
>
>
>
>
>
>
> On Wed, Feb 19, 2020 at 4:49 PM Andy Seaborne <[email protected]> wrote:
>
>
>
> On 19/02/2020 14:04, Marco Neumann wrote:
> > On Wed, Feb 19, 2020 at 10:27 AM Andy Seaborne <[email protected]> wrote:
> >
> >> https://builds.apache.org/view/H-L/view/Jena/
> >>
> >> On 17/02/2020 15:32, Marco Neumann wrote:
> >>> FYI
> >>>
> >>> current Apache Jena 3.15.0-SNAPSHOT mvn build fails with OpenJDK 13.02
> on
> >>> SPARQL Text Search - Elasticsearch
> >>
> >> In what way?
>
> Marco - in what way does it fail?
>
>
>
> Andy, something along those lines:
>
> Caused by: java.security.AccessControlException: access denied
> ("java.lang.RuntimePermission"
> "accessClassInPackage.jdk.internal.vm.annotation")
>
>
>
> in the Apache Jena - SPARQL Text Search - Elasticsearch module
>
>
>
> for details see attached debug.log  openjdk version "13.0.2" 2020-01-14
> linux (64-Bit Server VM)
>
>
>
> It's not a big deal for our current setup to change the jdk but it might
> interfere with some build pipelines
>
>
>
>
>
>
> >> Do you have fix?
> >>
> >
> > the fix for now is to use jdk_12.01 for the build and tests with 'clean
> > install'
> >
> > BUILD SUCCESS
> > Total time:  06:51 min
> >
> > I have a similar issue and jdks with the ElasticSearch build over at
> RDF4j.
> > looks like it's jdk_13.02 related
> >
> >
> >>
> >> BTW ElasticSearch test plugin has a timing issue - the background server
> >> does not always close down promptly. The error does not cause maven to
> >> stop usually.
> >>
> >>>
> >>> builds successful with OpenJDK 12.0.1 but need to manually skip java
> doc.
> >>> Doesn't skip on GeoSPARQL Engine doc automatically.
> >>
> >> With -Pdev?
> >>
> >
> > see above. fixed for now
> >
> >
> >>
> >>> Apache Maven 3.6.3
> >>> OS name: "linux"
> >>> Total time:  04:23 min
> >>>
> >>
> >
> >
>
>
>
>
> --
>
>
>
> ---
> Marco Neumann
> KONA
>
> --


---
Marco Neumann
KONA

Reply via email to