Hi all,
Since switching to ASDT 0.0.8 and using the Problems view to capture
MTASC errors, I have noticed a number of complaints about elements in
my ANT build.xml which work just fine when running the ANT build.
Here is an example portion of my build.xml and the error it generates
in the Problems panel:
<condition property="html.exists">
<and>
<isset property="html"/>
* <not><equals arg1="${html}" arg2=""/></not>
</and>
</condition>
Error - The content of element type "not" must match
"(depend|filename|custom|not|date|contains|selector|depth|or|and|present|majority|none|size)*".
I'm sure that the syntax I am using is correct, and I am getting the
expected results from the logical operators I am using (which run
different targets based on the results of variables). The build works
just fine, and there are no errors reported in the Console view which
displays the output from ANT and MTASC.
So I'm guessing that the errors that appear in the Problems panel are
due to Eclipse is checking against an older version of ANT or
something - I really don't know.
My solution for the time being is to suppress the ANT warnings by
clicking on the Filters button in the Problems panel and unchecking
XML Auto-Validate - but then I might miss something useful.
I was just wondering if anyone out there has encountered the same
issue, and whether anyone has an explanation or a solution?
Cheers,
Scott
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
