As our internal Jetspeed portal develops new functionality at the same
time as the Jetspeed project continues to fix bugs and improve, I need a
project structure that will let me upgrade the Jetspeed code without
screwing up my changes.
The top level POM file is certainly not suitable for my project since it
has the wrong project info and a list of developers that I should be
pleased to have on the project but probably will not want to get my
project notes.
What is the best practice for separating core Jetspeed code and project
info from custom portal code and configuration files so that a Jetspeed
upgrade does not wipe out all my customizations?
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
