It certainly seems that use of Maven by those whose project is a
software development tool called Jetspeed should be different from those
who are trying to build an application portal based on this tool
possibly in combination with other tools..
If I am building the Artifact Software e-learning portal, my maven POM
will be quite different than the POM that the Apache Jetspeed team will
want. The contents and usage of the Maven configuration files will be
completely different.
As project manager, I only have control over the central build files and
most of my staff should have nothing in ${user.home}build.properties
unless they have a non-standard test facility on their own PC.
It would be useful to have the discussion about how the Jetspeed
installation and download packages should be different for these two groups.
I am working on the getting started documentation and now is the time
for the experienced portal developers to make their views known.
Specially appreciated are the "thing that I know now that would have
been good to know before I got started with Jetspeed-2".
Ron
Scott T Weaver wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
