Commit aa6f1da
committed
Add implicit dependencies from the target
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.1 parent 5c59d79 commit aa6f1da
1 file changed
Lines changed: 12 additions & 0 deletions
File tree
- ui/org.eclipse.pde.core/src/org/eclipse/pde/internal/core
Lines changed: 12 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
58 | 58 | | |
59 | 59 | | |
60 | 60 | | |
| 61 | + | |
61 | 62 | | |
62 | 63 | | |
63 | 64 | | |
| |||
275 | 276 | | |
276 | 277 | | |
277 | 278 | | |
| 279 | + | |
278 | 280 | | |
279 | 281 | | |
280 | 282 | | |
| |||
641 | 643 | | |
642 | 644 | | |
643 | 645 | | |
| 646 | + | |
| 647 | + | |
| 648 | + | |
| 649 | + | |
| 650 | + | |
| 651 | + | |
| 652 | + | |
| 653 | + | |
| 654 | + | |
| 655 | + | |
644 | 656 | | |
645 | 657 | | |
646 | 658 | | |
| |||
0 commit comments