Conversation
Contributor
JSLair
commented
Jun 17, 2022
JSLair
commented
- add all stuff for creating and checking SEDA 2.2 in sedalib (with a general mechanism to add other subversion if needed)
- add all stuff for managing SEDA 2.1 and SEDA 2.2, choose it in preferences and convert if possible an open work
- go for java 11 and review the README.md (no more specific droid, an option for SEDA2.2...)
- Add DataObjectProfile in BinaryDataObject and PhysicalDataObject - Add SEDA2Version, a SEDA 2 version management class, that make it possible to use different SEDA 2 version if: * only the ontology and the xsd declaration are different, not the messages structure * all used objects in the JVM are of the same SEDA version (global version) To be noticed: there is a very special function (SEDA2Version.convertToSeda2Version) implemented to convert a DataObjectPackage to another SEDA 2 version. This is mostly done to be used in interactive program like Resip. - Add a global mechanism for creating different versions of complex SedaMetadata with simple annotations in ComplexListType - Add SEDA 2.2 version of Content (mainly Agent), Event (LinkingAgentIdentifier) - Extend xsd schema validation for different SEDA versions (2.1 and 2.2) - Complete and review unit tests - Fix: - DataObjectPackage: a few small mistakes
- Add DataObjectProfile to BinaryDataObject and PhysicalDataObject structured editors - Add a SEDA version selector (2.1 or 2.2) * in preferences dialog, with conversion test thread of currently edited DataObjectPackage at validation * in preferences treatment context in config file - Add new XML tags translations and sample minimal subtags - Adapt check schema conformity menu labels with SEDA version - On file load, test if the used SEDA version was the same and ask to change the current used version to continue - Add an option for shell version S/sedaversion to define the SEDA subversion (1|2) - Fix: * take into account a few refactors of sedalib like seda21Validate changing to sedaSchemaValidate * reduce SonarLint issues in committed files
- set maven properties in poms - update launch4j version and clean parameters for java11 - fix the ReadMe for Java 11 version, getting rid of now useless specific droid compilation and add the sedaversion script option
- Replace the standard SEDA 2.2 XSD by the vitam one without abstracts - update maven-javadoc-plugin version to use in a proxified env without bug
laedanrex
approved these changes
Jul 21, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.