"""
The following artifacts
could not be resolved: org.apache.jena:jena-fuseki-main:jar:tests:5.3.0
(absent): org.apache.jena:jena-fuseki-main:jar:tests:5.3.0 was not found in
https://repo.maven.apache.org/maven2 during a previous attempt.
"""

Because jena-fuseki-main/ wasn't built.

Clear out <LOCAL REPO>/org/apache/jena/jena-fuseki-main/5.3.0
and run the build with -DskipTests to first to create artifacts.

    Andy

On 16/01/2025 19:46, Marco Neumann wrote:
Ok makes sense Andy, I will try to remedy this with an old maschine in the
DMZ still on ipv4.

That said when skippen tests I get another error, surprisingly one
occurring in an integration test which seem to be not in skipping realm

[INFO] Apache Jena - Fuseki with GeoSPARQL Engine ......... SUCCESS [
  3.259 s]
[INFO] Apache Jena - Integration Testing .................. FAILURE [
  0.007 s]
[INFO] Apache Jena - Benchmark Suite ...................... SKIPPED
[INFO] Apache Jena - Benchmarks Shaded Jena 4.8.0 ......... SKIPPED
[INFO] Apache Jena - Benchmarks Shaded Jena 5.1.0 ......... SKIPPED
[INFO] Apache Jena - Benchmarks JMH ....................... 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 - BOM .................................. SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time:  01:17 min
[INFO] Finished at: 2025-01-16T18:35:55Z
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal on project jena-integration-tests: Could not
resolve dependencies for project
org.apache.jena:jena-integration-tests:jar:5.3.0: The following artifacts
could not be resolved: org.apache.jena:jena-fuseki-main:jar:tests:5.3.0
(absent): org.apache.jena:jena-fuseki-main:jar:tests:5.3.0 was not found in
https://repo.maven.apache.org/maven2 during a previous attempt. This
failure was cached in the local repository and resolution is not
reattempted until the update interval of central has elapsed or updates are
forced -> [Help 1]

Marco

On Thu, Jan 16, 2025 at 7:04 PM Andy Seaborne <a...@apache.org> wrote:

This is a test mishandling IPv6 addresses.

It is trying to find a non localhost IP address for host machine (i.e
not 127.0.0.1 or [::1]). It messes up on IPv6 addresses.

The mocking is testing that the Shiro setup for "localhost" works only
for "localhost". It does not affect runtime use.

      Andy

On 16/01/2025 15:20, Marco Neumann wrote:
I am getting a build error at

[INFO] Apache Jena - Fuseki Server Main ................... FAILURE [
10.748 s]

[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
0.049 s -- in org.apache.jena.fuseki.mod.metrics.TestModPrometheus
[INFO] Running org.apache.jena.fuseki.mod.shiro.TestModShiro
[ERROR] Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
0.107 s <<< FAILURE! -- in org.apache.jena.fuseki.mod.shiro.TestModShiro
[ERROR] org.apache.jena.fuseki.mod.shiro.TestModShiro.access_localhost --
Time elapsed: 0.005 s <<< ERROR!
org.apache.jena.atlas.web.HttpException: Bad URL:
http://2a01:4f9:3051:1bae:0:0:0:2%enp4s0:45605/public/ds?default
starting
at character 33
          at org.apache.jena.http.HttpLib.toRequestURI(HttpLib.java:361)
          at org.apache.jena.http.HttpLib.newGetRequest(HttpLib.java:439)
          at org.apache.jena.http.HttpRDF.execGetToInput(HttpRDF.java:163)
          at
org.apache.jena.http.HttpRDF.httpGetToStream(HttpRDF.java:133)
          at
org.apache.jena.http.HttpRDF.httpGetToStream(HttpRDF.java:128)
          at org.apache.jena.sparql.exec.http.GSP.GET(GSP.java:148)
          at

org.apache.jena.fuseki.mod.shiro.TestModShiro.attempt(TestModShiro.java:230)
          at

org.apache.jena.fuseki.mod.shiro.TestModShiro.attemptByAddr(TestModShiro.java:214)
          at

org.apache.jena.fuseki.mod.shiro.TestModShiro.attemptByAddr(TestModShiro.java:208)
          at

org.apache.jena.fuseki.mod.shiro.TestModShiro.access_localhost(TestModShiro.java:119)
          at java.base/java.lang.reflect.Method.invoke(Method.java:580)
          at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
          at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
Caused by: java.net.URISyntaxException: Malformed escape pair at index
33:
http://2a01:4f9:3051:1bae:0:0:0:2%enp4s0:45605/public/ds?default
          at java.base/java.net.URI$Parser.fail(URI.java:2995)
          at java.base/java.net.URI$Parser.scanEscape(URI.java:3123)
          at java.base/java.net.URI$Parser.scan(URI.java:3146)
          at java.base/java.net.URI$Parser.parseAuthority(URI.java:3287)
          at
java.base/java.net.URI$Parser.parseHierarchical(URI.java:3240)
          at java.base/java.net.URI$Parser.parse(URI.java:3196)
          at java.base/java.net.URI.<init>(URI.java:645)
          at org.apache.jena.http.HttpLib.toRequestURI(HttpLib.java:352)


Best,
Marco





On Thu, Jan 16, 2025 at 11:25 AM Andy Seaborne <a...@apache.org> wrote:

Hi,

Here is a vote on the first release candidate for
Apache Jena version 5.3.0.

==== Release Vote

This vote will be open until at least

       Tuesday 21th January 2025 at 08:00 UTC

Please vote to approve this release:

           [ ] +1 Approve the release
           [ ]  0 Don't care
           [ ] -1 Don't release, because ...

Everyone, not just committers, is invited to test and vote.
Please download and test the proposed release. See the checklist below.

Staging repository:

https://repository.apache.org/content/repositories/orgapachejena-1067

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/2303067d36

Git Commit Hash:
     2303067d362d6d69e52da0111ec6f1f23a252c8e

Git Commit Tag:
     jena-5.3.0

If you expect to check the release but the time limit does not work
for you, please email to let us know within the schedule above.

==== In this release

Issues in this release:

     https://s.apache.org/jena-5.3.0-issues

Jena 5.3.0 has changes in the structure of the Fuseki server, a new IRI
provider, together with a lot of clearup and simplification of Jena's
use of Apache Xerces.

==== Contributions

@Ostrzyciel has contributed several test cases for initialization
and also cleaning up of Jena's use of Apache Xerces-derived code for RDF
datatypes:

@OyvindLGjesdal has contrinbuted imporvement to the jena-text build for
java21->

@Aklakan has contributed support for timeouts in SPARQL Updates,
provided fixes for closing execution iterators, OpAsQuery, and for
NodeFmtLib.

Committers with PRs: rvesse, sszuev, kinow, arne-bdt, afs
and not forgetting @dependabot

==== Fuseki

The artifact jena-fuseki-main, which was the UI-less embedded simple
server, now has equivalent functionality, including UI, to the
Fuseki/webapp packaging.

The artifact jena-fuseki-server packages jena-fuseki-main with
dependencies and UI files into a single jar.

It should be a drop-in replacement. There is no functionality added or
removed; it is a better base for future development.

Fuseki/webapp packaging for the WAR file which will continue to be
produced but may not get all future Fuseki development features.

-------------------

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?







Reply via email to