Re: Preparing for Jena5 - API deprecations

[Andrii Berezovskyi]

Hello Andy,

May I ask if there is any impact on the non-Fuseki users of Jena in regard to 
the planned javax.* -> jakarata.* migration?

–Andrew.

On 3 Jul 2023, at 14:57, Andy Seaborne  wrote:

So far we have:

1/ Java21 is due to be released September 2023 and be a LTS release.
2/ javax.* -> jakarata.*
3/ Drop a separate JSON-LD 1.0 subsystem.
4/ Term graphs

One more thing I'd like to suggest for Jena5 is simplification. Look for 
code/features that are now out of date because of where the standards have gone.

Two are:

A/ LiteralLabel

It may be possible to merge this Node_Literal itself which, together with 
generally simplifying the Node hierarchy, makes the system
There are what look like matters from RDF 1.0 WG in the code; RDF 1.1 makes RDF 
Terms simpler and clearer.

While this is in an "impl" package, it also features in some Model API calls.

B/ The "is well formed" flag ... also called "isXML" in some places at the node 
level despite the fact it is used for things other than XML. This does not need 
to be done when creating Node_Literals.

With term graphs, and parsing, value evaluations checking isn't required all 
the time but it adds costs to the critical path.

There is a control
 JenaParameters.enableEagerLiteralValidation
which is false and which controls how to respond to bad literals.


To allow for A and B, I'd like to deprecate API calls that involve them. It may 
turn out some parts need to be kept - I've only done an initial pass over the 
code - but I think it is better to warn now and not simply put in changes at 
Jena5 with no advance notice.

   Andy

Re: [VOTE] Apache Jena 4.5.0 RC1

[Andrii Berezovskyi]

Hello,

We didn't go through the checklist but instead switched Eclipse Lyo to use Jena 
4.5.0 from the staging repo [1] and all tests pass and a few downstream apps 
also seem to work fine. Thank you for your work!

+1 (non-committer)

/Andrew

[1] 
https://github.com/eclipse/lyo/commit/b03947d66c98f56cad199d2cbeb4348bf889ad82

On 2022-05-01, at 17:18, Andy Seaborne 
mailto:a...@apache.org>> wrote:

Hi,

Here is a vote on the release of Apache Jena 4.5.0.
This is the first release candidate.

The deadline is

   Wednesday, 4th May 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

* New, faster, streaming, more robust JSON result set reader.

* Switch to JSON-LD 1.1 as the JSON-LD default.

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.

 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-1052

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):91c399148f
 https://github.com/apache/jena/commit/91c399148f

Git Commit Hash:
 91c399148f4f94c19517a88eb8c85db83fdb1342

Git Commit Tag:
 jena-4.5.0

This vote will be open until at least

   Wednesday, 4th May 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?