I have done it that way for a few of my projects. On Tue, May 31, 2011 at 2:59 PM, Geoff Clitheroe <g.clithe...@gmail.com>wrote:
> I haven't done this but I'm pretty sure you could add an artifact > child to dependency with type war. > > > http://ant.apache.org/ivy/history/latest-milestone/ivyfile/dependency-artifact.html > > I would try something like the last example except with type war. > > Cheers, > Geoff > > > On Wed, Jun 1, 2011 at 7:15 AM, Jefferson Magno Solfarello > <jmagno...@gmail.com> wrote: > > Hello all, I have two projects here: > > > > One called *bp.ws.bp.ws.brokerinformation.war* > > And other called *bp.ws.bp.ws.brokerinformation.ear * > > > > The idea of the ear project is to assemble an ear file with the war file > and > > a specific application.xml file > > > > On the bp.ws.bp.ws.brokerinformation.*war*, I have on my ivy.xml: > > > > <publications> > > <artifact name="bp.ws.brokerinformation.war" type="war" > ext="war"/> > > </publications> > > > > So, it publishes a file called bp.ws.brokerinformation*.war.war* > > It's a requirement here (and not a problem) having .war twice (one for > the > > name of the project and other for the extension of the file) > > > > On the bp.ws.bp.ws.brokerinformation.*ear*, I have: > > > > <dependencies> > > <dependency name="bp.ws.brokerinformation.war" rev="1.0" > > transitive="false"/> > > </dependencies> > > > > The dependency is module level, right? > > When I run <ivy:resolve> on it, Ivy is trying to find the file > > bp.ws.brokerinformation.*war.jar* that is not in my repository, I have > there > > bp.ws.brokerinformation.*war.war* > > > > Am I doing something wrong? > > > > Regards, > > > > Jefferson > > >
