"John Coleman" <[EMAIL PROTECTED]> writes: > The web.xml in the dependency war does seem to be ignored so this is > quite a neat solution. :) > > We are using this to provide a library of resources all our web > applications can draw from. > > I still don't have a good answer on how to do what I call client > flavours. The client may need to have tweaked js, their own images and > properties files instead of plain-vanilla. > > I don't see this as fitting the dependency concept very well - because > we really need a switch at build time to control which set of assets > to incorporate. The main nasty occurs if we have tweaked scripts > because ideally we don't want to clone large pieces of script, just > for small client tweaks. This is particularly unpleasant in terms of > vcs. What we really need is all the tweaks to be parameterised in some > way so they work like components and can be snapped in. > > We may have to create our own "flavour" plugin. Is there a way to have > resource directories in the Maven project that are ignored by default, > and then switch a selected one on to merge into the target? Possibly > we might have a properties file that tells Maven to ignore certain > resource directories? I don't really want to config this inside the > POM. >
What I did was the following: - define the filter file to use as a property - define profiles for the different flavo(u)rs, each setting its own dependencies - at build time, choose profile and set the filter file(s) properties so that they correspond to the 'flavour' you build. I did this to build three different web apps: 1. one with the real business layer and addresses 2. one with the test dao layer 3. one with a mock business layer out of the same presentation layer. Regards, -- OQube < software engineering \ génie logiciel > Arnaud Bailly, Dr. \web> http://www.oqube.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
