Ant editor broken?

Hi.

I haven't edited my build files for a long time.
Having created a new one this morning I noticed that somehow the Ant editor didn't react as usual. It's behaves like the normal XML editor. It doesn't know anything about the structure of a build file anymore. No autocompletion for standard tags and attributes and no quick doc.

Robert

6 comments
Comment actions Permalink

Hello Robert,

RB> I haven't edited my build files for a long time.
RB> Having created a new one this morning I noticed that somehow the Ant
RB> editor didn't react as usual. It's behaves like the normal XML
RB> editor. It doesn't know anything about the structure of a build file
RB> anymore. No autocompletion for standard tags and attributes and no
RB> quick doc.

Ant support is being currently rewritten. Old Ant support is disabled in
current EAP builds, and the new Ant plugin will be included in the next EAP.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hi Dimitry,

OK, I feared that somehow by installing a plugin I have broken that feature myself.
I'm going to create the new build file by the old "copy and adapt" procedure and am looking forward to see the new Ant plugin.

Cheers,
Robert

0
Comment actions Permalink

RB> I haven't edited my build files for a long time.
RB> Having created a new one this morning I noticed that somehow the Ant
RB> editor didn't react as usual. It's behaves like the normal XML
RB> editor. It doesn't know anything about the structure of a build file
RB> anymore. No autocompletion for standard tags and attributes and no
RB> quick doc.

Ant support is being currently rewritten. Old Ant support is disabled in
current EAP builds, and the new Ant plugin will be included in the next
EAP.

Any serious reasons for rewriting it instead of just improving it a little? I mean
it was pretty good compared to the ANT support of other IDEs :) ?

Thanks in advance,

Ahmed.

0
Comment actions Permalink

Hello Ahmed,

>> Ant support is being currently rewritten. Old Ant support is disabled
>> in current EAP builds, and the new Ant plugin will be included in the
>> next EAP.
>>
AM> Any serious reasons for rewriting it instead of just improving it a
AM> little? I mean it was pretty good compared to the ANT support of
AM> other IDEs :) ?

There are two main reasons. The first is that the old Ant support codebase
was hard to maintain, and some of the bugs were very hard to fix. Second,
the new Ant support is developed as an "honest" plugin, using only OpenAPI
and ExtAPI features, and all the API improvements that are implemented because
of Ant requirements will be available to other plugin developers.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

>>> Ant support is being currently rewritten. Old Ant support is disabled
>>> in current EAP builds, and the new Ant plugin will be included in the
>>> next EAP.
>>>

AM> Any serious reasons for rewriting it instead of just improving it a
AM> little? I mean it was pretty good compared to the ANT support of
AM> other IDEs :) ?

Second, the new Ant support is developed as an "honest" plugin,
using only OpenAPI and ExtAPI features, and all the API improvements
that are implemented because of Ant requirements will be available to
other plugin developers.

This sounds fantastic :).
Thank you for the details.

Ahmed.

0
Comment actions Permalink

Any news on this? - lots of red still in the editor - including (but not limited to) properties propagating through nested imported (ant <import.../>). I've got eclipse guys waiting for this to work correctly before they'll move to IntelliJ. This has been a problem for a long time and our multi-module projects are extremely dependent on nested builds that are similar in structure to the IntelliJ project..

We're on build 6180 now.

Thanks,
-VL

0

Please sign in to leave a comment.