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 135779 - Uninstalling JavaFX Script modules deactivates some NetBeans plugins
Summary: Uninstalling JavaFX Script modules deactivates some NetBeans plugins
Status: VERIFIED DUPLICATE of bug 136318
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-26 09:20 UTC by Alexandr Scherbatiy
Modified: 2008-06-11 12:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
NetBeans Installer dialog (25.31 KB, image/png)
2008-05-26 09:21 UTC, Alexandr Scherbatiy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandr Scherbatiy 2008-05-26 09:20:36 UTC
JavaFX Script plugin 2008-05-23_02-01-55.zip
NetBeans 6.1 Web & Java EE, build 200804211638

Steps to reproduce:

- Install JavaFX Script plugin 
- Try to uninstall all JavaFX Script modules
  There is a message on 'NetBeans IDE Installer dialog'
    "The following plugins need to be deactivated because they require
     one or more of the plugins you are about to deactivate:

     BEA WebLogic Server [1.7]
     GlassFish [1.5.0.1.1]
     Web Applications [1.1]
     ...
    "
Comment 1 Alexandr Scherbatiy 2008-05-26 09:21:49 UTC
Created attachment 61895 [details]
NetBeans Installer dialog
Comment 2 Andrey Yamkovoy 2008-06-02 12:50:26 UTC
Looks like UC tries to uninstall some module which JavaFX plugin and some other modules (like BEA WebLogic Server,
Glassfish and so on) depends on. Looks like UC issue > change issue component to 'autoupdate'.
Comment 3 Lark Fitzgerald 2008-06-02 18:31:59 UTC
Is there a workaround for this?  At the moment I am un/re-installing the entire NB ide to get around this.
Comment 4 Jiri Rechtacek 2008-06-03 08:51:14 UTC
Seems a JavaFX debugger API module (a autoload) makes the problem. Modules such libraries (autoload) should be hidden
for end-users in Plugin Manager and end-users cannot deactivate them by hand. Use a workaround: make JavaFX debugger API
module hidden in Plugin Manager (in NetBeans project customizer) to avoid problem like this.

*** This issue has been marked as a duplicate of 136318 ***
Comment 5 Andrey Yamkovoy 2008-06-05 12:07:17 UTC
The Debugger API module is hided now.
Comment 6 Alexandr Scherbatiy 2008-06-11 12:01:50 UTC
verified