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.
Fresh build 781 from deadlock, JDK 1.5 on Mac OS X. 1. Go to the Plugins dialog. 2. Switch to New Plugins tab, it contains "Web and Java EE" 3. Switch to Installed tab, it does not contain "Web and Java EE" => "Web and Java EE" should be present in Installed, not sure why it is listed in New Plugins. I don't think it should be there.
Petr, I understand the problem PM has identified wrongly "Web and Java EE" as uninstalled plugin in your standard IDE, i.e. included "Web and Java EE". Content of New plugin tab contains plugins what were not be installed. Install tab contains installed plugin, it means intersection of New plugins and Installed must be empty. Update tab contains all plugins from Installed tab which has a update. This problem was fixed in main trunk together with issue 106798. Could you please on todays builds (06/19) if it works for you? Thanks .
No. I tried build 940 from deadlock and I can still see this issue. Attaching a screenshot. I installed from the "full" zip package.
Created attachment 43992 [details] "Installed" tab without Web and Java EE
Ok, I will continue to finding what's wrong.
Reproduced on #build netbeans-hudson-trunk-943-full.zip. Looks as a incorrect Web and Java EE feature then a bug in PM.
After fix issue 106799 no problem on Plugin Manager side. The modules JDBC Rowset and SQL Support Module are declared in Update Center catalog as a required part of 'Web and Java EE' plugin but are not installed in 'full' IDE. Please, report the problem to BE (rnovak) or fix the problem itself. Because impl. of issue 106799 allows to present partly installed plugin in Install tab then 'Web and Java EE' will be presented as installed with Missing modules note in plugin's description. I think I close as fixed for now. Possible disparity between UC declaration and modules in M10 builds should be fired to nbbuild/update centre content component. Anyway, I see no reason why this issue can block the issue 102180. Why the issues depends each other?
Jirko, thanks for the fix. I posted a question to the team that owns the two modules to find out what is the intention. Then we can discuss with RE. > Anyway, I see no reason why this issue can block the issue 102180. Why the issues depends each other? I probably don't quite understand the steps to reproduce issue 102180 (there are no good steps to reproduce), but I am assuming that the submitter of that bug is trying to deactivate the "Web and Java EE" features.