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.
080529. If you install Scala Debugger Projects Integration, you cannot disable it (either deactivate or uninstall) in Plugin Manager - if you try, PM says you also have to disable Java Debugger! You need to use Module Manager to disable just SDPI.
*** Issue 135779 has been marked as a duplicate of this issue. ***
I guess the problem is handling provides/requires dependency and causes issue 134493 too.
Seems that way. If a provider of a token is already installed, it is not necessary to install others.
Filed issue 137325 to remove jpda.EditorContext and jpda.SourcePathProvider providers in scala debugger.
When issue 137325 got fixed no plugin (i.e. multiple providers of any token) will cause problem like this. It won't happen in NetBeans 6.1 + with officially Update Centers nor NetBeans 6.5 Dev + officially Update Centers. I think this issue has became a potential issue but not actual just now I could decrease the problem priority.
Reassigning to the new "autoupdate/*" owner dlipin.
137325 is fixed, also two more issues this one depends on are fixed. How I can install Scala Debugger Projects Integration? I see only scala kit and scala runtime in plugin manager.
It's possible the set of modules, or kit dependencies, have changed since this was filed.
Jirka`s justification to close this issue as resolved later. Example: A module org.netbeans.mysql can create new database, it's provides a token: database-creator. Opposite module org.netbeans.dbui needs some database creator (not hard org.netbeans.mysql but any database creator) for its functionality, to express this fact it states: org.netbeans.dbui needs database-creator. In NetBeans runtime these module will loaded together. Back to the issue 136318: If there is org.netbeans.oracle module which provides database-creator token and if both of then are loaded in NetBeans for some reasons, neither NetBeans Module System nor Autoupdate can differentiate it and if users disables org.netbeans.mysql then org.netbeans.dbui will disable as well and because org.netbeans.oracle has then no opposite module, it will be disabled too. It's a known limitation of Autoupdate Services but I guess it's worthless to fix it because it's only artificial problem.
Clarification: "if both [mysql & oracle modules] are loaded in NetBeans for some reasons, neither NetBeans Module System nor Autoupdate can differentiate it and if users disables org.netbeans.mysql then org.netbeans.dbui will disable as well" - the module system will not disable dbui just because mysql was disabled so long as oracle is still enabled. This is a bug only in AU.
OK, I`ll reopen it for the future investigation and downgrade to P4 since it does not happen in the current codebase (?).
What steps shall I use to reproduce the problem?
(In reply to comment #12) > What steps shall I use to reproduce the problem? Organization of Scala-related plugins changed since then (as in comment #8). Root bug in PM probably remains open.