Skip to content
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

Force plug-in activation for custom property testers #276

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

trancexpress
Copy link
Contributor

This change ensures Eclipse correctly uses the property testers isBashFileWithoutExtension and isOpenPathActionEnabled, by setting the forcePluginActivation property in the respective plugin.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

This change ensures Eclipse correctly uses the property testers
'isBashFileWithoutExtension' and 'isOpenPathActionEnabled', by setting
the 'forcePluginActivation' property in the respective plugin.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: de-jcup#275
Signed-off-by: Simeon Andreev <simeon.danailov.andreev@gmail.com>
Copy link
Owner

@de-jcup de-jcup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thank you for the contribution.

@de-jcup de-jcup merged commit 49b5b58 into de-jcup:master Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Open path in terminal menu entry visible despite preference set to false
2 participants