[myoungstrom]

I have some XML files in my java source directory. I have those xml files copied to the project’s output directory by an ant script I have run automaticly in “Builders”. So the xml files frequenty are cleaned out and copied back in. Apparently when ME does an xml validation it finds those files in the output folder and validates them. Later when the files aren’t there ME attempts to validate them even though they aren’t there and I get an error in my “Problems” view that says:

File not found: “**The path to some file in my output directory** (The system cannot find the path specified)”.

The error goes away if I manually run validation in the project again with the files there.

It would be nice if there was a way to get the validator to not attempt to validate files that don’t exist or at least don’t provide an error if the file disappears. Any ideas?

Regards,
Mike

[Riyad Kalla]

Mike,
Eclipse automatically copies out any non-Java files to your output path… this is true for .properties files, .xml files and all other kinds of files… I don’t thikn you need your Ant script to do this.

Also I’ve never seen the behavior of MyEclipse to dig into the output directory to do validation work… are you certain this is what is happening? Do you have your output dir setup appropriately in your Java Build Path project properties? If you don’t, then MyEclipse may not be able to determine what your output dir is, and then treats everything like fair game.

[myoungstrom]

I’ll see if I can come up with a simple test case and get back with you.

Mike

[Scott Anderson]

Mike,

FYI, an enhanement to “not validate” things in the output path (derived resources) is a targeted enhancement for version 3.8.3 in December. A test case could make sure we cover it well. For support folks, the enhancement is bug #1130 if you need to attach a test case.

[Author]

Posts