This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When creating a basic RCP I create a skeleton application(module suite) and attempt to add just the netbeans modules that I require in the application by going to the project properties->libraries and selecting various clusters and modules. I receive warnings about unsatisfied dependencies when I un-select some modules. It would be nice if I could select just the modules that I want and then the dependencies get automatically included instead of me having to manually check all the dependencies.
Probably would be good. Trickier with provide-require/need/recommend dependencies, especially if there is more than one provider for a given token.
Would of course be subsumed by my recent proposal to do away with ${excluded.modules}.
*** Issue 156245 has been marked as a duplicate of this issue. ***
core-main #5549abf0cc56 When there is a resolvable error, button "Resolve" appears in the bottom left corner of the libraries customizer and pushing it resolves the error automatically. Currently only dependencies on excluded modules arre esolved by transitively including them, missing provider could be resolved by offering the user potential providers in the same way as "Fix import" does (only one by one).
Breaks test compilation and I could not find an obvious hotfix (adding .warning to join method makes test run but it then fails). Backing out: core-main #5a80eb5a45f6
sorry for the test, fixed in core-main #dbb4b1b3ae49
Integrated into 'main-golden', will be available in build *200903111543* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/5549abf0cc56 User: Richard Michalsky <rmichalsky@netbeans.org> Log: #122821: Button for resolving missing excluded modules in suite customizer