Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 66976

Summary:	[content type] "Run Ant" not available from context menu
Product:	[Eclipse Project] Platform	Reporter:	Kevin Barnes <cocoakevin>
Component:	Resources	Assignee:	Rafael Chaves <eclipse>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	Darin_Swanson, dj.houghton
Version:	3.0
Target Milestone:	3.0 RC3
Hardware:	All
OS:	All
Whiteboard:

Description Kevin Barnes

2004-06-14 11:28:08 EDT

checked out "security" project from jxta.org. Tried to build using build file in security/build/java, but 
Run Ant and Run Ant... are not in the context menu (JUnit Plugin Test is the only option). Running from 
Run menu works fine.

Comment 1 Darin Wright

2004-06-15 09:54:05 EDT

Marking as RC3 candidate. Needs investigation.

Comment 2 Darin Swanson

2004-06-15 11:51:11 EDT

If the Ant buildfile contains a byte order mark (BOM) then the content type 
for the buildfile will not be set. See bug 67048. This may be the cause or 
possibly the content parsing is failing in some other way.

Comment 3 Darin Swanson

2004-06-15 13:41:47 EDT

The parsing in XMLRootElementContentDescriber cannot handle the comment at the 
beginning of this buildfile. 
If fails with fatal org.xml.sax.SAXParseException: End of entity while 
processing comment.

Moving to Core.

Comment 4 Rafael Chaves

2004-06-15 14:56:48 EDT

Adding DJ for obtaining approval.

Comment 5 Rafael Chaves

2004-06-15 14:57:42 EDT

DJ, please disregard comment above. It was intended to another bug. Still need
to investigate this one.

Comment 6 Darin Swanson

2004-06-15 19:19:30 EDT

I beleive this is likely just a duplicate of 67211...the parsing stops in the 
comment preamble to the buildfile.

Comment 7 Rafael Chaves

2004-06-16 11:36:19 EDT

I will follow Darin's suggestion and close as duplicate. Kevin, please reopen if
the fix for bug 67211 does not work for you.

*** This bug has been marked as a duplicate of 67211 ***

Comment 8 Darin Swanson

2004-06-18 12:21:21 EDT

I verified this is fixed in the latest build.