Leo Simons wrote:
Berin Loritsch wrote:
I am having the hardest time getting Maven and Forrest to work together. The plugin is not installing cleanly. Any tips will be appreciated.
I also can't run Forrest by itself without the proper "Forrest" artifacts where the command line expects them.
Can I get a little help on this? A pointer in the right direction?
sure, but first some more information would be a good idea, like what environment you're using, what versions of what tools you installed in what location, what errors you're seeing, y'know, the usual ;)
Running WIndows XP, Maven Beta 9, JDK 1.4.1, etc.
I tried building the plugin, but that didn't work. THanks for making the new version available (it was not before).
Ok here is the culprit:
<!-- !!! override property defaults with parent-files !!! -->
<property file="${project.home}/../forrest.properties" />
<property file="${project.home}/../../forrest.properties" />
<property file="${project.home}/../../../forrest.properties" />
<property file="${project.home}/../../../../forrest.properties" />This is bad.
There might be room for defined levels of properties, but blindly applying values from forrest.properties files in four parent directories blindly will cause the types of issues I am running into.
We don't have a problem in Fortress because the levels are deep enough:
D:/projects/avalon/fortress/docs
../../../../forrest.properties = D:/forrest.properties
There is no "fail silently" for the <property/> tag if it can't find a directory for a file.
If we have defined levels like:
project.home=.
parent.project.home=${project.home}That way we can overload it so that we can have:
parent.project.home=${avalon.buildsystem}
and the properties loaded from:
<property file="${project.home}/forrest.properties"/>
<property file="${parent.project.home}/forrest.properties"/>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
