Hi all,

I've just checked in a cleanup of maven project.properties files using the
maven 1.0-rc3 properties inheritance feature.
Furthermore, I've normalized the public J2 configuration properties and ensured
all have now a proper reverse url prefix.
Finally, cleaned out some obsolete files and added a few Apache 2 license headers.

To be able to build the latest J2 codebase ensure you have also the latest
maven-1.0-rc3 installed.

Also, checkout the updated http://portals.apache.org/jetspeed-2/getting-started.html
which describes the new set of configuration properties.

Regards,

Ate

Ate Douma wrote:
Hi all,

With the new maven-plugin several, yet undocumented, required properties were added.
I want to get these properly documented but after looking at the project.properties files
scattered throughout the codebase I've come to the conclusion that first performing a clean up
of too many duplicated properties is in order and that we should use proper reverse url prefixes
for J2 specific properties (like: org.apache.jetspeed.server.home instead of catalina.home).


Since maven 1.0-rc3, project.properties is inherited from parent projects while
still allowing overrides.
This means we can define default values for required properties in J2/project.properties alone.
The ${USER_HOME}/build.properties can then be used to override those where needed, but out of
the box it should already work without it.
Documenting (and keeping that up to date) of the required properties will also be much easier.


So, I propose we require maven-1.0-rc3 to be used for building and deploying J2.

If this is accepted I propose to clean up all the unneeded properties and ensure that all the J2
specific properties use reverse url prefix (I'll do the work then).



Regards,

Ate



---------------------------------------------------------------------
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]



Reply via email to