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.
Trying to unselect j2ee in module manager results in uninstalling of j2se project module a therefore broking functionality of netBeans. This is absolutly unacceptable. J2SE projects can't depend on J2EE
What exactly is "trying to unselect *j2ee*"? Did you e.g. try to unselect all modules in the Java EE category, or something else?
What I did was to unselect J2ee node in module manager, hence automatically unselecting all modules belonging to j2ee category
Ah sorry, my fault, I thought this was for 6.0, which doesn't have a J2EE node. We need to make sure that no modules outside the enterprise cluster are in the "Java EE" category.
Not a showstopper for the preview release, lowering to P2 for now. Not sure what the expected behavior is in NetBeans 6, since as Andrei points out, there is no simple way to disable the whole category. Is there a spec available for how this will work in 6.0 FCS? Also, I assume the current list of categories is provisional and the categories will be redefined - this should be coordinated across all teams. Moreover, I expect the "Installed" tab in the Plugins dialog will not be the primary way to turn on or off the Java EE features - for NB 6 FCS, UI from the installer which lists the high level components should be available in the Plugins dialog.
Still present in 6.0, and I believe is P1
This is not a P1 (according to Bug priority guidelines). J2SE project is probably selected because of dependencies on APIs like JPA, which in fact IS J2EE technology. Anyway, as Petr mentioned we can move it if there will be some spec for that.
J2SE is selected because of dependency on j2ee.metadata And how come suddenly j2se project is dependent on j2ee when j2ee wan until recently just an optional package? There is no way that j2se is dependent on j2ee. And it must be fixed asap
I am sorry. I don't understand how this issue depends on "Web and Java EE" does not appear under the Installed tab (issue 106851). Can you please elaborate?
Just that if it's not in 'Installed' tab I cannot uninstall it to test the behavior mentioned in this issue. Anyway I am having some other problems with Plugin dialog in latest build (not able to switch from NBM to Plugin view), so will have to solve this first.
Issue 106851 is not a blocker. just go to settings and switch from Plugins to NetBeans modules and you will see all modules with categories. Modules in java1 cluster should not be listed in Java EE category.
I don't know if the plugin manager changed its way of handling clusters vs. plugins, but in fresh build if I deselect 'Web and Java EE' plugin, IDE is suggesting deactivation of EJB Refactoring, NetBeans Profiler (J2EE Projects) and Web Refactoring. Those are obviously ok, so I am closing this.
And doesn't it by the way deselect as well J2SE project?
No.
In the current build of NB 6.0 (updated less that 3 hours ago): In the Plugin Manager, I have a view that individual modules are displayed (Settings tab - radio button "NetBeans Modules (NBM)" selected). In the "Installed" tab, I right-click on a row with module "Java EE Metadata" (from category "Java EE" and select "Deactivate Category 'Java EE'" from the pop-up menu. I get a window displaying the following information: The following plugins were scheduled to deactivate: Java EE Metadata Model Support Java EE Metadata Java Persistence API Support API The following plugins have to be added to the deactivation, because one or more plugins you are about to deactivate depend on them. Java SE Projects
yes indeed it is the case. And I am afraid there can be more modules which are affected (like Java Persistance API support). Java SE Projects is dependent on JavaEE Metadata Model Suport and JavaEE Metadata. Anyway, please clean this mess.
Those are my modules, taking over.
Fixed. Checking in j2ee/metadata/src/org/netbeans/modules/j2ee/metadata/Bundle.properties; /cvs/j2ee/metadata/src/org/netbeans/modules/j2ee/metadata/Bundle.properties,v <-- Bundle.properties new revision: 1.5; previous revision: 1.4 done Checking in j2ee/metadata/support/src/org/netbeans/modules/j2ee/metadata/model/support/resources/Bundle.properties; /cvs/j2ee/metadata/support/src/org/netbeans/modules/j2ee/metadata/model/support/resources/Bundle.properties,v <-- Bundle.properties new revision: 1.3; previous revision: 1.2 done Checking in j2ee/persistenceapi/src/org/netbeans/modules/j2ee/persistenceapi/resources/Bundle.properties; /cvs/j2ee/persistenceapi/src/org/netbeans/modules/j2ee/persistenceapi/resources/Bundle.properties,v <-- Bundle.properties new revision: 1.3; previous revision: 1.2 done Checking in j2ee/toplinklib/src/org/netbeans/modules/j2ee/toplinklib/Bundle.properties; /cvs/j2ee/toplinklib/src/org/netbeans/modules/j2ee/toplinklib/Bundle.properties,v <-- Bundle.properties new revision: 1.3; previous revision: 1.2 done