r351574nc3 / docbkx-tools

Automatically exported from code.google.com/p/docbkx-tools
0 stars 0 forks source link

PostProcess doesn't resolve parent properties #25

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Define a copy action on postProcess configuration parameter using
properties of the parent project
2. Run docbkx:generate-html

What is the expected output? What do you see instead?

Properties of the parent project are properly resolved.
Properties are not resolved and stays ${xxx} in the ant script.

What version of the product are you using? On what operating system?

Using version 2.0.8 on Windows XP.

Please provide any additional information below.

Example:
<postProcess>
  <copy todir="${project.build.directory}/site/css"
file="${parent.basedir}/src/manual/css/manual.css" />
</postProcess>

The "project.build.directory" is correctly replaced but anything starting
with "parent." is not.

Original issue reported on code.google.com by lehph...@gmail.com on 18 Feb 2009 at 8:05

GoogleCodeExporter commented 9 years ago

Original comment by MimilO...@gmail.com on 5 Mar 2009 at 9:58

GoogleCodeExporter commented 9 years ago
Hi,

both preprocess and postprocess are subjected to this behaviour.

I finally found the problem (or at least the solution), you have to use
"project.parent.*" instead of "parent.*".

<echo message="${project.parent.basedir}" /> is working as expected.

Cedric,

Original comment by MimilO...@gmail.com on 5 Mar 2009 at 10:03

GoogleCodeExporter commented 9 years ago
It is working as expected now, I'm sorry for creating this "bug".

Thank you

Original comment by lehph...@gmail.com on 6 Mar 2009 at 1:15

GoogleCodeExporter commented 9 years ago
No problemo, 

now we have a place where it is described, you are certainly not alone with 
this problem.

Original comment by MimilO...@gmail.com on 6 Mar 2009 at 3:45