Refactoring of the target map. This is done to enable a preselection of the used targets.
Selection of targets to use by additional property page
Removed 'only targets with description' setting
Last used target is stored in a separate Properties file. The local properties
are overwritten so I cannot store values there.
Thus the project needs no saving if you choose another target.
Refactoring of fetchAntNode
Remove of calls to the fetchAntNode method. This should speed up a little.
name of the project (if present) is included in the node name.
Added property to keep the default target.
Remove the arbitrary command. This should be done through the windows settings.
Ant actions are now disabled if ant is running.
added ability to call the ant manual
ant target group now recognizes a null target as the default target
ant's output in fixed font
Check for ant running before another thread is started
-> AntRunner panel is not cleared when ant is running.
the 'warning:' prefix is cut
Notification if a project is set up for a prior version of AntRunner
ant is executed in the project directory
Refactoring of adding build file as a child: Existing nodes in the project
are moved to AntNode as a child.
ant node is removed if no build file selected (JB5 and upwards)
If the call to ant wasn't successfully this failure is now detected
and presented to the user.
Known sources of this problem:
the path to the ant script is wrong
due to an bug in ant: the classpath contains spaces
Version 0.8
This version is just a bug fix. If you wanted to create an
AntNode for a new project an error occurred. This error should now
be fixed.
Version 0.7
The internal name of the Ant-Node was changed from AntNode to
AntRunner. This was necessary to use AntRunner.
and the OpenTool Ant Tool on the same project. If you have installed the
new AntRunner.
version you will see a question mark instead of the Ant icon. You have
to configure a new Ant Node via the menu Tools -> Configure Ant. To
remove the old Ant node with the question mark you have to change the .jpr
or .jpx manually.
Version 0.6b introduced the external JVM for ANT
. It is not necessary to use the JBuilder
internal JVM for ANT
. Therefore the internal JVM was dropped and only the external JVM will
be used.
It is possible to display only targets with description. This is
useful if you have many internal targets. So you can add for each target
you want to use from JBuilder.
a description and only this targets are displayed. Currently you have to
change to another project and back or to restart JBuilder
to activate this change.
Version 0.6b
You can use AntRunner
in a JVM of its own. ANT
called from AntRunner
should behave nearly the same as the standalone ant.