Sounds reasonable to disable this test for now.
On that note, I'm also starting to lean towards disabling modules/
timer tests for now too.
--jason
On Jul 28, 2006, at 6:04 AM, Prasad Kashyap wrote:
Your suspicion about the JDK version became stronger when the same
activation module built successfully on my Linux machine which has jdk
1.4.2_10. The windows machine on which it failed had jdk 1.5.0_06.
I think we should exclude this test for now. Then we should fix the
test to account for differences in jdk versions.
What say you ?
Cheers
Prasad.
On 7/27/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
FYI, this was the test that I had commented out before in that
module... that mysteriously started working.
Maybe it is related to the JDK version? Just a guess though.
--jason
On Jul 27, 2006, at 11:51 AM, Prasad Kashyap wrote:
> At revision 426188. Clean local repo
>
> Test in activation module fails. Anybody know what suddenly changed
> there ?
>
>
---------------------------------------------------------------------
-
> -----------
> Test set: org.apache.geronimo.activation.handlers.MailcapTest
>
---------------------------------------------------------------------
-
> ---------
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
0.06
> sec <<< FAILURE!
> testTextPlainHandler
> (org.apache.geronimo.activation.handlers.MailcapTest)
> Time elapsed: 0.03 sec <<< FAILURE!
> junit.framework.ComparisonFailure:
> expected:<...activation.handlers.TextPlain...> but
> was:<...mail.handlers.Text...>
> at junit.framework.Assert.assertEquals(Assert.java:81)
> at junit.framework.Assert.assertEquals(Assert.java:87)
> at
>
org.apache.geronimo.activation.handlers.MailcapTest.testTextPlainHand
l
> er(MailcapTest.java:34)
>
>
> Cheers
> Prasad
