yes you need to set the *type* to war <dependency> <groupId>com.mygroup</groupId> <artifactId>com.mygroup.underlay.web</artifactId> <version>[1,2-!)</version> <type>war</type> </dependency>
If your underlay defines depedencies then i found it better to do it like this... build the underlay way with a classifier so the war ends up as an attachment to the main artifact, depend apon the main artifact and the war file... you get dependency resolution (normally masked by war depedency) as well as the underlay <dependency> <groupId>com.mygroup</groupId> <artifactId>com.mygroup.underlay.web</artifactId> <version>[1,2-!)</version> </dependency> <dependency> <groupId>com.mygroup</groupId> <artifactId>com.mygroup.underlay.web</artifactId> <version>[1,2-!)</version> <type>war</type> <classifier>underlay</classifier> </dependency> On Tue, 18 Dec 2007 13:09:42 Jan Torben Heuer wrote: > Michael McCallum wrote: > > create a war project with just those images css... > > > > depend apon it from all your other war projects... the war plugin will > > cleverly use the image/css war as a base when building... > > Recently I tried to depend on a war project - but it was not possible to > download it - maven always searched the .jar-file in the repository? Did I > do something wrong? > > Jan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
