New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration flag for deactivating an annex #2288
Comments
We need the following:
|
@jjhugues did you intend the flag to be project specific (project A can use annex B, but project C can NOT use annex B) or is the flag should be applied to all projects (if annex B flag is unchecked, then it can NOT be used in project A and project C) |
@AaronGreenhouse Do you know if it is possible to access preferences from stand alone java programs (jar files) that you can run from command line to process aadl file? |
The flag should be project specific |
@asazonova I don't know for sure, but I think it would probably work. The core Workspace preference and project properties data structures are not UI-specific. |
for workspace preference, we use final IPreferenceStore store = OsateCorePlugin.getDefault().getPreferenceStore(); This Preferences prefs object does not have a method to set a default value. However, unlike workspace preference, for projects we set the preference explicitly with prefs.putBoolean(annexExtensionId.toLowerCase(), value); - see implementation below: this one does not have a check if oldValue == newValue, which is good for us, it will just set the preference to false without ignoring it Conclusion,
|
Add screenshots and explanation how to use this feature to Advanced section of help (org.osate.help) |
|
In some cases, one may want to deactivate an annex from the regular parsing phase. For instance apply analyses that do not depend on them
One may imagine a configuration parameter for that, that would simply deactivate the corresponding registered parser
An open question could be: how about analysis? We could have a warning if EMV2 is disabled when trying to run FHA or FTA
The text was updated successfully, but these errors were encountered: