[
https://issues.apache.org/jira/browse/LABS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl updated LABS-337:
------------------------------
Attachment: LABS-337.1.patch
I don't like the write(null) hack, why not introduce a new method and call it
reset()? The comments also didn't match the method's behavior (write doesn't
throw anything anymore).
The patch adds the reset method, replaces all write(null) with reset and
changes the comment for the write method.
> Some JUnit tests fail after clean checkout
> ------------------------------------------
>
> Key: LABS-337
> URL: https://issues.apache.org/jira/browse/LABS-337
> Project: Labs
> Issue Type: Bug
> Components: Vysper
> Affects Versions: Current
> Environment: java version "1.6.0_0"
> OpenJDK Runtime Environment (IcedTea6 1.5pre-r0507febca60d)
> (ArchLinux-1.5-0.1-x86_64)
> OpenJDK 64-Bit Server VM (build 14.0-b10, mixed mode)
> Reporter: Michael Jakl
> Priority: Minor
> Attachments: LABS-337.1.patch
>
>
> After a fresh checkout four JUnit tests fail when running "ant
> run-unit-tests":
> [junit] Test
> org.apache.vysper.xmpp.modules.core.im.handler.PresenceHandlerBaseTestCase
> FAILED
> [junit] Test
> org.apache.vysper.xmpp.modules.core.im.handler.PresenceSubRequestOutHandlerTestCase
> FAILED
> [junit] Test org.apache.vysper.xmpp.protocol.ProtocolStateTestCase FAILED
> [junit] Test
> org.apache.vysper.xmpp.protocol.ProtocolWorkerProcessTestCase FAILED
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
