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

Build: #983 was successful Manual run by wroot

Stages & jobs

  1. Build and Package

  2. Deploy

  3. copy nightlies to website

Build result summary

Details

Completed
Queue duration
1 second
Duration
2 minutes
Labels
None
Revision
4b1b155dd4a997c00f4e670081daf8aafb9ca501
Total tests
401
Successful since
#967 ()

Tests

Code commits

Author Commit Message Commit date
Greg Thomas <greg.d.thomas@gmail.com> Greg Thomas <greg.d.thomas@gmail.com> 4b1b155dd4a997c00f4e670081daf8aafb9ca501 OF-1895: Unload properties that belong to a plugin
Guus der Kinderen Guus der Kinderen c0e81a77cf4e5d7e489bfd78fb4cc7be56129494 There's no need to add a duplicate character to split on.
Guus der Kinderen Guus der Kinderen 22c7a95e873d23db4f923fa1a9f618851e27b83c OF-1106: Allow for multiple namefields.
This commit allows one to configure more than one LDAP attribute to be used for the Name field, where the first non-empty attribute is used (note that this is different from combining multiple attribute values, which was already supported).

The new functionality is used by defining the mapping value as follows:

    (|({givenName})({displayName})({cn}))

In the example above, the attribute used will be the first non-empty attribute value from the list:

- givenName
- displayName
- cn

Obviously, other attribute names can be used. It's also possible to use fewer or more fields.

This particular format (which mimics LDAP filter syntax) was used to avoid clashes with mappings where it is desirable to join multiple fields (which is also supported in Openfire), for example:

    {familyName}, {givenName}
Guus der Kinderen Guus der Kinderen a64480ed827019cfe2c76d02ae39945ec73d63b0 OF-1106: Apply new 'priority' filter to VCard mapping.
Guus der Kinderen Guus der Kinderen 955061fc09a1e6b6fc34ac794037be0486927621 OF-1949: Should combine LDAP values in User's "name" field.

Jira issues

IssueDescriptionStatus
1 more issue…
Unknown Issue TypeOF-1106Could not obtain issue details from Jira
Unknown Issue TypeOF-1895Could not obtain issue details from Jira
Unknown Issue TypeOF-1938Could not obtain issue details from Jira
Unknown Issue TypeOF-1944Could not obtain issue details from Jira
Unknown Issue TypeOF-1947Could not obtain issue details from Jira