+1 (non-binding) Maven is much easier to support than the current process. Gradle (if ever) could be done later. Also, there are folks like me that want to use components of cloudstack as libraries w dependencies and the current process is not catered towards that. Maven would.
-A On Aug 7, 2012 11:27 AM, "Andy Gross" <a...@andygross.org> wrote: > > I've heard good things about Gradle, and "because everyone else is doing > it" is rarely a good justification for choosing technologies, but it seems > Maven is the de facto standard for most Apache (and other open source) > projects. If integrating Cloudstack in other environments or extending > Cloudstack are important for developers and users, Maven might be the > easiest way to go. > > Just my .02. > > - Andy > > > > On Aug 3, 2012, at 5:00 PM, Chiradeep Vittal <chiradeep.vit...@citrix.com> > wrote: > > > Gradle seems to be another > > http://www.gradle.org/ > > > > > > Since it is allows scripting (as opposed to configuration xml), it could > > potentially fulfill the waf role as well. > > Anybody have any experience with Gradle? > > > > On 7/24/12 2:19 PM, "Alex Huang" <alex.hu...@citrix.com> wrote: > > > >>> Just out of curiosity, have tools like Ivy and maven been ever > >>> considered for > >>> dependency management? > >> > >> We are looking at these two tools. Our first thoughts is devs should be > >> able to start projects that are tied to other parts of their code so we > >> want this to be as flexible as possible. Maven forces too much of a > >> structure on to the developers. Ivy seems like the right tool to go > >> with. Any comments? > >> > >> --Alex > >> > > > >
