Builds Spark (minus the Install4j distributables) after every change to the code.

Build result summary

Details

Completed
Duration
22 seconds
Labels
None
Agent
Default Agent
Revision
918c15adba9ffe457da1274f99024a91e9728378 918c15adba9ffe457da1274f99024a91e9728378
Total tests
5
Successful since
#190 ()

Tests

  • 0 New failures
  • 0 Existing failures
  • 0 Fixed

Code commits

Author Commit Message Commit date
wroot <wrooot@users.noreply.github.com> wroot <wrooot@users.noreply.github.com> 918c15adba9ffe457da1274f99024a91e9728378 918c15adba9ffe457da1274f99024a91e9728378 Merge pull request #538 from R87A/SPARK-2175
SPARK-2175: Fix offline message handling after a reconnect
R87A <ostretsov_av@hotmail.com> R87A <ostretsov_av@hotmail.com> 88845242ba2b9b4e43b62099b7842c9e91d79f3b 88845242ba2b9b4e43b62099b7842c9e91d79f3b Don't handle offline messages if the corresponding chat room has already been created.
This eliminates duplicate messages in the transcript window when the user reconnects while the chat room is open.
R87A <ostretsov_av@hotmail.com> R87A <ostretsov_av@hotmail.com> 015970e3d72aac395fd588a4f940182b0d52dd49 015970e3d72aac395fd588a4f940182b0d52dd49 Fix chat room existence check and chat room creation.
Existence check should take into account the actual type of the parameter passed to the method.
There it is important to distinguish JID (EntityJid type) and bare JID (EntityBareJid type) since both are used:
bare JIDs - within one-on-one chats;
full JIDs - within private chats of group chat members.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeSPARK-2175Could not obtain issue details from Jira