ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Enderling" <TEnderl...@intershop.de>
Subject Native dependencies
Date Thu, 18 Oct 2012 17:46:22 GMT
Hi,

from reading some old threads from 2009 I found that configuration
intersections were introduced in order to allow a more elegant solution
to declaring dependencies to platform specific modules/artifacts. I have
however not yet found how to actually use configuration intersections
for this purpose.

1. I would like to model different platforms as configurations, i.e. a
configuration win, another configuration win32 that extends win, another
configuration win64 that extends win32.
2. I would like to specify in the conf attribute of an artifact:
- The platform(s) it is compatible too. If specifying win, it should be
compatible to win32 and win64 (which is probably already dealt with by
using 'extends'.)
- One or more non-platform-configurations in which the artifact should
be included, like common, develop, test.
3. I also would like to specify in the conf attribute of a dependency:
- The platform(s) it is compatible too. If specifying win, it should be
compatible to win32 and win64.
- One or more non-platform-configurations in which the dependency should
be followed.
4. When resolving I want to specify one or more
non-platform-configurations and a platform. All artifacts compatible to
that platform and contained in any of these configurations should be
retrieved, the others omitted. All dependencies compatible to that
platform should be followed, the others omitted. The mapping should make
sure that the platform is passed down to the dependent modules.

The combination of inheritance (extends) and intersections seems to make
this a very troublesome adventure - at least I haven't really
acomplished this, yet.

Do you have any working setups for this?

Best regards,
Tim Enderling

Mime
View raw message