Tim Dysinger a écrit :
I have a simple war project and I want to extend it by branding it for
each of our customers. The "branded" projects is essentially the same
code as the main project with slightly over-ridden web content (jsps and
images).
What is the simplest way to do this in Maven? I was thinking of making
a seperate project for each "brand" and having ant update the main
project's war file with the over-ridden web content. How would one do
this effectively?
-Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This looks like a skin above your worker project.
Maybe you can acheive your goal by creating
one project for each "skin" holding the skin's flavor.
Each of those skin's flavor projects depends from the worker project.
Each of those projects have to create the war file using its own flavor,
the worker project artifact, all the dependencies artifact, the common
resources (the resources of the worker project).
The worker project's artifact has to become a pure jar (maybe with
common resources).
If the assembly of the flavored war file has the same behaviour with
each different skin, it will be usefull to create a plugin for that
behaviour (on which the skins projects depend) if the behaviour can
not be handled by the sole war plugin.
Wrapping project
+ parent project --------------- for pom common informations
+ worker project --------------- contains the workflow and any thing
that make the work (can be split into smaller projects)
+ skins war plugin ------------- the maven plugin that creates a skinned
artifact
+ skin 1 project --------------- holds the first skin behaviour
...
Raphaël
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
