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

Build: #1824 was successful Scheduled with changes by Guus der Kinderen

Stages & jobs

  1. Build and Package

  2. Deploy

  3. copy nightlies to website

Build result summary


Queue duration
21 minutes
4 minutes
Total tests
First to pass since
#1823 (Scheduled – )


Code commits

Author Commit Message Commit date
Guus der Kinderen Guus der Kinderen c074219f79c344db08230a778fcf7b62bd586a43 LGTM: ignore insecure-cookie when unsetting the cookie.
As long as we're exposing the admin console on a non-HTTPS endpoint (our port 9090), we will have a need to set cookies on an unsecure endpoint. This raises (rightfully) the LGTM 'insecure-cookie' alert, as Insecure cookies may be sent in cleartext, which makes them vulnerable to interception.

However, LGTM also raises this alert when we remove the cookie (which we do by setting an immediately-expired cookie with no data). The alert can be suppressed for that one.
Guus der Kinderen Guus der Kinderen 5f30df15cf6ac47b87aba7bba6c960d3ef143836 OF-2411: Prevent deadlock in XmlProperties
OF-2377 introduced an updated implementation of the thread-safety module of XmlProperties (the old one wasn't fully thread-safe).

This new implementation causes a very specific problem at startup: When the initial attempt to migrate an XmlProperty is undertaken, TaskEngine is instantiated, which in turn tries to read/write properties (while under lock). This causes a deadlock.

To work around this issue, this commit replaces the usage of TaskEngine with a throw-away thread (that does not use any properties).
Guus der Kinderen Guus der Kinderen 0eded0ebf84ec395516011fc35d35509905f6de5 OF-2412: Handle secure XML property migration synchronously
When Openfire starts, all XML properties are migrated to the database. This currently is performed in an asynchronous process. This seems to open the door for a race condition. As the amount of properties involved is unlikely to be very high, switching to a synchronous process seems to offer more predictability.

Jira issues

Unknown Issue TypeOF-2377Could not obtain issue details from Jira
Unknown Issue TypeOF-2411Could not obtain issue details from Jira
Unknown Issue TypeOF-2412Could not obtain issue details from Jira