Apolologies for that one, I've really only been keeping an eye on M2 with junit-toolkit snapshots. Pinning it to the version, as you have done is a perfectly good solution for the moment. Reason I am using snapshots is because otherwise I cannot check my code in when the toolkit is changed, as I have to wait 4 or 5 days to put a new release out on the central repository.
Once the testing stuff on M2 is complete, it will be merged/copied wholesale onto trunk anyway, and I will put out a proper release of the toolkit too. Also, lets not forget those M2->trunk Java merges that Martin made, that are currently in limbo somewhere... That would have fixed this problem too. Rupert On 03/08/07, Rafael Schloming <[EMAIL PROTECTED]> wrote: > > I just had to fix the trunk build again. This time the culprit was more > sloppy submits and the SNAPSHOT dependency on junit-toolkit. Apparently > the latest junit-toolkit SNAPSHOT breaks some of the APIs we depend on. > > I've changed the junit-toolkit dependency from 0.6-SNAPSHOT to > 0.6-20070718.144514-11 as an immediate workaround, but someone in the > know should take a look at > org.apache.qpid.interop.coordinator.Coordinator and determine an > appropriate fix. > > FWIW it seems like a really bad idea to ever use the SNAPSHOT feature of > maven as our build can be arbitrarily broken by changes in other projects. > > --Rafael >
