--On Saturday, December 17, 2005 4:45 PM -1000 Aaron Kagawa
<[EMAIL PROTECTED]> wrote:
Hey Guys,
I've been getting this error in Eclipse in some of the local.build.xml
files.. For example dist.build.xml and
hackyCore_Installer/local.build.xml.
Anybody else see those?
thanks, aaron
Yes, I've been hassling with this ever since the Version 7 redesign.
Basically, the issue is this:
* We have a "single top-level entry point" for our build system: build.xml
* build.xml imports a couple dozen subsidiary build files to create one
logical build file. This is a very reasonable, modular, and effective
design, and is current best practice in Ant.
* Eclipse is not smart enough to understand the above, and so it complains
when you edit a subsidiary build file if it contains a definition that
would be visible to it under the circumstances in which we invoke the build
system using the single top-level entry point.
* There is a solution: put <import file="build.xml"/> at the top of every
subsidiary build file where warnings appear. I've tried this in the past,
and it almost kills Eclipse---the warnings go away, but it can take up to
30 seconds for Eclipse to process a single keystroke. Basically, the
circularities in the imports just kills the parser.
I definitely feel like this is a problem with Eclipse, not our design. I
solve it by disabling Eclipse warnings :-)
Cheers,
Philip
