Add an option to choose the runtime library used for bindings by JDT#211
Merged
guillep merged 2 commits intomoosetechnology:v4from Apr 10, 2026
Merged
Add an option to choose the runtime library used for bindings by JDT#211guillep merged 2 commits intomoosetechnology:v4from
guillep merged 2 commits intomoosetechnology:v4from
Conversation
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
2 participants
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.
Adding the option
-sysLibPath <path/to/lib.jar>to give to JDT a specific runtime library to use to resolve native Java bindings.This is necessary when you want to have models that match specific versions of Java, especially for older versions which can't run VVJ.
This option should ideally be used with the one used to specify the version of Java used (option
-1.7or-1.8for example). As it is, VVJ will run itself if you use the-sysLibPathoption without specifying the version used. Maybe it should return an error in that case?