>From a CM perspective it is essential that published ivy files be completely >resolved and self-contained. Otherwise we lose - or greatly complicate - >reproducability and traceability.
-steve Stephen Nesbitt Senior Configuration Management Architect The Cobalt Group -----Original Message----- From: Xavier Hanin [mailto:[EMAIL PROTECTED] Sent: Wed 11/15/2006 9:53 AM To: [email protected] Subject: Re: Should ivy.xml enable dependency imports? On 11/15/06, easyproglife <[EMAIL PROTECTED]> wrote: > > Hi. > > My situation is like this: > > I have many projects each one with its own ivy.xml. > I see that many of them share the same dependency. > > Do you think it makes sense to support dependency-import from a common > ivy.xml fragment file? Some kind of Ivy file inheritance as with pom inheritance? It makes sense, and may allow us to reach a better level of compatibility with m2. What I wouldn't like to see however is such imports in published ivy files. IMO ivy files in the repository should be self contained. Xavier To be specific, I use the 2.2 use case as described here: > http://wiki.apache.org/ivy/IvyUseCase > Each project has the dependency on the same properties file. > > Is there a way not to duplicate the dependency code across all ivy.xmlfiles > in all the projects? > > easyproglife. > >
