That's what I am doing. The initial war that has the applet pieces is the
thing that fails when the install plugin tries to do its thing because the
war plugin seems not to be providing a main artifact to it.
Anders Hammar
Tue, 11 Jan 2011 23:09:31 -0800
Why isn't the war the primary
And that's because you've configured the war plugin not to make it a primary
artifact. Remove that.
/Anders (mobile)
Den 12 jan 2011 16.56 skrev Mike Calmus m...@calmus.org:
That's what I am doing. The initial war that has the applet pieces is the
thing that fails when the install plugin tries
thing that fails when the install plugin tries to do its thing because the
war plugin seems not to be providing a main artifact to it.
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
configuration
I am trying to create a non-primary war that includes an applet jar and its
dependencies. This war is then merged into a larger war.
When I try to do this, though I get an error from the Maven Install plugin
indicating no primary artificat was created. The error returend is somewhat
different
Why isn't the war the primary artifact?
I would suggest you structure this as two modules; the first creates the war
that includes the applet and the other one is the larger war.
/Anders
On Tue, Jan 11, 2011 at 21:22, Mike Calmus m...@calmus.org wrote:
I am trying to create a non-primary war
