Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 179154 - ANT build autocomplete resolvers wrong to wrong basedir when doing complex import.
Summary: ANT build autocomplete resolvers wrong to wrong basedir when doing complex im...
Status: RESOLVED DUPLICATE of bug 174759
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-24 09:57 EDT by Davy Toch CLA
Modified: 2007-04-23 16:10 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Davy Toch CLA 2007-03-24 09:57:27 EDT
Put these two files in ${user.home}/.ant/scripts/import:

- defaults.xml :

<project basedir="." default="x">
  <property file="${user.home}/.ant/scripts/import/defaults.properties"/>
</project>

- defaults.properties:

prop=${basedir}/blabla

Also create a small Eclipse project with the following buildfile, e.g. in c:\tmp\test:

- build.xml:

<project basedir="." xmlns:u="defaults">

  <import file="${user.home}/.ant/scripts/import/defaults.xml"/>

  <target name="justatest">
    <echo>prop : ${prop}</echo> 
  </target>

</project>

If you execute the target 'justatest', then prop will resolve to the correct value:

 c:\tmp\test\blabla

However if you hover over ${prop} of build.xml in Eclipse, then you get:

 c:\Documents and Settings\dto\.ant\scripts\import\blabla

which is incorrect.

To know why the latter value is incorrect, you should read the specs of the <import> statement of ANT 1.6.5.
Comment 1 Darin Swanson CLA 2007-04-23 16:10:32 EDT
Thank you for the bug report.

On 3.3 I20070418-1012, I cannot reproduce the problem.
The hover is consistent with the expected output.

I believe this to be a duplicate of bug 174759.

*** This bug has been marked as a duplicate of bug 174759 ***