Conversation
Signed-off-by: Vytautas Astrauskas <[email protected]>
seidewitz
approved these changes
Dec 3, 2025
Member
seidewitz
left a comment
There was a problem hiding this comment.
On a fork, I was able get the Publish Release Build action (modified to do just an install, not a deploy) to trigger on the publication of the release, complete successfully, and attache the KPAR files to the release.
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
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.
Currently, creating KerML Project Archive (KPAR) files is a manual and tedious process, which prevents us from releasing the new set of KPARs with each release of the Pilot. This PR is the first step towards automating the release process of KPARs. It contains the following key changes:
pom.xmlto automatically build standard library's KPARs during each build (currently, only for the textual notation).To be able to build KPARs, Sysand needs to know the location of each library. This PR uses the concept of a workspace common in other package managers (for example, Cargo) to group all projects of the standard library so that it is easier to manage them. File
sysml.library/.workspace.jsonmaps project IRIs to their locations in the repository (relatively to the.workspace.jsonfile).Finally, this PR corrects two typos in
.meta.jsonfiles.I tested the PR in two ways:
./mvnw -B clean verify --file pom.xmlon my laptop. It succeeded and produced KPARs insysml.library/outputfolder.