Hi Sebastian,
We discussed this on the tech call this morning and we are proposing a version branch. Yev will create a pull request which can then be merged into master after branching the 2.1 version of the code. All – If anyone disagrees with this approach, please reply to the mail list. Regards, Gary From: Schuberth, Sebastian [mailto:[email protected]] Sent: Wednesday, January 11, 2017 12:00 AM To: Yev Bronshteyn; Gary O'Neall; [email protected] Subject: RE: SPDX Tools+Jena 3.1.1 Maybe not a fork, but just a new major version? I.e., maintain the current version in a separate branch in the repository, and “master” in the same repository will hold the Java 8 version? Regards, Sebastian From: [email protected] [mailto:[email protected]] On Behalf Of Yev Bronshteyn Sent: Tuesday, January 10, 2017 21:34 To: Gary O'Neall <[email protected]>; [email protected] Subject: SPDX Tools+Jena 3.1.1 So as I was investigating why I was having build issues after refactoring the java tools to use Jena 3.1.1, I learned that Jena 3 supports Java 8 only – it’s not mentioned in any of the readmes, just on the download page and in the parent POM. I think the update is still worth doing because there are features to be gained (TDB support for building up and querying large datasets from multiple SPDX files, Sparql 1.1, allowing for recursive language – think nested license expressions), etc. However, I think we’re looking at a fork here. Yev
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
