I had similar issues several times, the trick for me was to start to use
ant at a certain stage to do the customer specific resource handling.
Also what could be possible would be to use SVN branching to be able to
switch between customers (perfect job for svn branching if you ask me)
Werner
Richard Wallace wrote:
Hey everyone,
I've got an interesting question that came up while working on my last
project that I'm hoping someone has an answer to. Basically, the
situation is that there is a base webapp that has all the basic features
of the application. But, we plan on licensing it to clients and do some
customization for them, like custom user registration system, custom
skinning, etc. The thing is that most of the JSPs and other resources
from the base webapp can remain the same but a few will need to change
(logos, css, etc.).
Right now we don't have a good way of doing this other than to copy ALL
the JSPs over from the base into the sub-projects and modify only those
that need it. The problem we're running into is that adding features to
the base webapp and propagating them to the sub-projects is quickly
becoming a major PITA.
What I was thinking was that it would be nice if there was a way to do
something like an "overlay" of the webapp. So that the base webapp
would be unrolled first and then the sub-projects webapp would be rolled
out over top of that replacing any files that were modified and keeping
anything that wasn't. That way we would only have to maintain JSPs and
resources in the sub-project that are specific to that clients
customizations.
Is there anything out there that solves this problem already? Have
others run into this and what have you done? Any input would be
appreciated.
Thanks.
Rich
