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.

Bug 163311 - swing generator generates java 1.6 code
Summary: swing generator generates java 1.6 code
Status: RESOLVED WONTFIX
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: Other Windows ME/2000
: P3 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-21 21:51 UTC by crodrigu
Modified: 2009-06-26 12:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description crodrigu 2009-04-21 21:52:24 UTC
I do not have java 1.6 installed (only java 1.4 and 1.5) the swing generates code that uses java.swing.grouplayout which
I can not compile using java 1.5
Comment 1 Tomas Pavek 2009-04-22 12:44:28 UTC
This could happen if the GUI form was originally created on JDK 6 (possibly by someone else?). Once created, the GUI
form remembers what type of GroupLayout code it generates (so it's not changed back and force if the project is opened
on different JDKs). You can change it - just open the form, select its root node in Inspector and go to properties -
there's "Layout Generation Style" property which you can set to "Swing Layout Extensions" not to generate Java 6 code.

Also check the global setting in Tools | Options -> Misc -> GUI Builder -> Layout Generation Style. If it is changed to
"Standard Java 6 code", it forces new forms to generate Java 6 code no matter if Java 6 platform is present. This should
be set to Default. In case you have this set to default and newly created forms still generate javax.swing.GroupLayout
even if there is no JDK 1.6, then it is a bug - and we might need more information from you.
Comment 2 pribyl 2009-06-26 12:14:14 UTC
I am closing this incomplete issue as wontfix - reporter did not provide any additional info for a long time
(hopefully it is because the problem was solved  :) 

Crodrigu if you still encounter this problem, feel free to reopen this issue ant try to provide any additional info (see
tpavek's last post)

Thank you