Ant integration broken in build 6170

+1

Hello Mikael,

I see no such defects in 6170. For example, I have generated an ant build
for a test project of 3 modules by IDEA. It is all green.

Is even simplest script highlighted with red in your environment? E.g. is
]]>
red?

Is it Ok with other XML files (if any)?

I can't imagine that something this major has slipped through, so I
see no point in filing a JIRA item.

I installed 6170 and suddenly my ant integration is completely broken.
It
recognizes the "target" tag
but everything else gets a red mark with an error message like
"Element
'property' is undefined".
My gutter is just a mass of red marks.
Anyone have any idea what's going on?

Thanks in advance.

/Mikael

Alexander,
JetBrains.

I am seeing a similar problem in Selena EAP 6763. Both of my main Ant build.xml files are lit up like a Christmas tree.

Here is a snippet from the top of my build.xml:

    
        CoreServer ANT build script
    

    
    
        
        
    

]]>

IDEA says 'description' and 'echo' elements are undefined.
Maybe a bad change was checked into 6170 and 6763? I have been
using Selean EAP, and I didn't see this problem in earlier EAPs, for sure it wasn't in 6708 version.

I see no such defects in 6170. For example, I have generated an ant build
for a test project of 3 modules by IDEA. It is all green.

>

Is even simplest script highlighted with red in your environment? E.g. is
<project name="proj" default="main">
<target name="main">
<property name="prop" value="val"/>
</target>
</project>
red?

I copied your example above into a new build.xml in a new project. The tag
"property" is marked as red. See screenshot.

The same ant stuff works fine in 6140.

Is it Ok with other XML files (if any)?

It appears so.

/Mikael

On 2007-03-21 11:34:35 +0300, "Mikael Karlsson"
said: >> I see no such defects in 6170. For example, I have generated an ant build >> for a test project of 3 modules by IDEA. It is all green. >> >> Is even simplest script highlighted with red in your environment? E.g. is >> >> >> >> >> >>]]> red?

I copied your example above into a new build.xml in a new project. The tag
"property" is marked as red. See screenshot.

The same ant stuff works fine in 6140.

>> Is it Ok with other XML files (if any)?

It appears so.

/Mikael


<image>

Do you guys use bundled Ant or specify custom location. If latter, what
version it is?

Do you guys use bundled Ant or specify custom location. If latter, what
version it is?

I've tried both the bundled Ant 1.7 from 6170 and the bundled Ant 1.6.5 from
6140.
Same result.

Right now I tried changing Ant to 1.6.5 in 6170. Still red markers but on
switching back
to this news window to keep writing this post, IDEA reported an error.

Apparently, it's not possible to copy the error message from the reporting
dialog.

Anyway, it says:
The data "]]>" is not legal for a JDOM attribute: 0x0 is not a
legal XML character.

It's submitted as 87809. I haven't seen this error before.

/Mikael

All my ant files are lit up bright red since installing 6170. What a mess.

i found this one: add comments to it

http://www.jetbrains.net/jira/browse/IDEA-12055

On 2007-03-20 16:34:20 +0300, "Mikael Karlsson"
<mikael.karlsson@pitch.se> said:

I can't imagine that something this major has slipped through, so I see no
point in filing a JIRA item.

I installed 6170 and suddenly my ant integration is completely broken. It
recognizes the "target" tag
but everything else gets a red mark with an error message like "Element
'property' is undefined".
My gutter is just a mass of red marks.

Anyone have any idea what's going on?

Thanks in advance.

/Mikael

We've nailed down problem to IDEA being installed into a directory with
space characters in the path. So until the new build you may want to
re-install into a space-less path.

on Mac OSX it goes into "/Applications/IntelliJ IDEA 6" on its own

should that be renamed?

On 2007-03-22 05:21:16 +0300, k <krsjunk@netscape.net> said:

on Mac OSX it goes into "/Applications/IntelliJ IDEA 6" on its own

should that be renamed?

Yep

FYI This problem is fixed in Selena EAP 6766 (was broken in 6763)