Looks like this might have been a problem in Geronimo. The trunk's openejb dependency was recently switched from 3.0.0-SNAPSHOT to 3.0-SNAPSHOT but one set of references was not updated.
Jarek On Mon, Feb 25, 2008 at 3:51 PM, David Blevins <[EMAIL PROTECTED]> wrote: > > On Feb 25, 2008, at 11:56 AM, Jarek Gawor wrote: > > > David, > > > > Maybe the published snapshot is invalid. We see that error in Geronimo > > builds and that's always built with an empty ~/.m2/repository dir. > > Got to be something like that. I published on saturday after the > change, but you never know. > > Published new snapshots. > > -David > > > > > On Mon, Feb 25, 2008 at 2:48 PM, David Blevins > > <[EMAIL PROTECTED]> wrote: > >> > >> On Feb 25, 2008, at 12:29 AM, Jacek Laskowski wrote: > >> > >>> On Sun, Feb 24, 2008 at 9:03 PM, David Blevins > >>> <[EMAIL PROTECTED]> wrote: > >>> > >>>> Maybe do a clean build or a fresh svn checkout. There's definitely > >>>> nothing wrong with that class. > >>> > >>> Geronimo's build keeps crashing on the class as well so it's not > >>> only > >>> me who can't build openejb3 :( > >> > >> Have you tried doing a fresh svn checkout? Maybe rm -r the openejb > >> section of your ~/.m2/repository? > >> > >> I've built on three machines (osx, freebsd, and windows xp) all with > >> no issues. > >> > >> -David > >> > >> > > > >
