auto-generated ui code

Hello Cory,

We have our GUI options set to generate the GUI code into the java
files. When we build from the command-line (via ant), shouldn't the
$$$autogenerated$$$ blocks be regenerated?

We have a case where a developer deleted a component from a form and
checked in the changes to that form assuming that the $$$setupUI$$$
method would be refreshed at the next build. Instead we got compile
errors because the $$$setupUI$$$() method was stale. Rebuilding in the
IDE fixed the java file, but I was surprised that we had to do this.

Is there an option to the uidesigner task that we have to set to force
it to regenerate the GUI code?

Source code generation only works within the IDE. UIDesigner's javac2 Ant
task performs only bytecode instrumentation. If you're using the javac2 task,
you should simply switch to bytecode instrumentation.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

Dmitry Jemerov wrote:

Hello Cory,

>> We have our GUI options set to generate the GUI code into the java
>> files. When we build from the command-line (via ant), shouldn't the
>> $$$autogenerated$$$ blocks be regenerated?
>>
>> We have a case where a developer deleted a component from a form and
>> checked in the changes to that form assuming that the $$$setupUI$$$
>> method would be refreshed at the next build. Instead we got compile
>> errors because the $$$setupUI$$$() method was stale. Rebuilding in the
>> IDE fixed the java file, but I was surprised that we had to do this.
>>
>> Is there an option to the uidesigner task that we have to set to force
>> it to regenerate the GUI code?

Source code generation only works within the IDE. UIDesigner's javac2
Ant task performs only bytecode instrumentation. If you're using the
javac2 task, you should simply switch to bytecode instrumentation.

Ok, thanks for the information. It wasn't clear to me from the dialog or
the documentation that java-generation option is for IDE compiles only.

Cory