ST6RI-927 Automatically update metamodel and version fields for standard library releases#759
Conversation
metamodel and version fields for standard library releases
|
@vytautas-astrauskas-sensmetry |
…ding stdlib KPARs Signed-off-by: Vytautas Astrauskas <vytautas.astrauskas@sensmetry.com>
ce897aa to
f2591f8
Compare
Updated |
Added prefix |
The resource URIs for the usages in the |
Fixed in 813c891 |
Adds a Java program called by Maven during the build that updates metamodel and version tags of the standard library as follows:
If
sysml.metadata-tagis set inpom.xmltoMETAMODEL_TAG,.meta.json'smetamodelfield will be set tohttps://www.omg.org/spec/SysML/METAMODEL_TAG. For example, having<sysml.metadata-tag>20250201</sysml.metadata-tag>will result in"metamodel": "https://www.omg.org/spec/SysML/20250201". Similarly, for KerML. TheresourceIRIs for usages will have its date updated toMETAMODEL_TAG.If
sysml.build-tagis set inpom.xmltoBUILD_TAG,versionandversionConstraintfields will get-dev.BUILD_TAGsuffix. For example, having<sysml.build-tag>20260501</sysml.build-tag>will result in the following:For the 2026-05 release:
METAMODEL_TAG = 20250201(no change from v1.0/2.0)BUILD_TAG = 20260501This PR also updates the version of SysML KPARs to 2.1 and the version of KerML KPARs to 1.1.
Note. This description has been edited based on the PR discussion and additional commit.