> I was getting that exact same error! > Roger, see, Im not the only one!
Well at least I'm not going crazy. (yet) > The only fix I had for it was to delete my entire local repository > (maven) > The consensus is that a jar was corrupted, but hell, I had > this exact same problem on 3 different machines here I'll try it on my build server and see if it happens there too. > Im thinking we have some pico jar problems I see in the build > that there are now 2 different pico jars referenced in > different components I think that JS2-46 will solve this, but > if you need a lunch break, delete your repo, and rebuild... Funny thing is, I started off with a clean repo yesterday. I'll try it again, tho. If I still have problems, I'll report back. Thanks again! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
