Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (hermes.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <9809708.post@talk.nabble.com>
Date: Tue, 3 Apr 2007 05:56:07 -0700 (PDT)
From: smu <saulius.sinkunas@delfi.lt>
To: ivy-user@incubator.apache.org
Subject: Re: Common dependencies
In-Reply-To: <635a05060704022226w210459b5r2577461af0ad7655@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <9694201.post@talk.nabble.com>
 <635a05060703270826x4dae01adtec28ffb9038e6ffa@mail.gmail.com>
 <9797003.post@talk.nabble.com>
 <635a05060704022226w210459b5r2577461af0ad7655@mail.gmail.com>


Hi,

> http://www.nabble.com/ibiblio-resolver-and-optional-pom-dependencies-tf3497317.html

Thanks - I will have it in mind.

> This seems to be a bug. Could you give more details (like pointing to a
> pom
> using project.name, or pointing to a maven doc page explaining how we
> should

Sorry, it was my mistake. i had in mind {project.groupId} and
{project.version}.

When version 2.0 is going to be released?

BTW is it possible to receive all posts in this forum to email? I subscribed
to ivy mailing lists (using email) but still don't receive new posts. I
tried to subscribe 2 times but didn't receive any response.

Bye,
Saulius

> Saulius
>
>
> Xavier Hanin wrote:
> >
> > On 3/27/07, smu <saulius.sinkunas@delfi.lt> wrote:
> >>
> >>
> >> Hi,
> >>
> >> I'm trying to migrate to ivy from maven and have one question. Is it
> >> possible to create some common dependencies for multimodule project?
> >> Something like parent and child pom.xml in maven2. For example, I'm
> using
> >> Spring in almost all modules but don't want to declare it in every
> module
> >> (as in case of version change I will have to update all ivy.xml files).
> >> Is
> >> it possible to do with ivy?
> >
> >
> > Ivy do not support parent/child like maven, but you can do something
> very
> > similar by using virtual module. A virtual module is a module which
> > publishes no artifact at all (put an empty publication section in its
> ivy
> > file, since no publication element at all is equivalent to publishing
> one
> > jar artifact).
> >
> > Then when you declare a dependency on it, you will transitively get all
> > its
> > dependencies, and only its dependencies since it doesn't publish any
> > artifact.
> > The advantage is that you can obviously declare multiple dependencies
> like
> > that, so you are not limited to single level inheritance of maven
> > parent/child mechanism.
> >
> > HTH,
> >
> > - Xavier
> >
> > Thanks,
> >> Saulius
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Common-dependencies-tf3473658.html#a9694201
> >> Sent from the ivy-user mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Common-dependencies-tf3473658.html#a9797003
> Sent from the ivy-user mailing list archive at Nabble.com.
>
>


-- 
Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/


-- 
View this message in context: http://www.nabble.com/Common-dependencies-tf3473658.html#a9809708
Sent from the ivy-user mailing list archive at Nabble.com.