Bug 18253 - filter task handles tokens differently if they come from a file
Summary: filter task handles tokens differently if they come from a file
Status: RESOLVED DUPLICATE of bug 8972
Alias: None
Product: Ant
Classification: Unclassified
Component: Core tasks (show other bugs)
Version: 1.5.2
Hardware: Other other
: P3 normal (vote)
Target Milestone: ---
Assignee: Ant Notifications List
URL:
Keywords:
: 18252 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-03-23 01:04 UTC by Henrik Lynggaard
Modified: 2008-02-22 12:18 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henrik Lynggaard 2003-03-23 01:04:29 UTC
In my build file I load different properties files for properties depening on
the environment. I then Use these properties as values forow tokens during file
copy. 

However I have the problem that tokens comming from a properties files, does not
have its values property expanded while token set directly in the build file does

example (this one works)

<target ...>
  <property name="resin_install_dir" value="/opt/java/resin"> (this normally
comes from a file)

  <filter token="resin_dir" value="${resin_install_dir}/doc">
  <copy ....>
</target>

In this example the file copied contains "/opt/java/resin/doc/" as the replaced
tokens, which is what I was expecting

now having many tokens I moved them to a seperate file and did:

<target ...>
  <property name="resin_install_dir" value="/opt/java/resin"> (this normally
comes from a file)

  <filter filtersfile="tokens.properties">
  <copy ....>
</target>


In this example the file copied contains "${resin_install_dir}doc/" as the
replaced tokens, which is certainly not what I want.... :-(

While waiting for the fix: Is there another workaound for the desired
feature,without doing example 1 for all the tokens ?
Comment 1 Henrik Lynggaard 2003-03-23 01:06:06 UTC
*** Bug 18252 has been marked as a duplicate of this bug. ***
Comment 2 Stefan Bodewig 2003-03-24 09:20:29 UTC

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