Multiple Primary Artifacts from a Single WAR Project

[Shelley <ra...@gmail.com>]

I have a single web project which requires three distinct .war endstates,
where the only difference between each are the runtime dependencies (some
configuration files may also be different in the future).  Are there any
recommendations for accomplishing this?

Some background:
* The assembly plugin does not seem appropriate here, since the various
endstates are all primary artifacts; which leads me toward creating at least
a separate war project for each.
* WAR overlays currently seem to work, however, this requires me to create
essentially an "abstract" web project, which, although it compiles, does not
run (until it is declared as a dependency within another war).

Re: Multiple Primary Artifacts from a Single WAR Project

[Wayne Fay <wa...@gmail.com>]

I'd take the overlays approach with an "abstract" web project,
resulting in 3 separate poms and projects, and thus 3 separate "war
endstates" as you called it.

Wayne

On 8/31/07, Shelley <ra...@gmail.com> wrote:
> I have a single web project which requires three distinct .war endstates,
> where the only difference between each are the runtime dependencies (some
> configuration files may also be different in the future).  Are there any
> recommendations for accomplishing this?
>
> Some background:
> * The assembly plugin does not seem appropriate here, since the various
> endstates are all primary artifacts; which leads me toward creating at least
> a separate war project for each.
> * WAR overlays currently seem to work, however, this requires me to create
> essentially an "abstract" web project, which, although it compiles, does not
> run (until it is declared as a dependency within another war).
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org