Improvements and fixes including respective tests for Java2UML reactions #177
Conversation
This file contains 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
no package-info.java files are present. furthermore, references to types (classes or interfaces) that do not exist now lead to the creation of the respective type, including its package structure.
JanWittler
added
Java
|
Closed due to inactivity |
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.
This is a draft PR for improvements and fixes to the Java2UML reactions that were necessary for applying Vitruv to ArgoUML.
Specifically, this PR addresses the following issues:
For each of these issues there is also a test included. However, the tests currently fail, mainly because they rely on a workaround that was necessary to test propagation of external types (e.g., from an external library). Specifically, the tests require access to the internal resource set of the VSUM in order to add external libraries to the JaMoPP classpath. A proper way of doing this might be to introduce initializers for the resource set in a VSUM (e.g., to set required load options).