I also took Alex's suggestion to mean leaving the Ant build in place and then adding a Maven build too.
Whilst I have stated my dislike for this idea in the past in relation to the main Qpid tree, if this is what it took to have a maven build for proton I think it would be the way to go, i.e. instead of having an Ant build and making it easy for others to add a Maven build themselves, we should just do it. Robbie On 25 July 2012 18:52, Gordon Sim <[email protected]> wrote: > On 07/25/2012 05:06 PM, Glen Mazza wrote: > >> The problem with providing an Ant build is that non-Maven users, never >> having worked with it, tend to awfulize Maven, and then stick with Ant, >> continuing their misconception of Maven. Maven is really an ice cream >> cone, not a brussels sprout, but sometimes people need to be given a >> push to find that out. :) >> > > Last time I tried it tasted like something much worse than brussel > sprouts! It may have improved since then; it may be that there is a way to > pinch your nose so it doesn't taste quite so bad; it may one of those > flavours that some love and others hate. (It may be I'm stretching the > analogy too far!) > > > Also, burdening Joseph by having him >> create/maintain a separate Ant build also takes away his efforts towards >> creating an awesome Maven build. >> > > I don't think that was what was being proposed. There is already an ant > build in place and I think the assumption was the ongoing maintenance would > not be great given the simplicity of the project. > > It seems like a good idea to me, though as mentioned I don't currently see > myself as a key user/developer in the very near future at least and so > wouldn't want to impose anything on those who are. It would however let > people have a nibble at the latest maven and either be astounded at its > delicious nature or be able to take the bad taste away with a nice bite of > ant. (Sorry, I couldn't resist!). > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
