1. 14 Nov, 2017 8 commits
    • akrherz's avatar
      ensure all files end with line feed · 66b3cb97
      akrherz authored
      command form this time was
      git ls-files  '*.jsp' | while read f; do tail -n1 $f | read -r _ || echo >> $f; done
      66b3cb97
    • akrherz's avatar
      replace tabs with spaces, when tabs start the line · 42f2cd51
      akrherz authored
      the command line form was
      find . -name '*.jsp' ! -type d -exec bash -c 'expand -i -t 4 "$0" > /tmp/e && mv /tmp/e "$0"' {} \;
      42f2cd51
    • akrherz's avatar
      remove CRLF from *.{html,css,sql,xml,js,properties,jspf,java,jsp} · 0bc646f9
      akrherz authored
      all done via the magic of dos2unix
      0bc646f9
    • GregDThomas's avatar
    • Dave Cridland's avatar
      OF-1309 Route based on DomainPairs (#916) · 5815efc8
      Dave Cridland authored
      * OF-1309 Route based on DomainPairs
      
      * Fixes found during test
      
      * Fixes found during test II
      
      * Fixes in plugins (Kraken)
      
      * Update minServerVersion/version for Kraken
      5815efc8
    • Guus der Kinderen's avatar
      OF-210: Additional work. (#923) · fa6beb91
      Guus der Kinderen authored
      * Support for Roster Versioning (without send the modifications via roster pushes)
      
      * Roster versioning comparison clearing
      
      * Implementation Note: This empty IQ-result is different from an empty <query/> element, thus disambiguating this usage from an empty roster.
      
      * Avoid cache miss while updating roster
      
      When the roster is updated via group renaming, group user adding or removing, the roster pushes only happen if there is a cache hit. If there is a cache miss (what can happen if the cache is full or if the admin cleaned up the cache) the user is not properly notified about the roster update. Thus only update rosters in memory can lead to this undesired behavior.
      
      This commit avoids the use of the cache directly (where there can be a cache miss or a cache hit). It is using the method getRoster(username) that instantiante a new Roster in the case of a cache miss.
      
      * Clarify the code
      
      * OF-210: Base roster version on its hashCode.
      
      This commit removes all fields from the Roster class that do not relate to its state
      (replacing them with method variables - which seems harmless, as they're all final
      singletons). This allows for an easy override of Object#hashCode() and equals().
      These, in turn, are used to calculate the roster version from.
      
      * Simplified loop
      
      * Prevent potential NPEs.
      
      * Log exceptions for exceptions that cannot happen.
      
      If they cannot happen, we should scream murder if they do...
      
      * OF-210: Roster versioning enabled by default.
      fa6beb91
    • akrherz's avatar
      OF-1286 sync Openfire's truststore with Mozzila's shipped CAs · 1494c6b2
      akrherz authored
      Simply repeated dwd's commit 73b59106 on Ubuntu Trusty (20170717~14.04.1)
      1494c6b2
    • Dave Cridland's avatar
      OF-1427 Respond to PEP node disco#info · ca435745
      Dave Cridland authored
      ca435745
  2. 13 Nov, 2017 8 commits
  3. 06 Nov, 2017 1 commit
  4. 03 Nov, 2017 8 commits
  5. 02 Nov, 2017 2 commits
  6. 31 Oct, 2017 3 commits
  7. 30 Oct, 2017 1 commit
  8. 27 Oct, 2017 9 commits