Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 92546 - Ant content type describer activating ant core
Summary: Ant content type describer activating ant core
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M7   Edit
Assignee: Kevin Barnes CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-24 22:19 EDT by Darin Swanson CLA
Modified: 2005-04-29 15:34 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Swanson CLA 2005-04-24 22:19:02 EDT 
From bug 89195 comment #29:

Another reason is that as it stands, org.eclipse.ant.core is being activated 
when the Ant describer is loaded. Having it in runtime would avoid that. 

Otherwise, the class should be moved to its own package and that package 
should be marked as an exception in the Eclipse-AutoStart header in the bundle 
manifest, for example:

Eclipse-AutoStart: true; exceptions="org.eclipse.ant.internal.donotactivate"
Comment 1 Darin Swanson CLA 2005-04-27 19:09:04 EDT 
Moved AntBuildfileContentDescriber and AntHandler to the special no auto start 
package.

Reworked these two classes to be completely independent of the rest of Ant 
core plugin.

Changes to InternalCoreAntMessages and InternalCoreAntMessages.properties to 
remove the AntHandler message (which should not have been internationalized as 
these are internal errors).

Changes to the MANIFEST.MF file as well.
Comment 2 Darin Swanson CLA 2005-04-27 19:09:28 EDT 
Please verify Kevin.
Comment 3 Kevin Barnes CLA 2005-04-29 15:34:33 EDT 
verified