I think its safe to say Maven is a lot more mature now than it was back then, and is much more widely used. The issues that existed then certainly don't seem to bother the massive numbers of large projects using it today.
Given how popular it is with other developers as a build system and as a route for their projects to consume artifacts, I'd generally be in favour of making the switch if only to be nice citizens to prospective users of proton. Robbie On 23 Jul 2012 20:00, "Rajith Attapattu" <[email protected]> wrote: > I personally prefer the simple ant based system. > The last time Qpid used maven it was horrible :) .. it downloaded the > entire universe into my computer. > We also had trouble doing repeatable builds. > Now I don't know if it was due to the way Maven was used or if it was > an issue with Maven itself. > I've never had issues with ant before --- it always worked for me :) > With Maven it wasn't particularly a pleasant experience. > So I'm biased there and please don't blame me for that. > > Having said that, I'm not going to make a fuss, if the majority wants > Maven ! > > One more thing. Converting the build system to maven is fine, but who > ever does that should also take the responsibility of maintaining it > as well :) > To a certain extent that was also an issue with the previous attempt > at using maven. > > Rajith > > On Mon, Jul 23, 2012 at 2:38 PM, Oleksandr Rudyy <[email protected]> wrote: > > Hi, > > > > I completely support Joseph's proposal to use maven as building system > > for j-poton module. > > > > Kind Regards, > > Alex > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
