Skip to content

ST6RI-927 Automatically update metamodel and version fields for standard library releases#759

Merged
seidewitz merged 2 commits into
masterfrom
ST6RI-927
Jun 9, 2026
Merged

ST6RI-927 Automatically update metamodel and version fields for standard library releases#759
seidewitz merged 2 commits into
masterfrom
ST6RI-927

Conversation

@vytautas-astrauskas-sensmetry

@vytautas-astrauskas-sensmetry vytautas-astrauskas-sensmetry commented May 28, 2026

Copy link
Copy Markdown
Contributor

Adds a Java program called by Maven during the build that updates metamodel and version tags of the standard library as follows:

  1. If sysml.metadata-tag is set in pom.xml to METAMODEL_TAG, .meta.json's metamodel field will be set to https://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. The resource IRIs for usages will have its date updated to METAMODEL_TAG.

  2. If sysml.build-tag is set in pom.xml to BUILD_TAG, version and versionConstraint fields will get -dev.BUILD_TAG suffix. For example, having <sysml.build-tag>20260501</sysml.build-tag> will result in the following:

    "version": "2.1.0-dev.20260501",
    "usage": [
      {
        "resource": "https://www.omg.org/spec/KerML/20250201/Semantic-Library.kpar",
        "versionConstraint": "1.1.0-dev.20260501"
      },
    

For the 2026-05 release:

  • METAMODEL_TAG = 20250201 (no change from v1.0/2.0)
  • BUILD_TAG = 20260501

This 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.

@seidewitz seidewitz changed the title Set version and metamodel tags when building stdlib KPARs ST6RI-927 Automatically update metamodel and version fields for standard library releases May 28, 2026
@seidewitz seidewitz self-assigned this May 28, 2026
@seidewitz seidewitz added this to the 2026-05 milestone May 28, 2026

@seidewitz seidewitz left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As agreed for PR #760, the METAMODEL_TAG should remain 20250201. But you can leave the BUILD_TAG as 20260501.

@seidewitz

Copy link
Copy Markdown
Member

@vytautas-astrauskas-sensmetry
Also, please include the issue number (for this branch, ST6RI-759) in your commit messages.

…ding stdlib KPARs

Signed-off-by: Vytautas Astrauskas <vytautas.astrauskas@sensmetry.com>
@vytautas-astrauskas-sensmetry

Copy link
Copy Markdown
Contributor Author

As agreed for PR #760, the METAMODEL_TAG should remain 20250201. But you can leave the BUILD_TAG as 20260501.

Updated METAMODEL_TAG to the old date 20250201.

@vytautas-astrauskas-sensmetry

Copy link
Copy Markdown
Contributor Author

@vytautas-astrauskas-sensmetry Also, please include the issue number (for this branch, ST6RI-759) in your commit messages.

Added prefix ST6RI-927 (the issue number from JIRA) to the commit message.

@seidewitz

Copy link
Copy Markdown
Member

As agreed for PR #760, the METAMODEL_TAG should remain 20250201. But you can leave the BUILD_TAG as 20260501.

Updated METAMODEL_TAG to the old date 20250201.

The resource URIs for the usages in the .project.json files needs to be created using the METAMODEL_TAG (i.e, 20250201 for now ), not the BUILD_TAG.

@vytautas-astrauskas-sensmetry

Copy link
Copy Markdown
Contributor Author

As agreed for PR #760, the METAMODEL_TAG should remain 20250201. But you can leave the BUILD_TAG as 20260501.

Updated METAMODEL_TAG to the old date 20250201.

The resource URIs for the usages in the .project.json files needs to be created using the METAMODEL_TAG (i.e, 20250201 for now ), not the BUILD_TAG.

Fixed in 813c891

@seidewitz seidewitz self-requested a review June 9, 2026 16:24
@seidewitz seidewitz merged commit 6e3aa78 into master Jun 9, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants