+1 I think we should remove the Maven2 poms from the trunk, if only because leaving them leads people to trying it first and we already know it's not exactly a positive experience.
alex On 5/4/07, Paul Brown <[EMAIL PROTECTED]> wrote:
+1 from me to buildr. More likely to be working builds is better for our customers (i.e., community). On 5/4/07, Matthieu Riou <[EMAIL PROTECTED]> wrote: > Hi guys, > > I'm going to build a new release candidate for ODE, fixing the few problems > here and there that were still pending on RC1. I've switched to our rake / > buildr based build for the release simply because Maven2 is so unmanageable. > So all our releases are built with buildr (which does the job quite well). > > I'm thinking that we should actually use buildr as our default build system > for ODE. We'll have to support our releases for some time (I'm thinking of > the source release here) and I'm very uncomfortable doing so with Maven2. It > just breaks too easily. > > Any objection? Somebody who's such a Maven2 lover that he's willing to > maintain the Maven2 build? > > Cheers, > Matthieu >
