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: #658 was successful Changes by Florian Schmaus

Build result summary

Details

Completed
Duration
4 minutes
Labels
None
Agent
Default Agent
Revision
f0300dc906089564d57135f791c4e4900cfe224d f0300dc906089564d57135f791c4e4900cfe224d
Total tests
739
Successful since
#651 ()

Tests

Code commits

Author Commit Message Commit date
Florian Schmaus Florian Schmaus f0300dc906089564d57135f791c4e4900cfe224d f0300dc906089564d57135f791c4e4900cfe224d Remove deprecated "PacketReplyTimeout" methods in SmackConfiguration
Florian Schmaus Florian Schmaus 35cf094386ea0bcfd617c57e8f0ad4fec9d08b87 35cf094386ea0bcfd617c57e8f0ad4fec9d08b87 sasl-javax: Do not set system properties in SASLGSSAPIMechanism
Smack did this for a long time, since eb56f8a55 ("GSSAPI work by Jay
Kline (SMACK-218)."). Not always in a static block though. But
irregardless this is bad practice as it causes side-effects and may
overrides settings.

For example, one users reports:

java.lang.SecurityException: java.io.IOException: gss.conf (No such file or directory)
    at sun.security.provider.ConfigFile$Spi.<init>(ConfigFile.java:137)
    at sun.security.provider.ConfigFile.<init>(ConfigFile.java:102)
    at sun.reflect.GeneratedConstructorAccessor119.newInstance(Unknown Source)

Jira issues

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