Android 1.5 project in Eclipse and whenever I merely have an x

24 down vote favorite

I have an Android 1.5 project in Eclipse and whenever I merely have an xml resource file open the build dies with an error. E.g. if I have theres\layout\main.xml open as the active document it won't build and throws the following error:

Error in an XML file: aborting build.
res\layout\main.xml:0: ERROR Resource entry main is already defined.

Then I have to delete main.out.xml and switch to any .java file in the project to get it to build.

Do I have something configured incorrectly or is this just an Eclipse or ADT bug?It drove me nuts for an hour before I figure out what the cause was.

edited Apr 8 at 18:28

Korhan Öztürk
1,872 1 3 13

asked Nov 4 '09 at 14:29

duckworth
2,590 1 7 23

100% accept rate

	Well, I have this kind of problem, but simply Project / Clean did works for me.I removed main.out.xml from res/layout, then resaved an main.xml, then reopens project. After this magic, project builds properly. – user560761 Jan 3 '11 at 1:57
	I ran into the same issue.I delete first the xml files which were not parsed main.out.xml and strings.out.xml and then i go clean my project.When i re-run,everything was fine. Rgds, – user626896 Feb 21 '11 at 16:03
	I had the same issue, and it totally freaked me out..., the .xml.out files even caused more and more errors, anybody should mention that problem on developer.android.com thanks anyway!! – Andy Nov 10 '11 at 10:04

feedback

5 Answers

active oldest votes

up vote 42 down vote accepted

I ran into this as well.

If you have an xml file open and click the 'Run' button, then instead of running your Android project Eclipse will try to run a transform on the xml file. It then creates a new xml file with the output of the transform and adds it to your project. Then the project will fail to run at all because of the existence of the duplicate xml file.

So make sure you don't have any duplicate xml files in your project (look at the manifest file, as well as layout files). The way I work around this is to make sure the project tree has focus (or just select a tab with a java file) before clicking 'Run'.

There is likely a better way to handle this (via a config change perhaps), but I'm pretty new to Eclipse and that's the workaround I came up with :). Hope that helps.