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: | "Activating Java SE, Java SE, Java SE" at weird time | ||
---|---|---|---|
Product: | ide | Reporter: | _ tboudreau <tboudreau> |
Component: | Features On Demand | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | Keywords: | ERGONOMICS |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Screen shot
Projects |
Description
_ tboudreau
2009-09-29 02:00:18 UTC
Created attachment 88461 [details]
Screen shot
Making this P2, as, more importantly than the "Java SE, Java SE, Java SE" text, this bug makes it extremely time-consuming to work on a module which you test by using the form editor. You have to start NetBeans once, manually enable Java SE in Tools > Plugins, then shut NetBeans down and start it again before the form editor is able to create .form files. The root of the problem seems to be that Java SE is not enabled when you create a new J2SE project - you can create the project and classpath scanning happens, but the Java SE cluster stays not enabled - apparently *something* gets enabled (since scanning happens), but not everything is enabled, and this breaks the form editor. Works for me in clean build from Oct 11, but I may not exactly understand the steps to reproduce. However whatever I tried works OK. Closing. Reproducible 100% of the time with the attached modules - simply run Bean Library Module, clean it, run it, in the IDE that is started, follow the steps described. I reproduced this in build 20091001 on Mac OS w/ JDK 6. I'll try it in today's build and reopen if I can still reproduce the problem. Created attachment 89324 [details]
Projects
1. unzipped the ZIP 2. start full IDE with empty userdir 3. start netbeans, open project BeanLibraryModule 4. start BeanLibraryModule 5. exit the BeanLibraryModule application 6. open Beans module 7. create from in its bean package Everything works OK. Works for me as well on Windows; I will double-check that it works on Macintosh once I get a newer build installed on my mac. However, the string "Activating Java SE, Java SE, Java SE" is pretty weird - is there any way that can still be constructed? It suggests something more is wrong than just not activating modules aggressively enough. I do not see such strange string either. If you give me steps to reproduce I can fix it (but I'll change priority to P4). Well, where is that string constructed? |