Re: [] [] Apache Jena 4.7.0 RC1
On 27/12/2022 11:45, Marco Neumann wrote: After shutting down a local instance of fuseki, all tests pass now and the build is successful. I remember that attempting to bind port 3030 has been in issue for some time and changing ports for the tests is a good idea. Already fixed for the next RC by: https://github.com/apache/jena/commit/080e9e71bc3ecabc88e2f9e1cb2dba220b68de3c Not ideal, but an easy fix for a later better one. At least it's not 3030. If the port is zero, a Fuseki (well, the OS really) allocates a free port which can be retrieved with getPort. While this is good news, I still get some intermittent but not reproducible test failures for the fuseki-UI cypress tests. https://github.com/apache/jena/issues/1644 the only thing that has changed is that it isn't only on one of my machines now which it has been for sometime - and it has just happened on a GH action. It does not appear to be Jena - it passes sometime .. in a deterministic test. Altering the local machine networking (including whether docker is running) changes the situation. So it seems to be the Cypress tests (the tests are not calling a Apache Jena Fuseki server, they call a mock). There is a screenshot captured in tests/e2e/screenshots/datasets.cy.js/datasets/ Changing the test order does not it fix it - just moves an error around. [INFO] [TESTS] ERROR Error: Command failed: /home/lotico/git/jena/jena-fuseki2/jena-fuseki-ui/node_modules/cypress/bin/cypress run --config baseUrl=http://localhost:33661 --headless Andy
Re: [] [] Apache Jena 4.7.0 RC1
After shutting down a local instance of fuseki, all tests pass now and the build is successful. I remember that attempting to bind port 3030 has been in issue for some time and changing ports for the tests is a good idea. While this is good news, I still get some intermittent but not reproducible test failures for the fuseki-UI cypress tests. [INFO] [TESTS] ERROR Error: Command failed: /home/lotico/git/jena/jena-fuseki2/jena-fuseki-ui/node_modules/cypress/bin/cypress run --config baseUrl=http://localhost:33661 --headless [INFO] [TESTS] Error: Command failed: /home/lotico/git/jena/jena-fuseki2/jena-fuseki-ui/node_modules/cypress/bin/cypress run --config baseUrl=http://localhost:33661 --headless [INFO] [TESTS] at makeError (/home/lotico/git/jena/jena-fuseki2/jena-fuseki-ui/node_modules/execa/index.js:174:9) [INFO] [TESTS] at /home/lotico/git/jena/jena-fuseki2/jena-fuseki-ui/node_modules/execa/index.js:278:16 [INFO] [TESTS] at processTicksAndRejections (node:internal/process/task_queues:96:5) [INFO] [TESTS] vue-cli-service test:e2e --headless exited with code 1 [INFO] --> Sending SIGTERM to other processes.. [INFO] [SERVER] yarn run serve:fuseki exited with code SIGTERM [INFO] error Command failed with exit code 1. [INFO] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. [INFO] [INFO] Reactor Summary for Apache Jena 4.8.0-SNAPSHOT: [INFO] [INFO] Apache Jena SUCCESS [ 2.531 s] [INFO] Apache Jena - Shadowed external libraries .. SUCCESS [ 1.871 s] [INFO] Apache Jena - IRI .. SUCCESS [ 4.383 s] [INFO] Apache Jena - Base . SUCCESS [ 7.559 s] [INFO] Apache Jena - Core . SUCCESS [ 41.746 s] [INFO] Apache Jena - ARQ .. SUCCESS [ 44.269 s] [INFO] Apache Jena - SHACL SUCCESS [ 5.231 s] [INFO] Apache Jena - ShEx . SUCCESS [ 6.129 s] [INFO] Apache Jena - RDF Patch SUCCESS [ 2.787 s] [INFO] Apache Jena - RDF Connection ... SUCCESS [ 4.030 s] [INFO] Apache Jena - DBOE Database Operation Environment .. SUCCESS [ 0.020 s] [INFO] Apache Jena - DBOE Base SUCCESS [ 3.691 s] [INFO] Apache Jena - DBOE Transactions SUCCESS [ 3.215 s] [INFO] Apache Jena - DBOE Indexes . SUCCESS [ 1.708 s] [INFO] Apache Jena - DBOE Index test suite SUCCESS [ 0.155 s] [INFO] Apache Jena - DBOE Transactional Datastructures SUCCESS [ 6.691 s] [INFO] Apache Jena - DBOE Storage . SUCCESS [ 2.986 s] [INFO] Apache Jena - TDB1 (Native Triple Store) ... SUCCESS [ 33.488 s] [INFO] Apache Jena - TDB2 (Native Triple Store) ... SUCCESS [ 23.775 s] [INFO] Apache Jena - Libraries POM SUCCESS [ 0.099 s] [INFO] Apache Jena - Command line tools ... SUCCESS [ 5.192 s] [INFO] Apache Jena - SPARQL Text Search ... SUCCESS [ 27.702 s] [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server . SUCCESS [ 0.008 s] [INFO] Apache Jena - Fuseki Core Engine ... SUCCESS [ 8.677 s] [INFO] Apache Jena - Fuseki UI FAILURE [01:09 min] [INFO] Apache Jena - Fuseki Data Access Control ... SKIPPED [INFO] Apache Jena - Fuseki Server Main ... SKIPPED [INFO] Apache Jena - Fuseki Server Jar SKIPPED [INFO] Apache Jena - Fuseki Webapp SKIPPED [INFO] Apache Jena - Fuseki WAR File .. SKIPPED [INFO] Apache Jena - Fuseki Server Standalone Jar . SKIPPED [INFO] Apache Jena - Fuseki Docker Tools .. SKIPPED [INFO] Apache Jena - Fuseki Binary Distribution ... SKIPPED [INFO] Apache Jena - GeoSPARQL Engine . SKIPPED [INFO] Apache Jena - Fuseki with GeoSPARQL Engine . SKIPPED [INFO] Apache Jena - Integration Testing .. SKIPPED [INFO] Apache Jena - Distribution . SKIPPED [INFO] Apache Jena - Security Permissions . SKIPPED [INFO] Apache Jena - Extras ... SKIPPED [INFO] Apache Jena - Extras - Query Builder ... SKIPPED [INFO] Apache Jena - CommonsRDF for Jena .. SKIPPED [INFO] Apache Jena - Extras - Service Enhancer SKIPPED [INFO] Apache Jena - Code Examples SKIPPED [INFO] Apache Jena - JDBC Parent .. SKIPPED [INFO] Apache Jena - JDBC Core API SKIPPED [INFO] Apache Jena - JDBC Remote Endpoint Driver .. SKIPPED [INFO] Apache Jena - JDBC In-Memory Driver SKIPPED [INFO] Apache Jena -
Re: [] [] Apache Jena 4.7.0 RC1
Hi, That is the same issue I also reported very very hidden in a Github PR: https://github.com/apache/jena/pull/1630#issuecomment-1321711418 I suggested a pointer for people building it on server where those libs might be missing, maybe close to or in developers doc, but I don't know what the correct place would be to find it. Bruno was thinking of A note in Jena Fuseki UI README.md, a BUILD.md file, a text somewhere in jena.apache.org? see, https://github.com/apache/jena/pull/1630#issuecomment-1322022087 But I have no idea where it would at least have a chance to be seen for this very rare issue. Cheers, Lorenz On 26.12.22 14:32, Marco Neumann wrote: had a look at the log and was able to fix this error. The system was missing the Xvfb dependency which seems to be required by the Cypress test framework. it's now passing the jena-fuseki2 build. and ready to get stuck in the geosparql tests. jena-fuseki-geosparql seems to build fine on its own but fails as part of the main pom. [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.709 s [INFO] Finished at: [INFO] [ERROR] No plugin found for prefix 'jena-fuseki-geosparql' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/lotico/.m2/repository), apache.snapshots ( https://repository.apache.org/snapshots), central ( https://repo.maven.apache.org/maven2)] -> [Help 1] org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin found for prefix 'jena-fuseki-geosparql' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/lotico/.m2/repository), apache.snapshots ( https://repository.apache.org/snapshots), central ( https://repo.maven.apache.org/maven2)] at org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve (DefaultPluginPrefixResolver.java:95) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix (MojoDescriptorCreator.java:266) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor (MojoDescriptorCreator.java:220) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:104) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:83) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:89) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293) at org.apache.maven.cli.MavenCli.main (MavenCli.java:196) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.in[INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.709 s [INFO] Finished at: 2022-12-26T14:30:37+01:00 [INFO] [ERROR] No plugin found for prefix 'jena-fuseki-geosparql' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/lotico/.m2/repository), apache.snapshots ( https://repository.apache.org/snapshots), central ( https://repo.maven.apache.org/maven2)] -> [Help 1] org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin found for prefix 'jena-fuseki-geosparql' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/lotico/.m2/repository), apache.snapshots ( https://repository.apache.org/snapshots), central ( https://repo.maven.apache.org/maven2)] at org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve (DefaultPluginPrefixResolver.java:95) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix (MojoDescriptorCreator.java:266) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor (MojoDescriptorCreator.java:220) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:104) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:83) at
Re: [] [] Apache Jena 4.7.0 RC1
had a look at the log and was able to fix this error. The system was missing the Xvfb dependency which seems to be required by the Cypress test framework. it's now passing the jena-fuseki2 build. and ready to get stuck in the geosparql tests. jena-fuseki-geosparql seems to build fine on its own but fails as part of the main pom. [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.709 s [INFO] Finished at: [INFO] [ERROR] No plugin found for prefix 'jena-fuseki-geosparql' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/lotico/.m2/repository), apache.snapshots ( https://repository.apache.org/snapshots), central ( https://repo.maven.apache.org/maven2)] -> [Help 1] org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin found for prefix 'jena-fuseki-geosparql' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/lotico/.m2/repository), apache.snapshots ( https://repository.apache.org/snapshots), central ( https://repo.maven.apache.org/maven2)] at org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve (DefaultPluginPrefixResolver.java:95) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix (MojoDescriptorCreator.java:266) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor (MojoDescriptorCreator.java:220) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:104) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:83) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:89) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293) at org.apache.maven.cli.MavenCli.main (MavenCli.java:196) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.in[INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.709 s [INFO] Finished at: 2022-12-26T14:30:37+01:00 [INFO] [ERROR] No plugin found for prefix 'jena-fuseki-geosparql' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/lotico/.m2/repository), apache.snapshots ( https://repository.apache.org/snapshots), central ( https://repo.maven.apache.org/maven2)] -> [Help 1] org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin found for prefix 'jena-fuseki-geosparql' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/lotico/.m2/repository), apache.snapshots ( https://repository.apache.org/snapshots), central ( https://repo.maven.apache.org/maven2)] at org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve (DefaultPluginPrefixResolver.java:95) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix (MojoDescriptorCreator.java:266) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor (MojoDescriptorCreator.java:220) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:104) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:83) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:89) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293) at org.apache.maven.cli.MavenCli.main (MavenCli.java:196) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
Re: [] [] Apache Jena 4.7.0 RC1
jena-fuseki-ui: Failed to run task: 'yarn run test:e2e -- --headless --browser chrome' failed. org.apache.commons.exec.ExecuteException: That message is only the log of the test failing - there will be text above indicating what happened in the e2e tests. Andy On 24/12/2022 20:50, Marco Neumann wrote: so far I can only confirm that it fails. I will add more details next week if I can find some. On Sat, Dec 24, 2022 at 8:44 PM Andy Seaborne wrote: We have an issue for this:: https://github.com/apache/jena/issues/1644 Please add details so we identify the cause. Andy On Sat, 24 Dec 2022, 18:35 Marco Neumann, wrote: while you are at it also take a look at the issue with jena-fuseki-ui: Failed to run task: 'yarn run test:e2e -- --headless --browser chrome' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) it prevents me from building a fresh clone with a clean install. On Sat, Dec 24, 2022 at 6:28 PM Andy Seaborne wrote: The problems with GeoSPARQL tests means this RC is cancelled. It'll be a few days before RC2. Andy On 20/12/2022 16:39, Andy Seaborne wrote: Hi, Here is a vote on the release of Apache Jena 4.7.0. This is the first release candidate. The deadline is Friday, 23rd December 2022 at 18:00 UTC Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... -- --- Marco Neumann
Re: [] [] Apache Jena 4.7.0 RC1
so far I can only confirm that it fails. I will add more details next week if I can find some. On Sat, Dec 24, 2022 at 8:44 PM Andy Seaborne wrote: > We have an issue for this:: > > https://github.com/apache/jena/issues/1644 > > Please add details so we identify the cause. > > Andy > > On Sat, 24 Dec 2022, 18:35 Marco Neumann, wrote: > > > while you are at it also take a look at the issue with > > > > jena-fuseki-ui: Failed to run task: 'yarn run test:e2e -- --headless > > --browser chrome' failed. org.apache.commons.exec.ExecuteException: > Process > > exited with an error: 1 (Exit value: 1) > > > > it prevents me from building a fresh clone with a clean install. > > > > > > On Sat, Dec 24, 2022 at 6:28 PM Andy Seaborne wrote: > > > > > The problems with GeoSPARQL tests means this RC is cancelled. > > > > > > It'll be a few days before RC2. > > > > > > Andy > > > > > > On 20/12/2022 16:39, Andy Seaborne wrote: > > > > Hi, > > > > > > > > Here is a vote on the release of Apache Jena 4.7.0. > > > > This is the first release candidate. > > > > > > > > The deadline is > > > > > > > > Friday, 23rd December 2022 at 18:00 UTC > > > > > > > > Please vote to approve this release: > > > > > > > > [ ] +1 Approve the release > > > > [ ] 0 Don't care > > > > [ ] -1 Don't release, because ... > > > > > > > > > > > > > -- > > > > > > --- > > Marco Neumann > > > -- --- Marco Neumann
Re: [] [] Apache Jena 4.7.0 RC1
We have an issue for this:: https://github.com/apache/jena/issues/1644 Please add details so we identify the cause. Andy On Sat, 24 Dec 2022, 18:35 Marco Neumann, wrote: > while you are at it also take a look at the issue with > > jena-fuseki-ui: Failed to run task: 'yarn run test:e2e -- --headless > --browser chrome' failed. org.apache.commons.exec.ExecuteException: Process > exited with an error: 1 (Exit value: 1) > > it prevents me from building a fresh clone with a clean install. > > > On Sat, Dec 24, 2022 at 6:28 PM Andy Seaborne wrote: > > > The problems with GeoSPARQL tests means this RC is cancelled. > > > > It'll be a few days before RC2. > > > > Andy > > > > On 20/12/2022 16:39, Andy Seaborne wrote: > > > Hi, > > > > > > Here is a vote on the release of Apache Jena 4.7.0. > > > This is the first release candidate. > > > > > > The deadline is > > > > > > Friday, 23rd December 2022 at 18:00 UTC > > > > > > Please vote to approve this release: > > > > > > [ ] +1 Approve the release > > > [ ] 0 Don't care > > > [ ] -1 Don't release, because ... > > > > > > > > -- > > > --- > Marco Neumann >
Re: [] Apache Jena 4.7.0 RC1
Hmm.
https://ci-builds.apache.org/job/Jena/job/Jena_Development_Deploy/385/
shows the same situation but that's a later commit: d5d727b
Job 384 has the "[maven-release-plugin] prepare release jena-4.7.0"
commit and that succeeded.
https://ci-builds.apache.org/job/Jena/job/Jena_Development_Test/
is OK at commit d5d727b
It looks like an initialization of tests issue for GeoSPARQL because
tests can be run in a random order.
The tests don't call Jena initialization directly. Many do touch Jena
code in setupClass but if there is already class initialization running,
recursive initialization is disabled (by the JDK).
Running the first test class in the pastebin - AngleFFTest - on it's own
fails on the ARQ constant for the PropertyFunctionRegistry
That isn't NoClassDefFoundError but broken class initialization may
leave things in a inconsistent state.
GeoSPARQL does have a serviceloader init that looks right.
I think we need to fix this and do RC2.
Andy
PS
It is only tests.
System initialization is being called. So geosparql must be partially
initializing, triggering JenaSystem.init but during it's own class init.
I love it when "static final Object abc = new X()" is null.
On 24/12/2022 17:16, Bruno Kinoshita wrote:
Hi Andy,
I just came back home and booted up Ubuntu, opened the browser and command
line and tried these commands. But I did use Eclipse in the past, so tried
these now:
find . -name work -type d -exec rm -rf {} \;
find . -name target -type d -exec rm -rf {} \;
mvn clean
mvn install
Same error.
mvn install -rf :jena-geosparql
also gives the same errors.
Bruno
Re: [] Apache Jena 4.7.0 RC1
Hi Andy,
I just came back home and booted up Ubuntu, opened the browser and command
line and tried these commands. But I did use Eclipse in the past, so tried
these now:
find . -name work -type d -exec rm -rf {} \;
find . -name target -type d -exec rm -rf {} \;
mvn clean
mvn install
Same error.
mvn install -rf :jena-geosparql
also gives the same errors.
Bruno
On Sat, 24 Dec 2022 at 17:42, Andy Seaborne wrote:
> Works for me (obviously, since the RC got built!)
>
> `mvn clean install` is probably necessary
>
> Does
>
> `mvn install -rf :jena-geosparql` restart the build?
>
>
>
> * java.lang.NoClassDefFoundError
>
> I've seen this, and similar, if Eclipse is also running even if idle.
>
> Eclipse sees the target directories changing on disk, and recompiles
> automatically while maven is running.
>
> Then what exactly goes wrong is "timing".
>
> * Caused by: org.apache.jena.sparql.ARQException: Context key is null
>
> is consistent with that, not finding a service loader file or deleting
> and recompiling a class causing class init mayhem.
>
>
> Could this be the issue?
>
> (I'm using same java17 version to compile, mvn 3.8.6 which is x.x.1 ahead.)
>
> GeoSPARQL isn't "core" -
>
> Andy
>
>
> On 24/12/2022 16:14, Bruno Kinoshita wrote:
> > Ok, confirmed I haven't voted. Fetched upstream, including tags. Checked
> > out jena-4.7.0:
> >
> > commit 3a62b5a5f162ef01fd46164fa11ffb5323169a61 (HEAD, tag: jena-4.7.0)
> > Author: Andy Seaborne
> > Date: Tue Dec 20 13:34:40 2022 +
> >
> > [maven-release-plugin] prepare release jena-4.7.0
> >
> > Then tried `mvn`, `mvn -Pdev`, `mvn install`, `mvn clean install` and all
> > four commands failed in the GeoSPARQL tests for my environment:
> >
> > Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
> > Maven home: /opt/apache-maven-3.8.5
> > Java version: 17.0.5, vendor: Private Build, runtime:
> > /usr/lib/jvm/java-17-openjdk-amd64
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "5.15.0-56-generic", arch: "amd64", family:
> > "unix"
> >
> > And the errors here: https://paste.apache.org/57232
> >
> > Could be just my environment (maven, OS, etc) so if it works for others,
> > n=that's not a blocker for the release I believe.
> >
> > Cheers
> > Bruno
> >
> > On Sat, 24 Dec 2022 at 10:58, Bruno Kinoshita wrote:
> >
> >> I don't think I voted yet... I will have time in 5 or 6 hours when I
> >> return home to confirm I haven't and then test and vote.
> >>
> >> Thanks!
> >>
> >> On Sat, 24 Dec 2022, 10:14 am Andy Seaborne, wrote:
> >>
> >>> Would any PMC member have a moment to cast a third vote?
> >>>
> >>> Andy
> >>>
> >>> On 20/12/2022 16:39, Andy Seaborne wrote:
> Hi,
>
> Here is a vote on the release of Apache Jena 4.7.0.
> This is the first release candidate.
>
> The deadline is
>
> Friday, 23rd December 2022 at 18:00 UTC
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
> >>>
> >>>
> >
>
Re: [] Apache Jena 4.7.0 RC1
Works for me (obviously, since the RC got built!) `mvn clean install` is probably necessary Does `mvn install -rf :jena-geosparql` restart the build? * java.lang.NoClassDefFoundError I've seen this, and similar, if Eclipse is also running even if idle. Eclipse sees the target directories changing on disk, and recompiles automatically while maven is running. Then what exactly goes wrong is "timing". * Caused by: org.apache.jena.sparql.ARQException: Context key is null is consistent with that, not finding a service loader file or deleting and recompiling a class causing class init mayhem. Could this be the issue? (I'm using same java17 version to compile, mvn 3.8.6 which is x.x.1 ahead.) GeoSPARQL isn't "core" - Andy On 24/12/2022 16:14, Bruno Kinoshita wrote: Ok, confirmed I haven't voted. Fetched upstream, including tags. Checked out jena-4.7.0: commit 3a62b5a5f162ef01fd46164fa11ffb5323169a61 (HEAD, tag: jena-4.7.0) Author: Andy Seaborne Date: Tue Dec 20 13:34:40 2022 + [maven-release-plugin] prepare release jena-4.7.0 Then tried `mvn`, `mvn -Pdev`, `mvn install`, `mvn clean install` and all four commands failed in the GeoSPARQL tests for my environment: Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0) Maven home: /opt/apache-maven-3.8.5 Java version: 17.0.5, vendor: Private Build, runtime: /usr/lib/jvm/java-17-openjdk-amd64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.15.0-56-generic", arch: "amd64", family: "unix" And the errors here: https://paste.apache.org/57232 Could be just my environment (maven, OS, etc) so if it works for others, n=that's not a blocker for the release I believe. Cheers Bruno On Sat, 24 Dec 2022 at 10:58, Bruno Kinoshita wrote: I don't think I voted yet... I will have time in 5 or 6 hours when I return home to confirm I haven't and then test and vote. Thanks! On Sat, 24 Dec 2022, 10:14 am Andy Seaborne, wrote: Would any PMC member have a moment to cast a third vote? Andy On 20/12/2022 16:39, Andy Seaborne wrote: Hi, Here is a vote on the release of Apache Jena 4.7.0. This is the first release candidate. The deadline is Friday, 23rd December 2022 at 18:00 UTC Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ...
Re: [] Apache Jena 4.7.0 RC1
Ok, confirmed I haven't voted. Fetched upstream, including tags. Checked out jena-4.7.0: commit 3a62b5a5f162ef01fd46164fa11ffb5323169a61 (HEAD, tag: jena-4.7.0) Author: Andy Seaborne Date: Tue Dec 20 13:34:40 2022 + [maven-release-plugin] prepare release jena-4.7.0 Then tried `mvn`, `mvn -Pdev`, `mvn install`, `mvn clean install` and all four commands failed in the GeoSPARQL tests for my environment: Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0) Maven home: /opt/apache-maven-3.8.5 Java version: 17.0.5, vendor: Private Build, runtime: /usr/lib/jvm/java-17-openjdk-amd64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.15.0-56-generic", arch: "amd64", family: "unix" And the errors here: https://paste.apache.org/57232 Could be just my environment (maven, OS, etc) so if it works for others, n=that's not a blocker for the release I believe. Cheers Bruno On Sat, 24 Dec 2022 at 10:58, Bruno Kinoshita wrote: > I don't think I voted yet... I will have time in 5 or 6 hours when I > return home to confirm I haven't and then test and vote. > > Thanks! > > On Sat, 24 Dec 2022, 10:14 am Andy Seaborne, wrote: > >> Would any PMC member have a moment to cast a third vote? >> >> Andy >> >> On 20/12/2022 16:39, Andy Seaborne wrote: >> > Hi, >> > >> > Here is a vote on the release of Apache Jena 4.7.0. >> > This is the first release candidate. >> > >> > The deadline is >> > >> > Friday, 23rd December 2022 at 18:00 UTC >> > >> > Please vote to approve this release: >> > >> > [ ] +1 Approve the release >> > [ ] 0 Don't care >> > [ ] -1 Don't release, because ... >> >>
Re: [] Apache Jena 4.7.0 RC1
[X] +1 (binding) tried the RC1 on our current deployment and couldn't see any different or negative behaviour but lots of improvements! Thanks Andy and also thanks to contributors! Cheers, Lorenz On 24.12.22 10:58, Bruno Kinoshita wrote: I don't think I voted yet... I will have time in 5 or 6 hours when I return home to confirm I haven't and then test and vote. Thanks! On Sat, 24 Dec 2022, 10:14 am Andy Seaborne, wrote: Would any PMC member have a moment to cast a third vote? Andy On 20/12/2022 16:39, Andy Seaborne wrote: Hi, Here is a vote on the release of Apache Jena 4.7.0. This is the first release candidate. The deadline is Friday, 23rd December 2022 at 18:00 UTC Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ...
Re: [] Apache Jena 4.7.0 RC1
I don't think I voted yet... I will have time in 5 or 6 hours when I return home to confirm I haven't and then test and vote. Thanks! On Sat, 24 Dec 2022, 10:14 am Andy Seaborne, wrote: > Would any PMC member have a moment to cast a third vote? > > Andy > > On 20/12/2022 16:39, Andy Seaborne wrote: > > Hi, > > > > Here is a vote on the release of Apache Jena 4.7.0. > > This is the first release candidate. > > > > The deadline is > > > > Friday, 23rd December 2022 at 18:00 UTC > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] 0 Don't care > > [ ] -1 Don't release, because ... > >
Re: [] Apache Jena 4.7.0 RC1
Would any PMC member have a moment to cast a third vote? Andy On 20/12/2022 16:39, Andy Seaborne wrote: Hi, Here is a vote on the release of Apache Jena 4.7.0. This is the first release candidate. The deadline is Friday, 23rd December 2022 at 18:00 UTC Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ...
Re: [] Apache Jena 4.7.0 RC1
OK I will repeat this elsewhere again but as you are aware there was a good discussion on the SPARQL-12 list with plenty of suggestions. maybe something like Sideways Information Passing or correlated subquery join. I will end this thread here to allow the process to proceed. On Tue, Dec 20, 2022 at 5:06 PM Andy Seaborne wrote: > > On 20/12/2022 16:44, Marco Neumann wrote: > > The URL to Lateral Joins is broken > > https://jena.apache.org/documentation/query/lateral-join.html > > The web site is updated when the release happens after the VOTE. > > It is on the "lateral-doc" branch at the moment. > > But go to the SPARQL CG text. > > > Overall I think this is a good contribution but I am not happy with the > > name "LATERAL join" as it implies SQL LATERAL join similarities. Can we > > call this something else? > > Such as? > > --- > > It is not suddenly dropping into a release. > It is mentioned in email "Towards Jena 4.7.0" > It is https://github.com/apache/jena/issues/1615 > > And it says "This is an experimental feature." > > VOTE threads are first and foremost about process. > > --- > > This is a discussion for SPARQL CG: > > https://github.com/w3c/sparql-12/issues/100 > https://github.com/w3c/sparql-12/blob/main/SEP/SEP-0006/sep-0006.md > > It's not what I might call a "join" (evaluate left and right arguments, > then perform operation to combine the two sides) but SQL-terminolgy is > often to call it a "join". > > https://docs.snowflake.com/en/sql-reference/constructs/join-lateral.html > """ > for each row in left_hand_table LHT: > execute right_hand_subquery RHS using the values from the current > row in the LHT > """ > > Andy > > c.f. Oxigraph. > > > > > Thank you, > > Marco > > > > . > > > > On Tue, Dec 20, 2022 at 4:39 PM Andy Seaborne wrote: > > > >> Hi, > >> > >> Here is a vote on the release of Apache Jena 4.7.0. > >> This is the first release candidate. > >> > >> The deadline is > >> > >> Friday, 23rd December 2022 at 18:00 UTC > >> > >> Please vote to approve this release: > >> > >> [ ] +1 Approve the release > >> [ ] 0 Don't care > >> [ ] -1 Don't release, because ... > >> > >> Items in this release > >> > >> https://s.apache.org/jena-4.7.0-issues > >> > >> Major: > >> > >> * Lucene upgrade 8.11.1 to 9.4.1 - @OyvindLGjesdal > >> There are changes to the stopword setting in the default > >> configuration of Lucene's StandardAnalyzer > >> Issue: https://github.com/apache/jena/issues/1581 > >> PR: https://github.com/apache/jena/pull/1582 > >> > >> * LATERAL joins > >> This is an experimental feature. > >> Issue: https://github.com/apache/jena/issues/1615 > >> Documentation: > >> https://jena.apache.org/documentation/query/lateral-join.html > >> > >> * RDF Patch > >> https://lists.apache.org/thread/8oc1gn2qnzx4ddwovx8h545jm270gpyx > >> Issue: https://github.com/apache/jena/issues/1618 > >> PR: https://github.com/apache/jena/pull/1619 > >> Documentation: https://github.com/apache/jena-site/pull/131 > >> > >> * Path improvements - @SimonBin et al > >> https://github.com/apache/jena/pull/1616 > >> https://github.com/apache/jena/pull/1638 > >> Plan: https://github.com/apache/jena/issues/1629 > >> > >> * Source code folder reorganisation > >> Rename jena-tdb directory as jena-tdb1 > >> Move jena-tdb2 directory to the top level directory > >> Issue: https://github.com/apache/jena/issues/1539 > >> Issue: https://github.com/apache/jena/issues/1540 > >> > >> Contributors: > >> OyvindL Gjesdal > >> Simon Bin > >> Alexandre Ardhuin > >> Claus Stadler > >> Brian Vvosburgh > >> Eric Prud'hommeaux > >> > >> Release Vote > >> > >> Everyone, not just committers, is invited to test and vote. > >> Please download and test the proposed release. > >> > >> Staging repository: > >> > https://repository.apache.org/content/repositories/orgapachejena-1055 > >> > >> Proposed dist/ area: > >> https://dist.apache.org/repos/dist/dev/jena/ > >> > >> Keys: > >> https://svn.apache.org/repos/asf/jena/dist/KEYS > >> > >> Git commit (browser URL): > >> https://github.com/apache/jena/commit/3a62b5a5f1 > >> > >> > >> Git Commit Hash: > >> 3a62b5a5f162ef01fd46164fa11ffb5323169a61 > >> > >> Git Commit Tag: > >> jena-4.7.0 > >> > >> This vote will be open until at least > >> > >> Friday, 23rd December 2022 at 18:00 UTC > >> > >> If you expect to check the release but the time limit does not work > >> for you, please email within the schedule above. > >> > >> Thanks, > >> > >>Andy > >> > >> Checking: > >> > >> + are the GPG signatures fine? > >> + are the checksums correct? > >> + is there a source archive? > >> + can the source archive be built? > >> (NB This requires a "mvn install" first time) > >> + is there a correct LICENSE and NOTICE file in each artifact > >> (both source and binary artifacts)?
Re: [] Apache Jena 4.7.0 RC1
On 20/12/2022 16:44, Marco Neumann wrote: The URL to Lateral Joins is broken https://jena.apache.org/documentation/query/lateral-join.html The web site is updated when the release happens after the VOTE. It is on the "lateral-doc" branch at the moment. But go to the SPARQL CG text. Overall I think this is a good contribution but I am not happy with the name "LATERAL join" as it implies SQL LATERAL join similarities. Can we call this something else? Such as? --- It is not suddenly dropping into a release. It is mentioned in email "Towards Jena 4.7.0" It is https://github.com/apache/jena/issues/1615 And it says "This is an experimental feature." VOTE threads are first and foremost about process. --- This is a discussion for SPARQL CG: https://github.com/w3c/sparql-12/issues/100 https://github.com/w3c/sparql-12/blob/main/SEP/SEP-0006/sep-0006.md It's not what I might call a "join" (evaluate left and right arguments, then perform operation to combine the two sides) but SQL-terminolgy is often to call it a "join". https://docs.snowflake.com/en/sql-reference/constructs/join-lateral.html """ for each row in left_hand_table LHT: execute right_hand_subquery RHS using the values from the current row in the LHT """ Andy c.f. Oxigraph. Thank you, Marco . On Tue, Dec 20, 2022 at 4:39 PM Andy Seaborne wrote: Hi, Here is a vote on the release of Apache Jena 4.7.0. This is the first release candidate. The deadline is Friday, 23rd December 2022 at 18:00 UTC Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... Items in this release https://s.apache.org/jena-4.7.0-issues Major: * Lucene upgrade 8.11.1 to 9.4.1 - @OyvindLGjesdal There are changes to the stopword setting in the default configuration of Lucene's StandardAnalyzer Issue: https://github.com/apache/jena/issues/1581 PR: https://github.com/apache/jena/pull/1582 * LATERAL joins This is an experimental feature. Issue: https://github.com/apache/jena/issues/1615 Documentation: https://jena.apache.org/documentation/query/lateral-join.html * RDF Patch https://lists.apache.org/thread/8oc1gn2qnzx4ddwovx8h545jm270gpyx Issue: https://github.com/apache/jena/issues/1618 PR: https://github.com/apache/jena/pull/1619 Documentation: https://github.com/apache/jena-site/pull/131 * Path improvements - @SimonBin et al https://github.com/apache/jena/pull/1616 https://github.com/apache/jena/pull/1638 Plan: https://github.com/apache/jena/issues/1629 * Source code folder reorganisation Rename jena-tdb directory as jena-tdb1 Move jena-tdb2 directory to the top level directory Issue: https://github.com/apache/jena/issues/1539 Issue: https://github.com/apache/jena/issues/1540 Contributors: OyvindL Gjesdal Simon Bin Alexandre Ardhuin Claus Stadler Brian Vvosburgh Eric Prud'hommeaux Release Vote Everyone, not just committers, is invited to test and vote. Please download and test the proposed release. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1055 Proposed dist/ area: https://dist.apache.org/repos/dist/dev/jena/ Keys: https://svn.apache.org/repos/asf/jena/dist/KEYS Git commit (browser URL): https://github.com/apache/jena/commit/3a62b5a5f1 Git Commit Hash: 3a62b5a5f162ef01fd46164fa11ffb5323169a61 Git Commit Tag: jena-4.7.0 This vote will be open until at least Friday, 23rd December 2022 at 18:00 UTC If you expect to check the release but the time limit does not work for you, please email within the schedule above. Thanks, Andy Checking: + are the GPG signatures fine? + are the checksums correct? + is there a source archive? + can the source archive be built? (NB This requires a "mvn install" first time) + is there a correct LICENSE and NOTICE file in each artifact (both source and binary artifacts)? + does the NOTICE file contain all necessary attributions? + have any licenses of dependencies changed due to upgrades? if so have LICENSE and NOTICE been upgraded appropriately? + does the tag/commit in the SCM contain reproducible sources?
