Nevermind that, is it possible to get ant to even recognise external tasks that are specified via taskdef?
Well, in my experience this sometimes fails in unexplicable ways, but most of the times I managed to have it working.
For example, if I put the following into the build.xml:
(I have it top-level, not inside a target) Idea correctly recognizes , tasks and so on. Sometimes it marks as errors inner tasks such as s inside s and so on, but in general this is a feature that at least exist.
Note that sometimes I have had errors with taskdefs inside targets not working, but working if moved outside the target (as ]]> childs).
ARGH! I just realized this has even gone worse in 3368: before if I had the xmlns:ivy="antlib:fr.jayasoft.ivy.ant" attribute on the ]]> tag this was marked red with no other annoyance. In 3368 this somehow causes the build.xml not to be recognized anymore as an ANT build file, and it is treated as a normal xml file. For a very short moment I have been happy, though: I thought that the lack of red lines on the gutter meant that all ant-syntax-related bugs had been resolved... :|
Nevermind that, is it possible to get ant to even recognise external tasks that are specified via taskdef?
Well, in my experience this sometimes fails in unexplicable ways, but most of the times I managed to have it working.
For example, if I put the following into the build.xml:
(I have it top-level, not inside a target) Idea correctly recognizes , tasks and so on. Sometimes it marks as errors inner tasks such as s inside s and so on, but in general this is a feature that at least exist. Note that sometimes I have had errors with taskdefs inside targets not working, but working if moved outside the target (as ]]> childs).
ARGH! I just realized this has even gone worse in 3368: before if I had the xmlns:ivy="antlib:fr.jayasoft.ivy.ant" attribute on the ]]> tag this was marked red with no other annoyance. In 3368 this somehow causes the build.xml not to be recognized anymore as an ANT build file, and it is treated as a normal xml file. For a very short moment I have been happy, though: I thought that the lack of red lines on the gutter meant that all ant-syntax-related bugs had been resolved... :|
You might want to vote for this issue:
http://www.jetbrains.net/jira/browse/IDEA-2572
Somebody (I think it was Igor) said that it won't make it into 5.0, but
they have plans for overhauling the Ant editor in the next minor release.
Dimitar