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.
Summary: | The "Availble" and "Installed" tab were empty when I opened the Plugin Manager. | ||
---|---|---|---|
Product: | platform | Reporter: | hantsy <hantsy> |
Component: | Plugin Manager | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jglick, mmirilovic |
Priority: | P2 | ||
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Other | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
available is empty, press "Reload CataLog" can load the moudles
installed is empty, there is no way to reload and view the installed modules |
Description
hantsy
2011-04-09 07:50:41 UTC
netbeans-7.0rc2-201104070802-ml-javaee.zip I used this version. Created attachment 107621 [details]
available is empty, press "Reload CataLog" can load the moudles
Created attachment 107622 [details]
installed is empty, there is no way to reload and view the installed modules
we are having problem with JDK 7, similar to one described by you - see issue 194407 ... but as you mentioned : you are able to reproduce it on JDK 6 (is this really correct?) .. also have you tried to re-size the dialog (it might help to show the list) yes...it is problematic with JDK 7. NetBeans set JDK 7 as default JDK when it starts up(even I set JAVA_HOME to JDK6 installed directory and added the JDK6/bin to system path ). I changed it in the netbeans.conf and specified the netbeans_jdkhome to D:/jdk6, it works well. (In reply to comment #5) > yes...it is problematic with JDK 7. > NetBeans set JDK 7 as default JDK when it starts up(even I set JAVA_HOME to > JDK6 installed directory and added the JDK6/bin to system path ). > I changed it in the netbeans.conf and specified the netbeans_jdkhome to > D:/jdk6, it works well. Now I am a little bit confused, so to make it clear : - it doesn't work on JDK 7 - it does work on JDK 6 Could you confirm this ? Thanks in advance. Sounds like a clear duplicate of bug #194407. yes. JDK7 does not work. JDK6 OK. *** This bug has been marked as a duplicate of bug 194407 *** |