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.
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*.
I would suggest to have a button for this in the libraries tab of the project
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.
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.
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.
"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.
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.
*** Issue 103869 has been marked as a duplicate of this issue. ***
*** Issue 61227 has been marked as a duplicate of this issue. ***
A "button" described in initial comment seems to indicate this is more about project UI than harness.