[jira] [Commented] (JENA-2266) convertLatLon swaps coordinates
[
https://issues.apache.org/jira/browse/JENA-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484490#comment-17484490
]
Claus Stadler commented on JENA-2266:
-
Hm I see.
So the safest approach to ending up with a JTS Geometry which works
out-of-the-box with e.g. leaflet via JTS' GeoJsonWriter or WktWriter is to to
force the SRS using
geometryWrapper.convert(SRS_URI.DEFAULT_WKT_CRS84).getParsingGeometry. At this
stage getXYGeometry should be the same - right? - Or is one of the geometry
getters preferred over the other?
It seems this issue can be closed as "not a bug".
> convertLatLon swaps coordinates
> ---
>
> Key: JENA-2266
> URL: https://issues.apache.org/jira/browse/JENA-2266
> Project: Apache Jena
> Issue Type: Bug
> Components: GeoSPARQL
>Affects Versions: Jena 4.3.2
>Reporter: Claus Stadler
>Priority: Major
> Attachments: image-2022-01-30-18-28-56-974.png
>
>
> The correct setting is that longitude corresponds to x-axis and latitude to
> y-axis, but in the code lat is passed for x and lon for y.
> {code:java}
> public class ConvertLatLon {
> public static final Literal toLiteral(double lat, double lon) {
> checkBounds(lat, lon);
> return WKTLiteralFactory.createPoint(lat, lon, SRS_URI.WGS84_CRS);
> }
> }
> {code}
> {code:java}
> public class WKTLiteralFactory {
> public static final Literal createPoint(Double x, Double y, String
> srsURI) {
> String tidyURI = tidySrsURI(srsURI);
> return ResourceFactory.createTypedLiteral(tidyURI + "POINT(" +
> reducePrecision(x) + " " + reducePrecision(y)
> + ")", WKTDatatype.INSTANCE);
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
Re: [VOTE] Apache Jena 4.4.0 RC2
+1 (binding) Thanks! Bruno On Mon, 31 Jan 2022 at 05:32, Andy Seaborne wrote: > Hi, > > Here is a vote on the release of Apache Jena 4.4.0. > This is the second proposed release candidate. > > == Changes RC1 -> RC2: > > JENA-2265 (Fuseki UI) > Use window.location.pathname for the Fuseki URL, fix Vue publicPath > > JENA-2264 (jena-core) > Improve Resource.getProperty(,lang). Include TestStandardModels. > > JENA-2262 (TestAdmin) > Skip to the end of response streams > > == > > The deadline is > > Wednesday, 2nd February 2022 at 19: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 > > > > The main item in this release is the updated Fuseki UI thanks to work by > Bruno. > > This can be tested by downloading > "org/apache/jena/apache-jena-fuseki/4.4.0/" zip or tar.gz from the > staging repository: > https://repository.apache.org/content/repositories/orgapachejena-1050 > > > > As general maintenance for the project: > > Apache log4j is at 2.17.1 > Apache Lucene: is updated to 8.10.1 -> 8.11.1 > Titanium JSON-LD updated 1.1.0 -> 1.2.0 > > as well as all other dependences being checked for updates. > > To get valid javadoc, the build was done with Java17 cross-compiling to > 11. A dry-run with java11 was done to check that no > Java17 library calls had crept in. > > The war file for Fuseki is no longer in the apache-jena-fuseki download. > Instead, it is available from the downloads page (links to be updated > when the release happens). > > Proposed: > https://dist.apache.org/repos/dist/dev/jena/binaries/ > > The Fuseki war file does not work in Tomcat10 due to the javax->jakarta > switchover. In theory, the Tomcat provided converter should work. > https://tomcat.apache.org/download-migration.cgi > > > This release includes the version of the TDB2 xloader used to load 16.6B > triples (WikiData all) into TDB2 and loading truthy (6B) on modest > hardware. Thanks to Marco, Lorenz and Øyvind for running Wikidata load > trails. > > Fuseki: serviceUpload is no longer added in a default configuration. > This is not SPARQL GSP. GSP (POST/PUT) does accept HTML file uploads as > well as POST/PUT by content-type. > > 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-1050 > > 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/582e4082ef > > Git Commit Hash: >582e4082ef53012527e686dd46cbeeb4b364f5fe > > Git Commit Tag: >jena-4.4.0 > > This vote will be open until at least > > Wednesday, 2nd February 2022 at 19: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? >
[jira] [Commented] (JENA-2266) convertLatLon swaps coordinates
[
https://issues.apache.org/jira/browse/JENA-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484418#comment-17484418
]
Greg Albiston commented on JENA-2266:
-
Longitude is indeed the X axis and latitude is the Y axis. However, the SRS
EPSG 4326 (referenced by {{{}SRS_URI.WGS84_CRS{}}}) used for WGS84 reverses the
axis order when encoding to latitude/longitude. The SRS OGC CRS84 has the axis
order longitude/latitude.
The produced Point literal conforms with the axis order, if it is perhaps
somewhat confusing in the naming of function parameters.
An example of this is provided on page 17 of the GeoSPARQL standard.
!image-2022-01-30-18-28-56-974.png!
> convertLatLon swaps coordinates
> ---
>
> Key: JENA-2266
> URL: https://issues.apache.org/jira/browse/JENA-2266
> Project: Apache Jena
> Issue Type: Bug
> Components: GeoSPARQL
>Affects Versions: Jena 4.3.2
>Reporter: Claus Stadler
>Priority: Major
> Attachments: image-2022-01-30-18-28-56-974.png
>
>
> The correct setting is that longitude corresponds to x-axis and latitude to
> y-axis, but in the code lat is passed for x and lon for y.
> {code:java}
> public class ConvertLatLon {
> public static final Literal toLiteral(double lat, double lon) {
> checkBounds(lat, lon);
> return WKTLiteralFactory.createPoint(lat, lon, SRS_URI.WGS84_CRS);
> }
> }
> {code}
> {code:java}
> public class WKTLiteralFactory {
> public static final Literal createPoint(Double x, Double y, String
> srsURI) {
> String tidyURI = tidySrsURI(srsURI);
> return ResourceFactory.createTypedLiteral(tidyURI + "POINT(" +
> reducePrecision(x) + " " + reducePrecision(y)
> + ")", WKTDatatype.INSTANCE);
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (JENA-2266) convertLatLon swaps coordinates
[
https://issues.apache.org/jira/browse/JENA-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Albiston updated JENA-2266:
Attachment: image-2022-01-30-18-28-56-974.png
> convertLatLon swaps coordinates
> ---
>
> Key: JENA-2266
> URL: https://issues.apache.org/jira/browse/JENA-2266
> Project: Apache Jena
> Issue Type: Bug
> Components: GeoSPARQL
>Affects Versions: Jena 4.3.2
>Reporter: Claus Stadler
>Priority: Major
> Attachments: image-2022-01-30-18-28-56-974.png
>
>
> The correct setting is that longitude corresponds to x-axis and latitude to
> y-axis, but in the code lat is passed for x and lon for y.
> {code:java}
> public class ConvertLatLon {
> public static final Literal toLiteral(double lat, double lon) {
> checkBounds(lat, lon);
> return WKTLiteralFactory.createPoint(lat, lon, SRS_URI.WGS84_CRS);
> }
> }
> {code}
> {code:java}
> public class WKTLiteralFactory {
> public static final Literal createPoint(Double x, Double y, String
> srsURI) {
> String tidyURI = tidySrsURI(srsURI);
> return ResourceFactory.createTypedLiteral(tidyURI + "POINT(" +
> reducePrecision(x) + " " + reducePrecision(y)
> + ")", WKTDatatype.INSTANCE);
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
Re: UI jar
Our UI is in a separate module but the idea is similar:
By setting
vue.config.js:
outputDir: 'target/classes/org.apache.jena.fuseki.ui'
the Vue build goes into that location during frontend-maven-plugin which
runs before the jar plugin.
jena-fuseki-webapp can unpack that in phase=generate-sources using
maven-dependency-plugin.
jena-fuseki-war is only the .war generation. Maybe jena-fuseki-webapp
can be slimmed down by extracting the server support functions and the
UI operations as Fuseki Modules leaving the war/webapp specific start-up.
Andy
BTW isn't the docs for maven-war-plugin but appears to work.
IIRC there is some reason not to rename the output, maybe if uploading
to a managed maven repo. But if producing locally that's not important.
On 30/01/2022 08:30, Martynas Jusevičius wrote:
Not a multi-module build, but this is how we publish WAR + JAR:
https://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#attachClasses
org.apache.maven.plugins
maven-war-plugin
3.2.3
ROOT
target/ROOT
true
true
The dependency then looks like this (using "classes" which is the
default classifier):
${project.groupId}
client
3.1.8-SNAPSHOT
classes
${project.groupId}
client
3.1.8-SNAPSHOT
war
On Sat, Jan 29, 2022 at 12:01 PM Andy Seaborne wrote:
On 28/01/2022 23:43, Bruno Kinoshita wrote:
Build passed from tag, with:
Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
Maven home: /opt/apache-maven-3.8.2
Java version: 11.0.13, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-96-generic", arch: "amd64", family: "unix"
Looked inside .jar and .tar.gz files in the dist area (binaries and
sources), and everything looks good (checked the new -ui module, didn't
find node_modules or any other unnecessary files). The jena-fuseki-ui
module creates a jar that only contains metadata. Maybe we could skip
releasing it in the future? I think as it is, it should be available in the
Maven repository as a jar dependency for users, even though it's not usable
in any way in Java I think.
We can make it a POM artifact then no jar generated.
Or.
Use the jar to deliver the UI files.
They can be served from the jar. No files on disk. No copying from
../jena-fuseki-ui/target/dist/ during jena-fuseki-webapp.
The Jetty content-serving servlet takes URL string - and a jar is
accessed with URL .
The path can be determined automatically by looking up the path-in-jar
as the server starts. The files are places under "src/main/resources/"
I have, experimentally, done a Fuseki module for the UI. This is a
drop-in to FusekiMain (ditto the admin functions as a drop-in).
These will convert the standalone Fuseki server to being a Fuseki/Main +
Mod_UI + Mod_Admin, not a webapp+Jetty to run it.
Good for docker.
What I haven't looked at is how to get the WAR file setup with this
change of build. A war file unpacks its contents to disk and has jars in
WEB-INF/lib which is the webapps classpath. "Should" work if start-up
can set the location of static content.
An alternative is have a prepare step in the build to unpack the jar.
Anyone got experience of delivering JS into a WAR file in a multi-module
build?
Andy
Re: [VOTE] Apache Jena 4.4.0 RC2
+1 ps: on the new fuseki UI it's not prompting for username and password even if set at load time. only when creating a dataset the login prompt shows up. it's not intuitive. if not logged in it still shows the UI but one can't create a dataset [image: image.png] On Sun, Jan 30, 2022 at 4:39 PM Andy Seaborne wrote: > +1 (binding) > > On 30/01/2022 16:32, Andy Seaborne wrote: > > Hi, > > > > Here is a vote on the release of Apache Jena 4.4.0. > > This is the second proposed release candidate. > > > > == Changes RC1 -> RC2: > > > > JENA-2265 (Fuseki UI) > > Use window.location.pathname for the Fuseki URL, fix Vue publicPath > > > > JENA-2264 (jena-core) > > Improve Resource.getProperty(,lang). Include TestStandardModels. > > > > JENA-2262 (TestAdmin) > > Skip to the end of response streams > > > > == > > > > The deadline is > > > > Wednesday, 2nd February 2022 at 19:00 UTC. > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] 0 Don't care > > [ ] -1 Don't release, because ... > -- --- Marco Neumann KONA
Re: [VOTE] Apache Jena 4.4.0 RC2
+1 (binding) On 30/01/2022 16:32, Andy Seaborne wrote: Hi, Here is a vote on the release of Apache Jena 4.4.0. This is the second proposed release candidate. == Changes RC1 -> RC2: JENA-2265 (Fuseki UI) Use window.location.pathname for the Fuseki URL, fix Vue publicPath JENA-2264 (jena-core) Improve Resource.getProperty(,lang). Include TestStandardModels. JENA-2262 (TestAdmin) Skip to the end of response streams == The deadline is Wednesday, 2nd February 2022 at 19:00 UTC. Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ...
[VOTE] Apache Jena 4.4.0 RC2
Hi, Here is a vote on the release of Apache Jena 4.4.0. This is the second proposed release candidate. == Changes RC1 -> RC2: JENA-2265 (Fuseki UI) Use window.location.pathname for the Fuseki URL, fix Vue publicPath JENA-2264 (jena-core) Improve Resource.getProperty(,lang). Include TestStandardModels. JENA-2262 (TestAdmin) Skip to the end of response streams == The deadline is Wednesday, 2nd February 2022 at 19: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 The main item in this release is the updated Fuseki UI thanks to work by Bruno. This can be tested by downloading "org/apache/jena/apache-jena-fuseki/4.4.0/" zip or tar.gz from the staging repository: https://repository.apache.org/content/repositories/orgapachejena-1050 As general maintenance for the project: Apache log4j is at 2.17.1 Apache Lucene: is updated to 8.10.1 -> 8.11.1 Titanium JSON-LD updated 1.1.0 -> 1.2.0 as well as all other dependences being checked for updates. To get valid javadoc, the build was done with Java17 cross-compiling to 11. A dry-run with java11 was done to check that no Java17 library calls had crept in. The war file for Fuseki is no longer in the apache-jena-fuseki download. Instead, it is available from the downloads page (links to be updated when the release happens). Proposed: https://dist.apache.org/repos/dist/dev/jena/binaries/ The Fuseki war file does not work in Tomcat10 due to the javax->jakarta switchover. In theory, the Tomcat provided converter should work. https://tomcat.apache.org/download-migration.cgi This release includes the version of the TDB2 xloader used to load 16.6B triples (WikiData all) into TDB2 and loading truthy (6B) on modest hardware. Thanks to Marco, Lorenz and Øyvind for running Wikidata load trails. Fuseki: serviceUpload is no longer added in a default configuration. This is not SPARQL GSP. GSP (POST/PUT) does accept HTML file uploads as well as POST/PUT by content-type. 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-1050 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/582e4082ef Git Commit Hash: 582e4082ef53012527e686dd46cbeeb4b364f5fe Git Commit Tag: jena-4.4.0 This vote will be open until at least Wednesday, 2nd February 2022 at 19: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?
[jira] [Resolved] (JENA-2265) UI: fix Fuseki URL's when using the UI in Tomcat
[
https://issues.apache.org/jira/browse/JENA-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-2265.
-
Resolution: Fixed
> UI: fix Fuseki URL's when using the UI in Tomcat
>
>
> Key: JENA-2265
> URL: https://issues.apache.org/jira/browse/JENA-2265
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
>Affects Versions: Jena 4.3.2
>Reporter: Bruno P. Kinoshita
>Assignee: Bruno P. Kinoshita
>Priority: Blocker
> Fix For: Jena 4.4.0
>
>
> Context:
> {color:#8c8c8c}[https://lists.apache.org/thread/z3gb5w95oc7c4v0g1jpk9jkxm0l4b7lh]{color}
> The UI was creating URL's for Fuseki starting with `/` without taking into
> consideration the paths when deployed on Tomcat.
> Also, the static resources were not being retrieved from correct URL.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (JENA-2265) UI: fix Fuseki URL's when using the UI in Tomcat
[
https://issues.apache.org/jira/browse/JENA-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-2265:
Priority: Blocker (was: Major)
> UI: fix Fuseki URL's when using the UI in Tomcat
>
>
> Key: JENA-2265
> URL: https://issues.apache.org/jira/browse/JENA-2265
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
>Affects Versions: Jena 4.3.2
>Reporter: Bruno P. Kinoshita
>Assignee: Bruno P. Kinoshita
>Priority: Blocker
> Fix For: Jena 4.4.0
>
>
> Context:
> {color:#8c8c8c}[https://lists.apache.org/thread/z3gb5w95oc7c4v0g1jpk9jkxm0l4b7lh]{color}
> The UI was creating URL's for Fuseki starting with `/` without taking into
> consideration the paths when deployed on Tomcat.
> Also, the static resources were not being retrieved from correct URL.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (JENA-2265) UI: fix Fuseki URL's when using the UI in Tomcat
[
https://issues.apache.org/jira/browse/JENA-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484339#comment-17484339
]
ASF subversion and git services commented on JENA-2265:
---
Commit 473bf297cee81559ab4ac7ecb8dff50871e16769 in jena's branch
refs/heads/main from Bruno P. Kinoshita
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=473bf29 ]
JENA-2265: Use window.location.pathname for the Fuseki URL, fix Vue publicPath
> UI: fix Fuseki URL's when using the UI in Tomcat
>
>
> Key: JENA-2265
> URL: https://issues.apache.org/jira/browse/JENA-2265
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
>Affects Versions: Jena 4.3.2
>Reporter: Bruno P. Kinoshita
>Assignee: Bruno P. Kinoshita
>Priority: Major
> Fix For: Jena 4.4.0
>
>
> Context:
> {color:#8c8c8c}[https://lists.apache.org/thread/z3gb5w95oc7c4v0g1jpk9jkxm0l4b7lh]{color}
> The UI was creating URL's for Fuseki starting with `/` without taking into
> consideration the paths when deployed on Tomcat.
> Also, the static resources were not being retrieved from correct URL.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (JENA-2265) UI: fix Fuseki URL's when using the UI in Tomcat
[
https://issues.apache.org/jira/browse/JENA-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484340#comment-17484340
]
ASF subversion and git services commented on JENA-2265:
---
Commit 483635bebd1cb76905f3bc7faec1a49519fb08d8 in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=483635b ]
Merge pull request #1182 from kinow/fix-ui-tomcat
JENA-2265: Use window.location.pathname for the Fuseki URL, fix Vue p…
> UI: fix Fuseki URL's when using the UI in Tomcat
>
>
> Key: JENA-2265
> URL: https://issues.apache.org/jira/browse/JENA-2265
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
>Affects Versions: Jena 4.3.2
>Reporter: Bruno P. Kinoshita
>Assignee: Bruno P. Kinoshita
>Priority: Major
> Fix For: Jena 4.4.0
>
>
> Context:
> {color:#8c8c8c}[https://lists.apache.org/thread/z3gb5w95oc7c4v0g1jpk9jkxm0l4b7lh]{color}
> The UI was creating URL's for Fuseki starting with `/` without taking into
> consideration the paths when deployed on Tomcat.
> Also, the static resources were not being retrieved from correct URL.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
Re: [VOTE] Apache Jena 4.4.0 RC1
Definitely, the UI work is very much appreciated and might improve the RDF user experience with fuseki overall. Will be good to have a reference to point to and a resource for the Apache Jena documentation. Best, Marco On Sun, Jan 30, 2022 at 1:43 AM Bruno Kinoshita wrote: > Hi Marco, > > Is there a write-up or a research paper on the new UI work by Bruno for > > reference? > > > > Nothing yet, sorry. > > I thought about that. My initial plan was to convert it first to Vue, > address any security issues in the update, then add tests, and finally > suggest some user interface/user experience improvements. > > In my mind that would give a nice paper or blog post. I wrote some tweets, > made one UI/UX improvement to the table in the dataset info that should be > included in this release, and have some notes lying around. > > Might try to write a blog post or maybe somewhere else like lwn or similar > that would receive some feedback on UI/UX & JS benefits... a good way to > showcase what was done, get some feedback (hopefully constructive) and > maybe some readers interested in participating too. > > Cheers > Bruno > > On Sun, 30 Jan 2022 at 01:30, Marco Neumann > wrote: > > > Thanks Andy. > > > > [ x ] +1 Approve the release > > > > FYI It now works best for me to perform a git reset --hard before the > git > > pull to get all the latest updates into the local version of the > > repository. > > > > BUILD SUCCESS Total time: 06:46 min > > Apache Maven 3.8.4 > > openjdk version 17.0.1 > > Ubuntu 20.04.3 LTS > > > > Is there a write-up or a research paper on the new UI work by Bruno for > > reference? > > > > Marco > > > > On Fri, Jan 28, 2022 at 6:53 PM Andy Seaborne wrote: > > > > > Hi, > > > > > > Here is a vote on the release of Apache Jena 4.4.0. > > > This is the first proposed release candidate. > > > > > > The deadline is > > > > > > Monday, 31st January December 2021 at 19: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 > > > > > > > > > > > > The main item in this release is the updated Fuseki UI thanks to work > by > > > Bruno. > > > > > > This can be tested by downloading > > > "org/apache/jena/apache-jena-fuseki/4.4.0/" zip or tar.gz from the > > > staging repository: > > > https://repository.apache.org/content/repositories/orgapachejena-1049 > > > > > > > > > > > > As general maintenance for the project: > > > > > > Apache log4j is at 2.17.1 > > > Apache Lucene: is updated to 8.10.1 -> 8.11.1 > > > Titanium JSON-LD updated 1.1.0 -> 1.2.0 > > > > > > as well as all other dependences being checked for updates. > > > > > > To get valid javadoc, the build was done with Java17 cross-compiling to > > > 11. A dry-run with java11 was done to check no > Java17 > > > library calls had crept in. > > > > > > The war file for Fuseki is no longer in the apache-jena-fuseki > download. > > > Instead, it is available from the downloads page (links to be updated > > > when the release happens). > > > https://dist.apache.org/repos/dist/dev/jena/binaries/ > > > > > > The Fuseki war file does not work in Tomcat10 due to the javax->jakarta > > > switchover. In theory, the Tomcat provided converter should work. > > > https://tomcat.apache.org/download-migration.cgi > > > > > > > > > This release includes the versions of the TDB2 xloader used to load > > > 16.6B triples (WikiData all) into TDB2 and loading truthy on modest > > > hardware. Thanks to Marco, Lorenz and Øyvind for running Wikidata load > > > trails. > > > > > > Fuseki: serviceUpload is no longer added in a default configuration. > > > This is not SPARQL GSP. GSP (POST/PUT) does accept HTML file uploads as > > > well as POST/PUT by content-type. > > > > > > 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-1049 > > > > > > 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/80c61f2d40 > > > > > > Git Commit Hash: > > >80c61f2d405e8b1fff74eb6ff72949fdc7718000 > > > > > > Git Commit Tag: > > >jena-4.4.0 > > > > > > This vote will be open until at least > > > > > > Monday, 31st January December 2021 at 19: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 needed: > > > > > > + are the GPG signatures fine? > > > + are the checksums correct? > > > + is there a source archive? > > > + can the source archive be
[jira] [Resolved] (JENA-2264) Tests of Resource.getProperty(Property, lang) not being run.
[
https://issues.apache.org/jira/browse/JENA-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-2264.
-
Resolution: Fixed
> Tests of Resource.getProperty(Property, lang) not being run.
>
>
> Key: JENA-2264
> URL: https://issues.apache.org/jira/browse/JENA-2264
> Project: Apache Jena
> Issue Type: Improvement
> Components: Core
>Affects Versions: Jena 4.3.2
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Reported with [comment on commit
> d761b735d9|https://github.com/apache/jena/commit/d761b735d9de4729ced6d16cd9676044b012fd13#r65049377].
> # Suite not being run.
> # Statements not being added to the model.
> # assertEquals is testing the statement not the lang.
> # Code being tested in {{ResourceImpl}} needs to explicitly code iterators.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (JENA-2264) Tests of Resource.getProperty(Property, lang) not being run.
[
https://issues.apache.org/jira/browse/JENA-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-2264:
Fix Version/s: Jena 4.4.0
> Tests of Resource.getProperty(Property, lang) not being run.
>
>
> Key: JENA-2264
> URL: https://issues.apache.org/jira/browse/JENA-2264
> Project: Apache Jena
> Issue Type: Improvement
> Components: Core
>Affects Versions: Jena 4.3.2
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 4.4.0
>
>
> Reported with [comment on commit
> d761b735d9|https://github.com/apache/jena/commit/d761b735d9de4729ced6d16cd9676044b012fd13#r65049377].
> # Suite not being run.
> # Statements not being added to the model.
> # assertEquals is testing the statement not the lang.
> # Code being tested in {{ResourceImpl}} needs to explicitly code iterators.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (JENA-2264) Tests of Resource.getProperty(Property, lang) not being run.
[
https://issues.apache.org/jira/browse/JENA-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484316#comment-17484316
]
ASF subversion and git services commented on JENA-2264:
---
Commit 7050d0a2ed9f469b8ad8de8a2d9c84fde6f03030 in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=7050d0a ]
JENA-2264: Improve Resource.getProperty(,lang). Include TestStandardModels.
> Tests of Resource.getProperty(Property, lang) not being run.
>
>
> Key: JENA-2264
> URL: https://issues.apache.org/jira/browse/JENA-2264
> Project: Apache Jena
> Issue Type: Improvement
> Components: Core
>Affects Versions: Jena 4.3.2
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Reported with [comment on commit
> d761b735d9|https://github.com/apache/jena/commit/d761b735d9de4729ced6d16cd9676044b012fd13#r65049377].
> # Suite not being run.
> # Statements not being added to the model.
> # assertEquals is testing the statement not the lang.
> # Code being tested in {{ResourceImpl}} needs to explicitly code iterators.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (JENA-2264) Tests of Resource.getProperty(Property, lang) not being run.
[
https://issues.apache.org/jira/browse/JENA-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484317#comment-17484317
]
ASF subversion and git services commented on JENA-2264:
---
Commit 69d2b7f2940ef280cf8cdaf6f7d9b1f4cd731781 in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=69d2b7f ]
Merge pull request #1181 from afs/property-lang
JENA-2264: Improve Resource.getProperty(,lang). Include TestStandardModels.
> Tests of Resource.getProperty(Property, lang) not being run.
>
>
> Key: JENA-2264
> URL: https://issues.apache.org/jira/browse/JENA-2264
> Project: Apache Jena
> Issue Type: Improvement
> Components: Core
>Affects Versions: Jena 4.3.2
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Reported with [comment on commit
> d761b735d9|https://github.com/apache/jena/commit/d761b735d9de4729ced6d16cd9676044b012fd13#r65049377].
> # Suite not being run.
> # Statements not being added to the model.
> # assertEquals is testing the statement not the lang.
> # Code being tested in {{ResourceImpl}} needs to explicitly code iterators.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
Re: UI jar
Not a multi-module build, but this is how we publish WAR + JAR:
https://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#attachClasses
org.apache.maven.plugins
maven-war-plugin
3.2.3
ROOT
target/ROOT
true
true
The dependency then looks like this (using "classes" which is the
default classifier):
${project.groupId}
client
3.1.8-SNAPSHOT
classes
${project.groupId}
client
3.1.8-SNAPSHOT
war
On Sat, Jan 29, 2022 at 12:01 PM Andy Seaborne wrote:
>
>
>
> On 28/01/2022 23:43, Bruno Kinoshita wrote:
> > Build passed from tag, with:
> >
> >
> > Apache Maven 3.8.2 (ea98e05a04480131370aa0c110b8c54cf726c06f)
> > Maven home: /opt/apache-maven-3.8.2
> > Java version: 11.0.13, vendor: Ubuntu, runtime:
> > /usr/lib/jvm/java-11-openjdk-amd64
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "5.4.0-96-generic", arch: "amd64", family: "unix"
> >
> >
> > Looked inside .jar and .tar.gz files in the dist area (binaries and
> > sources), and everything looks good (checked the new -ui module, didn't
> > find node_modules or any other unnecessary files). The jena-fuseki-ui
> > module creates a jar that only contains metadata. Maybe we could skip
> > releasing it in the future? I think as it is, it should be available in the
> > Maven repository as a jar dependency for users, even though it's not usable
> > in any way in Java I think.
>
> We can make it a POM artifact then no jar generated.
>
> Or.
>
> Use the jar to deliver the UI files.
>
> They can be served from the jar. No files on disk. No copying from
> ../jena-fuseki-ui/target/dist/ during jena-fuseki-webapp.
>
> The Jetty content-serving servlet takes URL string - and a jar is
> accessed with URL .
>
> The path can be determined automatically by looking up the path-in-jar
> as the server starts. The files are places under "src/main/resources/"
>
> I have, experimentally, done a Fuseki module for the UI. This is a
> drop-in to FusekiMain (ditto the admin functions as a drop-in).
>
> These will convert the standalone Fuseki server to being a Fuseki/Main +
> Mod_UI + Mod_Admin, not a webapp+Jetty to run it.
>
> Good for docker.
>
> What I haven't looked at is how to get the WAR file setup with this
> change of build. A war file unpacks its contents to disk and has jars in
> WEB-INF/lib which is the webapps classpath. "Should" work if start-up
> can set the location of static content.
> An alternative is have a prepare step in the build to unpack the jar.
>
> Anyone got experience of delivering JS into a WAR file in a multi-module
> build?
>
> Andy
