Great, that fixed that problem. It was (fortunately) a package under my
control.
But now I have a further problem.
It complains:-
[INFO] Deployment
descriptor: ... /AdminEar-0.0.1-SNAPSHOT/META-INF/application.xml does not
exist
Now in pom.xml I have,
...
<configuration>
<version>5</version>
<generateApplicationXml>false</generateApplicationXml>
...
In EJB Version 5 application.xml is not required. I found a hit on google
from a while back saying that this problem existed, and making reference
to a new version of the maven-ear-plugin (2.3.2) which fixes this, but
the latest version in the central maven repositories is 2.3.1. Does the
new version exist, and if so how does it get uploaded to the central
repository?
David
On Saturday 21 February 2009, Stephane Nicoll wrote:
> You have a transitive dependencies of type zip which seems pretty bad to
> me.
>
> mvn dependency:resolve will give you the list of dependencies
> mvn dependency:tree will explain where this zip dependency is coming from
>
> You can use excludes or you can fix the project you own it.
>
> HTH,
> Stéphane
>
>
> On Fri, Feb 20, 2009 at 10:08 PM, David Goodenough <
>
> [email protected]> wrote:
> > I am trying to use the maven-ear-plugin, and I keep getting:-
> >
> > [INFO] Failed to initialize ear modules
> >
> > Embedded error: Unknown artifact type[zip]
> >
> > I have tried using -X to get the debug messages, but I can not
> > see where it is finding a ZIP file to use as an artifact. There are
> > three modules I have specified (all jar files), but nothing else.
> >
> > How do I find out what it was trying to package that is causing it
> > to try package a ZIP file.
> >
> > David
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
