[#IDEA-11248] Ant: property and condition builtin tasks are showing error highlights for valid attributes

IDEA: Feedback

Ant: property and condition builtin tasks are showing error highlights for valid attributes

Created: 26 Jan 07 00:02 Updated: 12 Jul 07 22:50

Component/s:

Ant Integration

Issue Links:

Depend

This issue depends on:
	IDEADEV-12711 Ant integration: support task definit...

Relates

This issue relates to:
	~~IDEADEV-13346~~ Ant integration: overriding Property ...

Build:	6,656
Severity:	Medium

Description

« Hide

I have in my Ant build file various property and condition tasks like the following:

However, the "environment" and "location" attributes for "property" and "property and "value" attributes for "condition" are highlighted as "Attribute 'environment' is not allowed here", etc. When I ctrl-click the property or condition task name, the cursor moves to the last taskdef element (for ant-contrib) at the top of my build file. If I delete and then re-insert those taskdef elements, the error highlights on the property task go away but the condition error highlights remain. But if I reload the project, the error highlights are showing again.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Alexander Chernikov - 29 Jan 07 19:44

May relate to ~~IDEADEV-13346~~, since the presence or absence of taskdefs affects recognition of core tasks.

Checked the given script fragment in the minimal necessary context (surrounded with <project/> element): all code is "green" on my PC.

[ Permlink | « Hide ]

Colin Fleming - 05 Mar 07 13:40

I also have a lot of problems with taskdefs (as reported in ~~IDEADEV-13346~~).

[ Permlink | « Hide ]

Alexander Chernikov - 12 Jul 07 16:59

Selena 7061: the sample build file:

<project default="main">
	<property environment="enviro"/>
	<property name="imported.basedir" value="."/>
	<property name="common.destination" location="${imported.basedir}/../../src/cr11248/envi.xml"/>
	<condition property="env.PATH" value="${env.Path}">
		<isset property="env.Path"/>
	</condition>
	<target name="main"/>
</project>

is all green for me. Probably this issue is Obsolete.

[ Permlink | « Hide ]

Alexander Chernikov - 12 Jul 07 22:21

From ~~IDEADEV-13346~~, Colin:
[quot]
I'm still seeing this, or something very similar:

<target name="jaxb.generate"
          description="Generate Java binding classes from XSD">

    <taskdef name="xjc" classname="com.sun.tools.xjc.XJCTask">
      <classpath refid="tools.jaxb.classpath"/>
    </taskdef>
    <!-- update dependencies task above when adding new xmlbean tasks -->

    <xjc schema="${basedir}/src/com/core/devbench/bundle/content/node/scheme/iso8583parser/iso8583.xsd"
         destdir="${devbench.src.generated.dir}"
         package="com.core.devbench.bundle.content.node.scheme.iso8583parser.generated.dictionary"
         extension="true"
        >
      <produces dir="${devbench.src.generated.dir}/com/core/devbench/bundle/content/node/scheme/iso8583parser/generated/dictionary"
                includes="* impl/*" />
      <binding dir="${basedir}/src/com/core/devbench/bundle/content/node/scheme/iso8583parser" includes="*iso8583.xjb"/>
      <arg value="-Xcommons-lang" />
      <arg value="-Xelement-provider" />
    </xjc>

In the preceding code all attributes and sub-elements of the xjc task are incorrectly highlighted in red. Build 7041.
[/quot]

Yes, all attributes of xjc task are "red" in 7059. I've investigated the com.sun.tools.xjc.XJCTask. It contains no setters for "schema", "destdir" and other stuff. So, the introspector does not return these attributes. Instead, it implements DynamicConfigurator interface. In fact this is the issue IDEADEV-12711.

[ Permlink | « Hide ]

Colin Fleming - 12 Jul 07 22:50

Ok, thanks for the information! I've voted for that issue.