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

Stages & jobs

  1. Default Stage

  2. Deploy

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
8 minutes
Labels
None
Revision
b9c12d44c3d8e5697d892c2938fe4e031c90a137
Total tests
582
Successful since
#136 ()

Tests

Code commits

Author Commit Message Commit date
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> b9c12d44c3d8e5697d892c2938fe4e031c90a137 Use InetSocketAddress in log message in XMPPTCPConnection
The inetAddressAndPort String is redundant since
a2743549b8a4126e17f61adcb369f72d86ef58e1, because we now construct the
InetSocketAddress earlier and can hence use it in the log statement.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> a2743549b8a4126e17f61adcb369f72d86ef58e1 Make TCP socket connection attempt interruptable
by introducing SmackFuture.SocketFuture.

Fixes SMACK-847.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> d1c73eba8d4cdac363204a95da2d93905c0da6d0 Fix MamManager javadoc
of methods which have been renamed.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 48e31271720d65824e0ffff3f39abe9a2ef1980f Always wait for stream features after authentication
The purpose of the "maybeCompressFeaturesReceived" synchronization
point is to wait for the stream features after authentication. This is
not really reflected by its name and furthermore its
checkIfSuccessOrWait() method was only invoked if compression was
enabled, but we always want to wait for the stream features after
authentication. Hence move the call before the isCompressionEnabled()
check and one layer up in the call stack.

Fixes SMACK-846.

Configuration changes

Some of the jobs or stages referenced by this result no longer exist.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeSMACK-846Could not obtain issue details from Jira
Unknown Issue TypeSMACK-847Could not obtain issue details from Jira