OK Geir. My apologies for the crappy format of the cvs diff.
Here is a valid one (hopefully) and an additional patch as well that went
unnoticed until now in TexenTask. It amazingly did not show up because I was
developping on a Clearcase dynamic view and doing a getCanonicalPath on
multiple paths does not break on a dynamic view whereas it breaks (as
expected) on a static view.
I'm keeping the old way of resolving relative paths from the ant basedir
otherwise there could have been a problem since it would have used the jvm
directory instead of the ant basedir. (in most case the JVM directory is the
ant basedir so it often goes unnoticed until you have a global build file
that calls these build file and you start having a headache with paths)
Otherwise it would have been tricky to enforce people to specify relative
path by putting the property ${basedir}/path1/path2 instead of path1/path2
so that things are crystal clear for anyone reading/maintaining the build
file.
Additionally I added a log output in verbose mode to help debug for
templatePath and changed the System.out.println to a log in info mode.
Having a System.out in Ant is generally bad practice simply because the
context of your output will be 'echo' rather than the name of the task.
Cheers,
ps: Hope this is for good since I'm doing 100 things at a time.
Stephane
PropertiesUtil.java.diff
TexenTask.java.diff
