Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 73629 - Ant editor error markers conflict with XMLBuddy error markers
Summary: Ant editor error markers conflict with XMLBuddy error markers
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-09 18:34 EDT by Bob Foster CLA
Modified: 2009-08-30 02:25 EDT (History)
3 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 Bob Foster CLA 2004-09-09 18:34:29 EDT 
Open a build.xml file in Ant editor [3.0.1RC2] containing just:

<project></project>

This will produce an error marker in the left margin. Close the file and re-open
it in XMLBuddy. The error marker is still there. Edit the file to produce:

<project default="foo">
	<target name="foo">
		
	</target>
</project>

The error marker is still there! Nothing done in XMLBuddy (or any other editor)
will remove the Ant editor's error marker, since it is permanent and markers are
removed by id.

This seems a general design flaw. Editors should be able to control the markers
in a file, without having to be aware of other editors.
Comment 1 Darin Swanson CLA 2004-09-09 23:23:36 EDT 
Unlikely to be only an Ant Editor problem.
Kai have you already seen and considered this problem?
Comment 2 Darin Swanson CLA 2004-10-26 16:33:37 EDT 
My current take on this:
This is a design flaw in the Ant integration. The integration adds markers via 
the code within the Ant Editor support instead of having an Ant builder that 
manages the marker generation and removal from a particular resource. 
An Ant builder will properly support editing of Ant buildfiles no matter the 
editing implementation.
Comment 3 Darin Swanson CLA 2005-04-04 18:39:14 EDT 
This flaw will remain for 3.1
Comment 4 Denis Roy CLA 2009-08-30 02:25:48 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.