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

Fix editor bindings for gradle.properties and Kotlin DSL files #1284

Merged
merged 1 commit into from
Jan 11, 2024

Conversation

oleosterhagen
Copy link
Contributor

In order for the editor content type bindings configured in the plugin.xml to work correctly, the missing dependencies for the Generic Text Editor have to be added.

For Gradle Properties the content type configuration should use the full file name gradle.properties without a separate entry for the file extension, so that these files are opened with the Generic Text Editor and other property files are still handled by the Properties File Editor.

In order for the editor content type bindings configured in the
plugin.xml to work correctly, the missing dependencies for the Generic
Text Editor have to be added.

For Gradle Properties the content type configuration should use the full
file name "gradle.properties" without a separate entry for the file
extension, so that these files are opened with the Generic Text Editor
and other property files are still handled by the Properties File
Editor.
@donat
Copy link
Contributor

donat commented Jan 11, 2024

I've tested your changes and it does fix the editor association issue. It's not documented in the PR's title, but you also fixed the editor association for the .gradle.kts files 🎉 .

@donat donat added this to the 3.1.9 milestone Jan 11, 2024
@donat donat merged commit 4bd8a7f into eclipse-buildship:master Jan 11, 2024
2 checks passed
@donat
Copy link
Contributor

donat commented Jan 11, 2024

Thank you for the contribution!

@oleosterhagen oleosterhagen deleted the fix-editor-bindings branch January 11, 2024 17:44
@donat donat self-assigned this Jan 12, 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.

2 participants