Force plug-in activation for custom property testers #276
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 change ensures Eclipse correctly uses the property testers
isBashFileWithoutExtension
andisOpenPathActionEnabled
, by setting theforcePluginActivation
property in the respectiveplugin.xml
entries. This allows Eclipse to load the property tester class prior to trying to use it - in case the bash editor plug-in was not activated yet.Fixes: #275