ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Santos" <paulinho.san...@gmail.com>
Subject [Newbie] Best practice with configurations
Date Tue, 19 Aug 2008 17:04:36 GMT
Hello everybody,

I'm wondering which one would be the best practice with ivy configurations.

I have a module that have 4 configurations (core, linux, windows and test),
as their name implies, core has the core libraries  and when I build the
distributions for this module I set the classpath in different ways, for
example, core+windows or core+linux and to run the tests on my CI server
core+tests.

They all are stored in different folders since my pattern looks like this:
<ivy:retrieve pattern="${lib.root}/[conf]/[artifact].[ext]" />

 The problem with that, is that if core has a library (e.g.
commons-loggings) and let's say test has a transitive dependency to the same
library, since they are in separated folders, the eviction doesn't work, and
I can end up with two different versions of the same library in my
classpath.

So here is my question, instead of separating and leaving only the
necessaries libraries in each configuration, should I extend core and
duplicate its libraries in test, linux and windows configurations? That way,
I know eviction would work, but would this redundancy be the best solution?

thanks,

Paulo Santos

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message