Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).

Build: #584 was successful Changes by Florian Schmaus <flo@geekplace.eu>

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
4 minutes
Labels
None
Agent
Default Agent
Revision
daab6039a1af48199a709873020ba81096fb4b2d
Total tests
680
Successful since
#574 ()

Tests

Code commits

Author Commit Message Commit date
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> daab6039a1af48199a709873020ba81096fb4b2d Merge tag '4.3.3'
Smack 4.3.3
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> b054c4fe77435cc9cdbdd2722e9bb923815acdc7 m Smack 4.3.3
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 0de0873abb3b34618bb9b771800c505609a2113f m version.gradle: Add link to SMACK-858
Georg Lukas <georg@op-co.de> Georg Lukas <georg@op-co.de> e5bbd19ef11e4111d8927f44be5061e765975962 m StanzaDroppedListener for XEP-0198 resumption failures
If a stream resume fails, smack will re-send all queued stanzas after a
reconnect. However, it does not make sense to re-send them:

* IQs / IQ responses have probably timed out
* MUC messages and PMs will be rejected as you haven't rejoined yet
* regular messages should be amended with a <delay> element

This patch adds a StanzaDroppedListener interface to the
XMPPTCPConnection. If at least one StanzaDroppedListener is provided,
all queued messages will be drained into the StanzaDroppedListener(s).
Otherwise, the original behavior of attempting to transmit them will be
followed.

Discussion: https://discourse.igniterealtime.org/t/xep-0198-resume-failure-reconnect-resending-of-muc-messages/83510/3

Signed-off-by: Georg Lukas <georg@op-co.de>
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> c4289b2c1819bd7b62dca9ed7743410b19665296 m Add AbstractXMPPConnection.initState()
and init/reset the sychronization points there.

This method is called right at the beginning of connect() and at the
end of shutdown().

Jira issues

IssueDescriptionStatus
Unknown Issue TypeSMACK-855Could not obtain issue details from Jira
Unknown Issue TypeSMACK-856Could not obtain issue details from Jira
Unknown Issue TypeSMACK-858Could not obtain issue details from Jira
Unknown Issue TypeSMACK-859Could not obtain issue details from Jira
Unknown Issue TypeXEP-0198Could not obtain issue details from Jira