| Re: [rdf4j-dev] 5.0.0-M1 |
_______________________________________________Hi Havard,we have been able to validate the RDF4J 5.0 M1 build in our product and also to do some smoke testing.Here is our feedback:Code-Level
- Main change in our code-base was the removal of the Exception generic parameter from CloseableIteration
- For some algebra nodes we had to implement QueryModelNode#replaceChildNode and QueryModelNode#visitChildrent
- Some smaller changes, e.g. replacing Iterations.close(iter) with iter.close
Execution time:
- No compatibility issues discovered in quick smoke testing of our application
I noticed that the @Deprecated annotations are still present on the central interfaces (e.g. CloseableIteration). For myself - where I am using the Eclipse IDE - this means that I still have tons of deprecation warnings. Ideally for the next milestone build and the final 5.0 RDF4J release the deprecated annotations can be removed entirely.Another side question for RDF4J 5.0: to my knowledge RDF4J still uses HTTP client 4.5.x. In our application we have seen recently one limitation of the old http client version, namely that it does hot HTTP/2 (for which support is only added in the http client 5.x). We could solve this on the proxy level, but as we are doing a major release of RDF4J would it make sense to look into the http client as well? I suspect that the migration would not be too difficult, but haven't checked. Is this maybe already tracked and on the radar?Thanks again Havard for driving the RDF4J project.Best,AndreasAm Di., 22. Aug. 2023 um 14:23 Uhr schrieb Andreas Schwarte <aschwarte10@xxxxxxxxx>:Hi Havard,thanks a lot for this early milestone build.After my vacation I have now been able to follow up on this. We have tracked an internal task for the upcoming sprint to do a validation (+ quick smoke testing) of RDF4J 5.0 M1 in our product. I will report back the findings once the task is completed, likely within the next 2-3 weeks.Note: the RDF4J 5.0 timeline does not match the timeline for our next product release, so we cannot yet use the milestone in our main develop branch.Best,AndreasAm Do., 10. Aug. 2023 um 18:06 Uhr schrieb Håvard Ottestad via rdf4j-dev <rdf4j-dev@xxxxxxxxxxx>:Hi Everyone!_______________________________________________I've managed to publish the first milestone build of 5.0.0 (5.0.0-M1).If you develop a product on top of RDF4J you should try out the build and let us know if you run into any issues. Especially if it is due to code that has been removed. There will still be a lot of deprecation warnings for things that a not really deprecated anymore, some of these will be for code that might change slightly but in most of the cases it'll just be due to me not having removed the deprecation warnings.I ran into an issue with OSGI. I have no idea what is going on. Initially I thought it was due to upgrading some maven plugins. My latest theory was that it had something to do with the new collection factory which relies on both the 1.x and 3.x versions of MapDB. So far none of this has panned out and I still don't know what is broken. I found a workaround for the time being, running `mvn install` before maven assembly/package "fixes" the OSGI build error.If anyone knows anything about OSGI I would really appreciate some help: https://github.com/eclipse-rdf4j/rdf4j/issues/4744Cheers,Håvard
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev