> Personally, Im starting to think that putting properties in your
> $HOME/build.properties was a bad idea. Instead, each project should
> probably edit its build.properties directly in the project root (but
> don't checkin the build.properties). The Jetspeed Maven Plugin generates
> a "build.properties.sample". Recommend changing docs to say "edit
> build.properties.sampe file, and rename it to build.properties" and drop
> the sentence: "Set or override the build or maven-plugin properties in
> your ${USER_HOME}/build.properties file."
${HOME}/build.properties is an absolute requirement for me as all of my
builds run from automated build servers which have properties that differ
for each build server (staging, test and production). Having a single
build.properties housed in the CVS within the project does not offer the
flexibility my builds require.
Regards,
-Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
