In my subproject maven.xml files I've had to:
<loadproperties srcFile="../build.properties"/>
<loadproperties srcFile="../project.properties"/>
Maven loads settings in this order, and uses last set to determine final
value of a property:
${project.home}/project.properties
${project.home}/build.properties
${user.home}/build.properties
Ant on the other hand uses first-set, once a property has a value it can't
be changed.
So getting the loadproperties done in the right order is critical if you're
overriding anything with your build.properties.
THAT is a real PITA, I agree.
----- Original Message -----
From: "Colin Sampaleanu" <[EMAIL PROTECTED]>
To: "Maven Users List" <[EMAIL PROTECTED]>
Sent: Friday, September 19, 2003 11:29 AM
Subject: Any way to have shared properties when extending from a base
project
> I just realized that while you can extend a project with something like
> extend>${basedir}/../master/project.xml</extend>
> maven doesn't seem to read in build.properties (and project.properties
> either I guess) from the master project. This is a real PITA, as I don't
> want to force people to put identical build.properties files in all the
> subprojects, and it's not acceptible to have a build.properties file in
> the user directory, as it will trample the version for other projects.
>
> I think I'm missing something, as this is a big hole. What are other
> people doing in this situation?
>
> Regards,
> Colin
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
