Lars Hamann

Thanks for submitting the issue. I was able to reproduce the behavior to confirm the bug. The ModelAPI uses the `OCLCompiler` to create the Pre- and Postconditions, which is wrong....

A fix is available in #78. You can try it out with the results of the build.

Hi Chuck, I'm glad to hear you like USE. There are different ways to define operations in USE: - Side-effect free query operations These are the operations defined by an...

This one is a big one, because we want to solve more than just packages in the long-run. Plans are currently: - Add support for defining data types, i. e.,...

 This setting is not persited in the layout file. See `org.tzi.use.gui.views.diagrams.DiagramOptions` and `org.tzi.use.gui.views.diagrams.classdiagram.ClassDiagramOptions`

USE is using a Swing `JFileChooser` for this and this is the default look & feel of it. To use the file chosse specific to the OS, just a small...

Preview: https://github.com/useocl/use/suites/11113597098/artifacts/566229556

While it is easy to add an `exit` at the end of the test in-files, if not present. A problem exists with tests that provide a invalid USE model, i....

These "bump version issues" are automatically created after a USE version was released by creating a tag matching the pattern `v*.*.*`. See https://github.com/useocl/use/blob/master/.github/workflows/release.yml Because we don't know what type of...