ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mitch Gitman <>
Subject Re: Ivy Settings Conditionally Use an Environment Variable?
Date Thu, 02 Aug 2012 15:08:29 GMT
Nicolas is reminding me of some context I left out of my original answer.
Certainly, Ivy settings should be reusable in IvyDE or the equivalent
plugins for other IDEs. Certainly, Ivy settings should be able to stand on
their own independent of "the build."

For this, I've found that it's best to extract these properties into
properties files that can be commonly used between the build and the IDE.
See Ivy->Settings under IvyDE preferences. I think maybe my greatest
reticence about putting property definitions in Ivy settings XML is that
inevitably you find this pure configuration being scattered about and
becoming difficult to maintain. Better to put it in common files that can
be pulled in selectively depending on environment and reused.

As with so many of these things, I'm expressing a preference, not a mandate.

On Thu, Aug 2, 2012 at 5:03 AM, Nicolas Lalevée

> Le 2 août 2012 à 10:45, Eyad Ebrahim a écrit :
> > I'm not sure if it's necessary to include this feature in Ivy. Ivy is
> > supposed to compliment ant, and used along with it.
> > Doing this, is to invite un-welcomed practices into Ivy usage. The code
> > with be lost between ivy and ant.
> If a part of the ivy configuration is to be defined/computed in an ant
> script, how it is supposed to work within in the IDE ? Ant is very nice for
> headless build, but is too slow for an development in an IDE. So I see only
> two options: either make the ivysettings independent, or generate the ide
> metadata via ant. I have always worked with developers who prefer managing
> their IDE themselves since each one has its preferred setup or tool. So I
> tend to prefer the former solution.
> Also note that even if Ivy is really well integrated with Ant, there are
> many use outside of it. Within IDE like IvyDE or IvyBeans for instance. And
> some new build tool are using it for their dependency management (see
> gradle, sbt, easyant).
> IMHO of course too :)
> Nicolas
> > IMHO of course.

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