Hi Doug, Answered inline...
On 8/3/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
parent not being released. Is there a way to release the parent pom without have to build all the children? I wouldn't mind doing this once but it could be an ordeal if you had to do it every time a dependency was added to the parent. In short, can a parent pom be released in isolation of it's members?
mvn -N will keep Maven from traversing into the submodules, so you can use mvn -N install to only install the parent pom without going into all the children and building/installing them.
a. Can I use uberwar to merge this local client files into a publish platform war?
Uberwar does not exist for M2. Take a look at Assembly plugin or take advantage of the ability of the WAR plugin to "overlay" wars.
b. Can I dynamically set the artifactId? If not then I would need 1 POM per client which probably wouldn't scale. In this event I may need to consider using ant for this step. Has anybody had to deal with this before?
You might be able to pass artifactId as a property that is passed from command line or a profile file.
Does anybody have any examples of how you'd go about creating an artifact like this? I.E. Kick off a war process, then zip it up? If not zip, then jar? I'd also need to be able to control what stuff actually made it into the generated artifact.
The assembly plugin is your friend. Or you could try doing this with <finalName> instead, but I think assembly is the right answer. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
