-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade rdf-toolkit and Java #373
Comments
Some discussion is happening w.r.t. risks. A comment will come when that's done being updated. |
Risks have been updated. |
Requirement 1 was revised to say we should upgrade to at least Java 11, not necessarily exactly Java 11. |
The repository version noted in this commit does not currently catch subdirectories' Turtle files, so a follow-on patch will update the repository pointer. References: * #373
References: * casework/CASE-Utilities-Python#37 * #373
The version of rdf-toolkit run by the pre-commit hook now handles an RDF list differently than the prior version of rdf-toolkit. This commit is a mechanically-produced result. References: * #373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
The solution is posted, and interestingly |
* ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * #373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
The initial solution's scope has been narrowed on encountering an issue with |
Something the CASE OC should address is whether the CASE retrieval of
|
This prevents a potential build failure scenario where rdf-toolkit issues a release and suddenly all CI pinned to 1.11.0's SHA-512 fails. References: * #373 Reported-by: Paul Brandt <paul@brandt.name> Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * #373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch removes all handling of rdf-toolkit.jar from the CASE ontology repository. UCO had adopted CASE's rdf-toolkit retrieval in version 0.7.0, and now UCO Issue 373 will be upgrading the retrieval process. This patch handles delegation of rdf-toolkit provisioning. A follow-on patch will handle the rdf-toolkit and Java upgrade that is the focus of UCO Issue 373. References: * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
The version of rdf-toolkit run by the pre-commit hook now handles an RDF list differently than the prior version of rdf-toolkit. This commit is a mechanically-produced result. References: * #373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov> (cherry picked from commit ab0aff8) (cherry picked from commit a77e4e9)
Revisions to the Java setup match UCO commit `efce5c1`. References: * ucoProject/UCO@efce5c1 * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Revisions to the Java setup match UCO commit `efce5c1`. References: * ucoProject/UCO@efce5c1 * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
On starting testing-review of the implementation, I realized CASE would fall out of sync in Java support if it was not upgraded as part of this ticket. Due to needing to synchronize dependency of a core maintenance technology (a programming language version), this UCO issue now spans its implementation responsibility downstream into CASE. If this is a significant concern before opening for a Solutions Approval vote, please provide feedback. |
@ajnelson-nist : I didn't pay sufficient attention, and assumed that this applied to both UCO and CASE. I wouldn't call the Java and toolkit upgrade a significant concern for CASE, but we need to appropriately communicate this to the CASE community. So unless the CASE community was already informed simultaneously with UCO, I'd suggest to distribute this to the CASE community as a CASE vote for next CD-OC. |
@plbt5 - this was announced to the CASE and UCO Ontology Committees simultaneously. |
No effects were observed on Make-managed files. References: * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
A follow-on patch will regenerate Make-managed files. References: * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
PR 398 has had its review checklist completed. |
No changes were observed in Make-managed files. References: * [ONT-465] typo in ttl file * ucoProject/UCO#373 * ucoProject/UCO#380 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No changes were observed in Make-managed files. References: * [ONT-465] typo in ttl file * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
A follow-on patch will regenerate Make-managed files. References: * [ONT-465] typo in ttl file * ucoProject/UCO#373 * ucoProject/UCO#380 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * [ONT-465] typo in ttl file * ucoProject/UCO#373 * ucoProject/UCO#380 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No changes were observed in Make-managed files. References: * [ONT-465] typo in ttl file * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch incorporates all changes UCO adopted for resolution of its Issue 373. References: ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Background
Requirements
Requirement 1
The CI currently uses rdf-toolkit version 1.8, but version 1.10 is available. UCO should upgrade rdf-toolkit to version 1.10 and in turn upgrade to at least Java 11 (minimum requirement for using rdf-toolkit 1.10).
Risk / Benefit analysis
Benefits
UCO's CI will be utilizing the latest version of rdf-toolkit. Additionally, JRE 8 is end-of-life.
Risks
rdf-toolkit
compatibility with Javas > 11.Competencies demonstrated
Competency 1
N/A
Solution suggestion
lib/Makefile
and recorded SHA2-512 hash.rdf-toolkit
within CASE to use UCO as imported as a submodule. This is an expansion of responsibility of a UCO issue, creeping into CASE, but is seen as necessary to keep a shared technology synchronized.Coordination
develop
develop
The text was updated successfully, but these errors were encountered: