Build #1,171

Plan branch:
Generates the latest/greatest Maven-based artifacts for the Openfire project, every night.

Build: #1171 was successful Scheduled with changes by daryl herzmann <akrherz@iastate.edu>

Stages & jobs

  1. Build and Package

  2. Deploy

  3. copy nightlies to website

Build result summary

Details

Completed
Queue duration
4 minutes
Duration
3 minutes
Labels
None
Revision
88abdd47682c323a5d0fce561269600c8dfb8342
Total tests
436
Successful since
#1160 ()

Tests

Code commits

Author Commit Message Commit date
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> 88abdd47682c323a5d0fce561269600c8dfb8342 Merge pull request #1653 from guusdk/OF-1836_handle-stream-errors
OF-1836: Properly handle S2S stream errors
Guus der Kinderen Guus der Kinderen 8eebbd1880a4b572f4f99bd983962d92999d61e4 m OF-1836: Properly handle S2S stream errors
Up until now, receiving stream errors were processed in the chatch-all "we don't know what to do with this" code. Instead, Openfire should support proper error parsing.

Functionally, this won't introduce much of a change, as the behavior for processing unprocessable data is to close the connection, which is similar to what happens after processing a stream error.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-1836Could not obtain issue details from Jira