Issue when building and using SysmlInteractive class

[bertilmuth]

EDIT: When using the March release of the sysml.library
(sources download at https://github.com/Systems-Modeling/SysML-v2-Pilot-Implementation/releases/tag/2026-03), the parsing problems described below don't occur.

---

I downloaded the pilot implementation as described, but selected the latest version of the plugin (using the GUI installer).

When running a clean maven build, it built the jar file org.omg.sysml.interactive-0.59.0-SNAPSHOT-all.jar.

However, the tests of sysml interactive failed.

Also, when using the org.omg.sysml.interactive.SysMLInteractive class, it has problems with the new sysml.library.

Even for simple sysml files that only consist of one package and one part usage, the parser says the files are invalid.

When changing sysml.library (taken from the top level directory) with an older version of it, it works!

(Note that SysmlInteractive in verbose mode claims to load the new library's files, but then still throws an error.)

This is the sysml file:

package 'Valid'{
part def 'Block';
}

And this is the error:

ERROR:Must directly or indirectly specialize Parts::Part (1.sysml line : 2 column : 2)

[seidewitz]

I cannot reproduce your problem. I did a clean installation using the installer, did a Maven clean install (on the head of master) and was able to process your simple example without any problem using SysMLInteractive.

It seems unlikely that the issue is with the library. The library models have not changed since the end of last year. It is more likely that Xtext is not able to correctly link to elements of the library models.

How are you running your tests of SysMLInteractive?

[seidewitz]

Note that two new projects have been added for 2026-04: org.omg.sysml.model and org.omg.sysml.model.bundle.

[bertilmuth]

I cannot reproduce your problem. I did a clean installation using the installer, did a Maven clean install (on the head of master) and was able to process your simple example without any problem using SysMLInteractive.

It seems unlikely that the issue is with the library. The library models have not changed since the end of last year. It is more likely that Xtext is not able to correctly link to elements of the library models.

How are you running your tests of SysMLInteractive?

I'm valildating the exact same .sysml files using different versions of the 'sysml.library' folder.
I just ran my own code with the 'sysml.library' folder here:
https://github.com/Systems-Modeling/SysML-v2-Pilot-Implementation/tree/master/sysml.library

And it didn't consider any file I put in as valid, even though they were considered valid with previous versions of that folder.

[bertilmuth]

Also, I don't know if this is related, but it just struck me as odd: a dependency to sysand was added (which I might not have on the classpath):

3009d58

[seidewitz]

Also, I don't know if this is related, but it just struck me as odd: a dependency to sysand was added (which I might not have on the classpath):

3009d58

The identified commit added the use of Sysand for the automatic generation of the .meta.json files in the library projects. So, all the .meta.json files changed in that commit, but none of the .sysml files. The last time there was any change to a library model was in November. There is no substantive difference between the 2026-03 and 2026-04 model libraries.

I'm valildating the exact same .sysml files using different versions of the 'sysml.library' folder.
I just ran my own code with the 'sysml.library' folder here:

Are you running SysMLInteractive from within Eclipse, or from the command line, or programmatically from other software?

[bertilmuth]

Current main version of the sysml.library folder (doesn't work) vs. version from March 2026 (works).

One thing to note: I used a newer version of Eclipse Modeling Tools (>12.2025) when I installed via Oomph.

I compile with mvn clean package, then use the interactive all-jar in a standalone Java application which I run from Eclipse.

The code looks like this:

        SysMLInteractive sysml = SysMLInteractive.getInstance();
        sysml.setVerbose(false);
		sysml.loadLibrary(sysmlLibraryPath);

SysMLInteractiveResult result =  sysml.process(...);

[seidewitz]

I still cannot reproduce the problem. I compared the files in sysml.library from the latest release (2026-04) to 2026-03 and, as expected, the only changes were to .meta.json files (and only one change was substantive).

If you are willing to send me your entire program, I could try running it in my Eclipse environment (2025-12). Or you could post a note on SysML v2 Release, to see if anyone else has the problem. If not, then there is something odd going on with your local configuration.