Bug 34680 - Eclipse and AntXMLContext.setCurrentTargets(Map)
Summary: Eclipse and AntXMLContext.setCurrentTargets(Map)
Status: RESOLVED FIXED
Alias: None
Product: Ant
Classification: Unclassified
Component: Core (show other bugs)
Version: 1.6.3
Hardware: Other other
: P2 normal (vote)
Target Milestone: 1.7.0
Assignee: Ant Notifications List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-29 19:50 UTC by Darin Swanson
Modified: 2008-02-22 12:18 UTC (History)
0 users


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 2005-04-29 19:50:39 UTC 
Eclipse's Ant integration has a class that extends ProjectHelper2 for 
generation of an Ant model for the Eclipse Ant editor.

As such we need to manipulate the AntXMLContext.
Unfortunately changes in Ant 1.6.3 to AntXMLContext (bug 34566) are causing us 
pain:
  AntXMLContext.setCurrentTargets(Map) has default protection.

Can this method be made public (preferred) or at least made protected?

This is not a show stopper for Eclipse integrating Ant 1.6.3...I have 
implemented a workaround using reflection. But this workaround is ugly...
Comment 1 Peter Reilly 2005-05-03 10:35:37 UTC 
Opps, sorry.
It was a last minute fix....
I am not too sure if there will be another 1.6 release, but
I will place the change in the 1.6 branch so it will be be
picked up if there is.
Comment 2 Darin Swanson 2005-05-03 18:33:02 UTC 
Thanks. If there is any way this could cause a rev of the Ant release it would 
be great. This problem is causing more grief than anticipated...performance etc.