Add implicit dependencies from the target#1869
Merged
laeubi merged 1 commit intoeclipse-pde:masterfrom Jul 15, 2025
Merged
Conversation
Currently if one defines implicit dependencies in the target these only getting added to the launch but not the project, this makes these quite hard to use. The best would be to make this feature more flexible to let the user choose if it is a runtime requirement or a compile dependency. Unless we have this, it seems the best way is to add it in both cases as indicated in the help: > The Implicit Dependencies section is used to manage the implicit > dependencies of the target. Any plug-in marked as an implicit > dependency will always be added as a required plug-in when PDE > determines requirements.
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
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.
Currently if one defines implicit dependencies in the target these only getting added to the launch but not the project, this makes these quite hard to use. The best would be to make this feature more flexible to let the user choose if it is a runtime requirement or a compile dependency.
Unless we have this, it seems the best way is to add it in both cases as indicated in the help: