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 73741 - [65cat] Add fix module dependency to libraries
Summary: [65cat] Add fix module dependency to libraries
Status: NEW
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker with 4 votes (vote)
Assignee: Martin Kozeny
Keywords: UI
: 103869 (view as bug list)
Depends on:
Reported: 2006-03-19 18:24 UTC by _ viendu
Modified: 2013-02-14 13:17 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description _ viendu 2006-03-19 18:24:15 UTC
When develop Netbeans module, it would be very productive to developers to have
a button to fix module dependency, or two buttons with one to add missing one
and another to remove redundant one (incase people know what they're doing and
want to add an extra one for later use).  Currently, there is an ant task
(thanks to Martin Krauskopf for pointing this out) fix-dependency, but it's not
visible, and not where new users would look for when they working with libraries
for module.  Also, this task needs to be improved.  For my very small project,
it iterates many times before fixing it successfully.  For a large project, this
may not be acceptable.
Comment 1 Martin Krauskopf 2006-03-19 18:49:38 UTC
I agree (as on the list) that this useful feature is somehow hidden. Not sure
where it should be exactly placed.
Would be nice to have this faster and behave better (e.g. show modules to be
removed before actually removing them). However I think that progress bar
showing some status would be enough for now. If you have too much modules
dependencies in your module, you might consider whether the module should not be
splitted. Speed is more or less acceptable *for me*.
Comment 2 tk_fhd_aui 2006-03-20 06:29:21 UTC
I would suggest to have a button for this in the libraries tab of the project 
properties dialog.

Comment 3 Jesse Glick 2006-03-20 16:47:53 UTC
No plans to work on it. Not so easy to improve; current version (removing
unnecessary deps) just relies on trial-and-error with javac. Doing better would
probably require a significant knowledge of Java language and compiler semantics.
Comment 4 Martin Krauskopf 2006-03-20 16:56:18 UTC
No plan to work on the speed, right? But this issue is primarily (summary) about
moving the task into more visible place. Maybe it should be filed as two ones.
Comment 5 Jesse Glick 2006-03-20 16:59:05 UTC
I would rather not make it more prominent unless and until it is more thoroughly
tested and probably improved in some ways. Right now it should be considered
experimental; was originally introduced mainly to assist with the openide.jar split.
Comment 6 Jaroslav Tulach 2006-03-21 06:53:22 UTC
"tested and improved in some ways" - well, it is unit tested enough - the only 
thing it needs is to test in real situations, which is hard to do unless we 
expose it more. Improved - What do you mean? It takes a while, but this is not 
an action that should be run implicitly, just on user request. If needed it is 
possible to add a progress bar which will count from 0 to N where N is number 
of dependencies of your module. Not hard to do. It could also be rewritten as 
a wizard, with last panel showing summary and allowing to cancel/apply the 
change. Beyond the UI there is not much to improve. What it does, it does 
right. Btw. if you do not feel ok including this into standard apisupport we 
can make it Alpha AU module without much problems.
Comment 7 pzajac 2006-03-21 09:16:26 UTC
I also don't see any problem qith fix dependecies. I use it in non nbcvs
modules.    I am also for to make it more visible. 

Comment 8 Jesse Glick 2008-06-20 03:09:03 UTC
*** Issue 103869 has been marked as a duplicate of this issue. ***
Comment 9 rmichalsky 2008-07-23 08:49:34 UTC
*** Issue 61227 has been marked as a duplicate of this issue. ***
Comment 10 Jaroslav Tulach 2012-06-20 14:28:52 UTC
A "button" described in initial comment seems to indicate this is more about project UI than harness.