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.

Bug 122821 - Automatically include dependent modules recursively in suite Libraries
Summary: Automatically include dependent modules recursively in suite Libraries
Status: RESOLVED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: rmichalsky
URL:
Keywords: UI
: 156245 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-11-27 07:26 UTC by quintona_gmail_com
Modified: 2009-03-11 22:49 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description quintona_gmail_com 2007-11-27 07:26:05 UTC
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.
Comment 1 Jesse Glick 2008-06-20 03:00:43 UTC
Probably would be good. Trickier with provide-require/need/recommend dependencies, especially if there is more than one
provider for a given token.
Comment 2 Jesse Glick 2008-11-07 03:16:00 UTC
Would of course be subsumed by my recent proposal to do away with ${excluded.modules}.
Comment 3 rmichalsky 2009-01-06 10:24:38 UTC
*** Issue 156245 has been marked as a duplicate of this issue. ***
Comment 4 rmichalsky 2009-03-09 22:06:54 UTC
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).
Comment 5 Jesse Glick 2009-03-10 01:17:09 UTC
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
Comment 6 rmichalsky 2009-03-10 13:55:32 UTC
sorry for the test, fixed in core-main #dbb4b1b3ae49
Comment 7 Quality Engineering 2009-03-11 22:49:57 UTC
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