Dominik Dahlem wrote:
> This master project property file can be kept in source > control and provides a single location for settings shared > among sub-projects. Imagine you have 50 sub-projects and each > of them contains a project properties file with settings > which could well be shared. It's maintenance hell, if properties > are likely to change.
I am in this very situation, I've found that in some cases I can use preGoals as a hack to work round this. It's not elegant, but until property inheritance is in place it may help.
For example, I added this to the master maven.xml file and it seems to work.
<preGoal name="checkstyle:init">
<echo>preGoal in root maven.xml is fudging checkstyle to use geotools config settings</echo>
<j:set var="maven.checkstyle.properties" value="../../geotools_checks.xml"/>
</preGoal>
The echo is only there to remind me to take it out once the issue is resolved.
James
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
