On Sat, 22 Feb 2003, James Mitchell wrote:
> Did I check those in too soon? If so, sorry about that. No problem. There was only one file affected in this case, and it was easy enough to resolve. In the future, though, it might be a good idea for us to put a freeze on checkins between the tag date and the actual release date. The problem this time around was exacerbated by the long delay between these two points, which is entirely my fault. But freezing the tree would help us avoid potentially messy solutions in the future. By the way, in answer to the question in the subject line, the release is up, and I'm about to send the announcement. Hurrah! -- Martin Cooper > > > -- > James Mitchell > Software Engineer/Struts Evangelist > http://www.open-tools.org/ > > "Beer is the reason we get up each afternoon." > -- Ray McNeill > > > > > -----Original Message----- > > From: Martin Cooper [mailto:[EMAIL PROTECTED] > > Sent: Saturday, February 22, 2003 10:36 AM > > To: Struts Developers List > > Subject: Re: Where's RC1? > > > > > > Thanks, Rob. It seems there were a lot of changes to that > > file when James > > checked in his tests, and I didn't want to include those in the RC1 > > version. So I checked in a version that had just your change > > applied to > > the original RC1 version, and then re-checked in the HEAD > > version so that > > we're back to where we were. I've re-tagged the file for RC1, > > rebuilt, the > > tests are passing, so keep your fingers crossed! > > > > -- > > Martin Cooper > > > > > > On Sat, 22 Feb 2003, Rob Leland wrote: > > > > > After fixing the DTD reference in the struts-config.xml it > > appears that > > > all tests passed, > > > unlike the earlier email I sent you. > > > > > > Though I am not sure about the last test since it doesn't > > seem to report > > > any > > > failure count. > > > ---- > > > [junit] Testcase: testMultiFactory took 2.003 sec > > > [junit] Testcase: testSingleSharedFactory took 0.1 sec > > > [junit] Testcase: testUtilBaseEnvironment took 0 sec > > > > > > stop.tomcat.40: > > > [java] Stopping service Tomcat-Standalone > > > [runservertests] Server stopped ! > > > > > > BUILD SUCCESSFUL > > > ---- > > > Is it supposed to report the Failures like the other tests > > > [junit] Tests run: 3, Failures: 0, Errors: 0, Time > > elapsed: 2.113 sec > > > ^^^^^^^^^^^^^^^^^ > > > > > > -Rob > > > > > > > > > Martin Cooper wrote: > > > > > > >I know this is the question on the tip of all struts-dev > > folks' tongues. > > > >First of all, I do apologise for taking so long to get > > this puppy out. The > > > >tag happened on time, but this has been an insane week at > > my day job, and > > > >I've had little time to validate the build. (My employer > > announced an > > > >acquisition on Wednesday, which added some extra hooplah > > to the week > > > >too...) > > > > > > > >In any case, running the Cactus tests tonight, I have a > > problem. On all of > > > >the Tomcat versions I've tried so far (4.1.18, 4.0.6, > > 3.3.1), I get a test > > > >failure in the Tiles tests. The relevant part of the > > output follows: > > > > > > > >----- cut here ----- > > > > [junit] Testcase: testMultiFactory took 2.544 sec > > > > [junit] Caused an ERROR > > > > [junit] > > > > > >junit.framework.Assert.assertNotSame(Ljava/lang/String;Ljava/lang/Ob > > > >ject;Ljava/lang/Object;)V > > > > [junit] at > > > >org.apache.struts.tiles.TestTilesPlugin.testMultiFactory(Test > > > >TilesPlugin.java:236) > > > > [junit] at > > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > > [junit] at > > > >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces > > > >sorImpl.java:39) > > > > [junit] at > > > >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet > > > >hodAccessorImpl.java:25) > > > > [junit] Testcase: testMultiFactory > > > >----- cut here ----- > > > > > > > >There was a flurry of messages on the Cactus tests on this > > list recently, > > > >but this does not appear to be related to the problems > > described therein. > > > > > > > >Obviously, I need to determine whether this is a bug that > > we need to fix > > > >prior to RC1, or if I somehow messed up my system. (I have > > been able to > > > >run the Cactus tests in the past.) Therefore, I'd > > appreciate it if someone > > > >else could take the tests for a spin, and let me know the results. > > > > > > > >Thanks! > > > > > > > >-- > > > >Martin Cooper > > > > > > > > > > > > > >--------------------------------------------------------------------- > > > >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] > > > > > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
