It appears to me that only the property ${basedir} can be resolved at
runtime. I don't know, whether that is a limitation to the ant
checkstyle ant target.
Because some of my projects have a different depth in the project layout
I can't rely on a one-for-all setting of the maven.checkstyle.properties
in the ~/build.properties file. I got away with my problem when I
specified this property in each project. There is a bit of duplication
here, but i don't have the error anymore.
Cheers,
Dominik
On Mon, 2004-05-17 at 11:06, Dominik Dahlem wrote:
> Hi all,
>
> is there a way to resolve a property in jelly explicitly? The checkstyle
> plugin internally sets the checkstyleProperties property which in my
> case is based on maven.checkstyle.properties. I set
> maven.checkstyle.properties to
> ${projectA.home}/master/src/config/checkstyle.xml in ~/build.properties.
> projectA.home in turn is specified in a specific project.properties
> file.
> Before the ant target of checkstyle is executed it prints out the
> checkstyleProperties property correctly with the path resolved whereas
> the target itself bellies up, because it can not find the configuration
> file "file:${projectA.home}/master/src/config/checkstyle.xml". I assume
> the checkstyleProperties property is not resolved correctly inside the
> checkstyle ant target.
>
> Did anyone come across a similar problem?
> Thanks for any help.
>
> Dominik
--
Dominik Dahlem <[EMAIL PROTECTED]>
-------------------------------------------------------
Trinity College Dublin
Department of Computer Science,
Dublin 2, Ireland
fax: (+353) 1-677 2204
www: http://www.cs.tcd.ie/Dominik.Dahlem/
-------------------------------------------------------
signature.asc
Description: This is a digitally signed message part
