Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Ant launching API changes

With the fix to bug 42262 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=42262) the Ant launch configuration constants will be available as API in the org.eclipse.ant.ui plugin.

This note is to alert any users of the constants in their internal form, that they will no longer be available in the internal form, but instead must be used from the API interface instead.

The details of the changes:

The following constants have been removed from org.eclipse.ant.internal.ui.launchConfigurations.IAntLaunchConfigurationConstants
and place into org.eclipse.ant.ui.launching.IAntLaunchConfigurationConstants

ID_ANT_LAUNCH_CONFIGURATION_TYPE
ID_ANT_BUILDER_LAUNCH_CONFIGURATION_TYPE
ATTR_ANT_TARGETS
ATTR_ANT_AFTER_CLEAN_TARGETS
ATTR_ANT_MANUAL_TARGETS
ATTR_ANT_AUTO_TARGETS
ATTR_ANT_CLEAN_TARGETS
ATTR_TARGETS_UPDATED
ATTR_ANT_PROPERTIES
ATTR_ANT_PROPERTY_FILES
ATTR_HIDE_INTERNAL_TARGETS
ATTR_SORT_TARGETS
ATTR_DEFAULT_VM_INSTALL
ID_ANT_PROCESS_TYPE


The following constants will remain in the internal interface org.eclipse.ant.internal.ui.launchConfigurations.IAntLaunchConfigurationConstants (both of them are deprecated and will not be exposed as API)

ATTR_ANT_CUSTOM_CLASSPATH
ATTR_ANT_HOME

Michael Rennie


Back to the top