Perhaps the war of words can be out aside and we can get back to the discussion at hand: Should the Maven work be put in place for M1 or wait until M2. It seems that Steve has done most of the work needed to get the Qpid Java stuff building using Maven. It may need a bit of polish, but it is mostly there. Based on Robert's comments it sounds like there is also work that is required to get the Ant builds working properly also. So which work is most valuable to do? From the votes posted on this thread the community feels that using Maven is a desirable goal for the future of the project. If that is so, it makes sense to do the Maven work in lieu of doing the Ant work. If that is not the case, then do the Ant work.
> -----Original Message----- > From: Robert Greig [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 14, 2006 1:12 PM > To: [email protected] > Subject: Re: Maven build > > On 14/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote: > > > > And in the context of your email I read that as implying > that maven > > > was part of that. Maybe that was a misinterpretation but it > > > certainly read like that to me. > > > > Saying that "maven is required" would clearly be provably wrong, > > wouldn't it? So why would you think that that's what I'm saying? > > I have no idea what you believe or don't believe, I can only > interpret based on what you write. > > > Actually, no. It was mere days of effort. I was traveling > for several > > weeks in the middle of that work, and once I got back into > the work, I > > ran into the issue of the poorly-structured tests. I tried multiple > > avenues around the test issues and around the junit4 issues, which > > took a few days, but once I refactored the tests, the new > mvn branch > > took just a few hours on Sunday to put together. > > But you stated in an earlier email that you were working > until 2am yesterday on it? Or am I putting words in your mouth again? > > RG >
