incubator-easyant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Louis Boudart <>
Subject Re: Build configurations
Date Thu, 21 Mar 2013 20:07:46 GMT
Easyant is build on top of ivy. Our entry point is a module descriptor (a
pure ivy file) where you will describe:
 * standard ivy informations such as project name / version / dependencies
 * informations introduced by easyant like :

You can associate the following things with a particular build

   1. Property values
   2. Plugins
   3. Dependencies (de facto as we uses ivy :))


I was wondering: What's the idea behind reusing Ivy configurations for
different build profiles?

I've read [1], and I understand the general notion of loading different
sets of plugins/properties for different use cases. I however don't see any
direct connection between how Ivy uses configurations (to specify different
sets of artifacts and dependencies) with your usage. (The property
EasyAntMagicNames.ACTIVE_BUILD_CONFIGURATIONS does not seem to be read

So the question is - why do your build profiles need to be Ivy

Best regards,


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