Community
Participate
Working Groups
After creating an Ant launch configuration via the launch shortcut "Run As > Ant Build", and openning it in the LCD, the "apply" button is enabled. Newly created configurations should not be immediately dirty. Similarly, if I create a new configuration while in the LCD with an Ant Build file as the active editor, navigating to the JRE tab enables the "Apply" button, but the user has not changed anything.
The fix to bug 308645 is causing this. Setting the vm type / name attributes cause the JRE block (which we reuse from JDT) to remove them (as deprecated attributes) on the first call to performApply() - which is called by navigating to the JRE tab.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
