David Dyer went down the Option 3 route so I thought that I would try 1)
modified to use Eclipse.
Just to get with the program, I will start working on 3) under Eclipse.
David and I will start to work together a bit more as well so that we
can reduce the number of problems that we need help with.
I would still be interested in your suggestions about how minimize the
impact of the release of Jetspeed 2.3 or Jetspeed 3 on our Portal project.
Ron
David Sean Taylor wrote:
On Apr 30, 2007, at 5:20 AM, Ron Wheeler wrote:
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?
We provide you with three choices:
1. a Maven-1 custom build project as defined here:
http://portals.apache.org/jetspeed-2/getting-started-binary.html
2. a Maven-2 custom build project as defined here:
http://portals.apache.org/tutorials/jetspeed-2/
http://wiki.apache.org/portals/Jetspeed2/Maven2BuildSupport
3. an Ant custom build project (still writing the documentation on
this one, the docs will be ready this week)
You can dl the Ant custom build example from here:
http://www.bluesunrise.com/training/ant/
And follow the instructions from an email on this list from last week
I prefer #3, as that is what I am now teaching in Jetspeed training
courses
---------------------------------------------------------------------
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]
