Create a new module suite (set of IDE extensions, not application). Run it to test a module in the suite.
Create a new Java SE project. Project is created on disk. No "Activating Java SE" appears in project wizard. Project is created.
Right click the package of the new project, and choose New > Panel to create a JPanel subclass. Press Next.
Next step of the wizard shows a progress bar and says "Activating Java SE, Java SE, Java SE" - caption is definitely wrong (see screenshot).
Once it is ready, finish the wizard.
JPanel is created, BUT:
- The corresponding .form file is not created
- Guarded block markers in the editor are created, but guarded blocks are editable
- (possibly unrelated) Deleting the created file triggers an OutOfMemoryError: PermGen space
Created attachment 88461 [details]
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
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]
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
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
Well, where is that string constructed?