Sure. The problem you're going to have with this is, both jar:jar and
war:war (if that's the right mojo name) will set the main project
artifact to their respective output...leaving you with the question
"Which one will be installed in the local repository" and the more
important question "Which one will get RELEASED?"
To me, this is a question of decomposition. You have common code used
by two projects, so factor it out into a separate project. The fact
that one of the projects only decorates this common code with as-yet-
uncompiled JSP or similar doesn't change that fact.
Just my $0.02.
-john
On Aug 16, 2007, at 10:27 AM, Mel Riffe wrote:
Hi David,
I think the "Maven Way" suggests you have a project for the Jar and a
project for the War.
However, executing 'jar:jar' within the project should produce the
desired
results.
HTH
Mel
On 8/16/07, David Williams <[EMAIL PROTECTED]> wrote:
Hi Eveyone,
We currently create a war file for a certain artifact. Now
another group
has created an application that requires the first artifact to be
a jar
not
a war. Is there any way to have maven create both a jar and a war
for a
single artifact?
Thanks,
David
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
