A project should create either a jar, or an ear, not both. Split it up into two projects.....
On Sat, 26 Jun 2004 13:55:16 +0200, Manfred Wolff <[EMAIL PROTECTED]> wrote: > > Hi > > I have a project that builds a jar file a.jar *and* and ear file calls > a.ear. The ear file must contain the jar file. > > <dependency> > <groupId>a</groupId> > <artifactId>a</artifactId> > <version>0.1-dev</version> > <type>jar</type> > <properties> > <ear.bundle>true</ear.bundle> > </properties> > </dependency> > > This dependency crashes by building the jar file, because the jar will > be created with the jar:jar goal. The jar goal will dissolve the > dependency and finds not the a-0.1-dev.jar, because he will create it. > After that I call the ear:ear goal and will include the jar just been > created. Has anyone a solution for this. > > I need dependencies that are only valid for specific goals like > > <dependency> > <goals> > <goal>ear</goal> > </goals> > <groupId>a</groupId> > <artifactId>a</artifactId> > <version>0.1-dev</version> > <type>jar</type> > <properties> > <ear.bundle>true</ear.bundle> > </properties> > </dependency> > > Manfred > > --------------------------------------------------------------------- > 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]
