Re:Apache Ivy – any future or is it also going to be retired?
by pjmlp on Monday December 05, 2016 @02:19PM
(#13108374)
I have spent one year taking part in a multi-team project to fix a build system, because everyone made their own little changes in Ant.
A chaos in a three site distributed system, with around 300 developers at its peak.
In this regard, Gradle is even worse than Ant in what concerns keeping a build infrastructure clean.
Re:Apache Ivy – any future or is it also going to be retired?
by perrylaj on Monday December 05, 2016 @02:48PM
(#13108707)
Oddly enough, my experience was quite opposite of yours, but it sounds like the scope of your system might be a little larger than ours.
The key to cleanliness (from my perspective) was to create versioned plugins for any build functionality that was required in more than one subproject. This simple rule prevents spaghetti task dependencies and maintains sanity for everyone. It gives us the best of both worlds -- a little bit of flexibility when needed for one-offs, but then a well defined DSL via plugins for anything that is done more frequently.
The problem with that is that it doesn't work with slow / compiled languages. That's the worse thing about Maven (tied with the insane unnecessary complexity of the plugin architecture). The dev cycle for trying out a new plugin is atrocious. Compare that to editing a local copy of a Python, Ruby, or Groovy script.