[Magic] Transitive Dependencies
cameron.taggart at gmail.com
Tue May 3 11:54:47 EDT 2005
I am trying to avoid explicit versioning of the required resources for each
dependency. In the Service Project I would like to do something like:
<import uri="artifact:module:com/company/daos-1.2" />
and have it magically use all of the resources which that version was
released with. I just have not been able to successfully set this up yet.
The .module file that I end up creating doesn't end up containing any
On 5/2/05, Niclas Hedhman <niclas at hedhman.org> wrote:
> On Tuesday 03 May 2005 04:51, Cameron Taggart wrote:
> > Let's say that DAO's wants to upgrade from Hibernate v2.x to Hibernate
> > Under the current build process, all the projects must update their
> > dependencies.
> If you only have 4 tightly coupled projects, then it is true that they all
> will be updated in the same go.
> However, you _can_ (not sure if it is good) have one index.xml per project
> in each declare the explicit version of those resources that you want
> different versions on.
> > Any good solution? Does module support fit the bill?
> Modules is about "a collection of projects", that converts the <project>
> elements into <resource> elements, and not really related to your
> Modules allows you to "forget" the individual projects in a collection,
> just do a <import> on the entire module, and you know that you have all
> resources available.
> For instance, you do
> <import uri="artifact:module:dpml/metro/dpml-metro-public#2453" />
> and you know that all the different public APIs of Metro will be available
> resources, and that their dependencies are brought in as well.
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
More information about the dev-dpml