I would prefer to stick to ant for 4.0, particularly because switching now could be a barrier to some devs in their progress toward bugfixing 4.0, if they have to take some time to get their build environment working again... unless it's the very last thing you do.
On Thu, Aug 16, 2012 at 3:26 PM, Chip Childers <chip.child...@sungard.com> wrote: > My preference is, based on timeline, to use ant for 4.0. > > - chip > > Sent from my iPhone. > > On Aug 16, 2012, at 5:12 PM, David Nalley <da...@gnsa.us> wrote: > >> Hi folks, >> >> I am particularly limiting the scope of this to what we do for 4.0, >> since that is the pressing timeline. >> >> Here are the current options: >> >> * Continue using ant, and have the hacky stuff I wrote as ant targets >> deal with dependency resolution. (see the differences in the deps-ctrl >> branch) >> >> * Use Gradle (see the gradle branch) >> >> * Use Maven (I haven't seen any of this, but Darren reports that he >> has this building - Darren: can we see this somewhere publicly >> perhaps?) >> >> While I'd like to have us choose the system that we are going to use >> for all time (and despite some reservations, I think Maven is likely >> my personal choice for what we should move to long term), I am also >> concerned that we don't let the perfect become the enemy of the good. >> So given all of that - what should our choice be? >> >> --David >>
