If HiveMindTestCase doesn't need to change to compile, then everything should be okay. We're marking the easymock jar as optional in our pom. So, if you provide another one that's newer and HiveMindTestCase still works, it should be good to go.
-----Original Message----- From: James Carman [mailto:[EMAIL PROTECTED] Sent: Sunday, June 18, 2006 9:33 AM To: 'Tapestry development' Subject: RE: easymock Did you have to do anything to upgrade? Is there an incompatible API change? -----Original Message----- From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] Sent: Sunday, June 18, 2006 1:57 AM To: Tapestry development Subject: Re: easymock Ah sorry about that Kent. I felt badly enough about my goof and any trouble that you might have run into that I went through the pain of upgrading everything already. :( I should probably have been more vocal about what I was doing, didn't know other cooks were coming into the kitchen. Not sure how everyone else feels, but can't imagine hivemind has ~more~ unit tests than tapestry - so maybe they would like to upgrade as well ? ;) (theoretically we should be independent in that regard besides the HivemindTestCase cross-over ? ) As long as we're on the subject, I should warn everyone that I also plan/would like to change our unit tests to use TestNG as well. It's the only reason I went through all those months of interaction to make sure it was in maven2 to begin with. This of course doesn't need to happen ~right~ now, but it should hopefully be something done relatively soon as we finish our migration to maven2. (just thought I would throw that out in case people thought it was a more casual choice ) Of course I am not the only developer here, so people should feel free to speak up if there are any concerns. I'm not as good at being delicate with words so hopefully any bluntness on my part won't be perceived too badly.. On 6/17/06, Kent Tong <[EMAIL PROTECTED]> wrote: > > Kent Tong <kent <at> cpttm.org.mo> writes: > > > > > > Oops! Now I know what Kent was talking about in regard to > easymock...We're > > > upgraded now! > > > > Do we really want to upgrade? As Hivemind 1.1 is using easymock 1.1, I > think > > we should stick to 1.1. What do you think? > > BTW, last night I just finished making maven2 build all the modules in > tapestry 4.1 properly and all tests pass (still with easymock 1.1). Now > all the code uses easymock 2.2. It's OK, but I'd like to know which > version to use. > > -- > Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
