This is an automated email from the ASF dual-hosted git repository.

rombert pushed a change to annotated tag org.apache.sling.discovery.oak-1.2.0
in repository 
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-discovery-oak.git.


      at 8db5c62  (tag)
 tagging d808ccdc719916bb0a8ba0a882ebdbfc5fcef2d0 (commit)
      by Stefan Egli
      on Wed Nov 25 13:46:56 2015 +0000

- Log -----------------------------------------------------------------
org.apache.sling.discovery.oak-1.2.0
-----------------------------------------------------------------------

This annotated tag includes the following new commits:

     new d1c3dce  SLING-4603 : added discovery.oak to the project - this is 
based on discovery.base, which handles topology connectors and contains a few 
other base classes that were factored out of discovery.impl for exactly this 
reuse
     new f889c65  SLING-4603 : some minor wording change
     new c03ca86  SLING-4603 : more aggressively clearing the idMap-cache to 
avoid stale entries on slingId change - plus added getSyncHistory to 
BaseSyncTokenConsistencyService to allow adding it to the webconsole for debug 
- plus some cleanup in webconsole wrt discoveryLite info
     new f030cb5  SLING-4603 : introducing configuration for syncToken 
enabling/disabling - plus using the ConsistencyServiceChain - plus more details 
when PROPERTIES_CHANGED
     new f32fadf  SLING-5173 : re-added complete consistency-history after 
introducing splitting them and using the ConsistencyServiceChain. Probably 
should be refactored into something slightly nicer though
     new e993509  SLING-5188 : similar to moving discovery.impl's topology 
webconsole, do the same for discovery.oak
     new e2707dd  SLING-5094 / SLING-5173 / SLING-4603 related : ensure that 
before invoking the ConsistencyService.sync no async events are still in the 
queue. This is achieved by enqueueing an async event too that once it gets 
triggered ensures that no async events are left. This mechanism ensures that 
before the syncToken is written, all TopologyEventListeners have received a 
TOPOLOGY_CHANGING - and only that guarantees that the syncToken mechanism 
carries a high guarantee.
     new 38813a3  SLING-5191 / SLING-4603 : rename ConsistencyService to 
ClusterSyncService - plus making timeout/interval values for the same 
configurable in discovery.oak
     new f845fb8  SLING-4603 : method renamed : handlePotentialTopologyChange, 
which is slightly confusing anyway, renamed to checkForTopologyChange
     new bf3ac64  SLING-4603 : switch to discovery.base/.commons 1.0.0
     new d22f2a2  [maven-release-plugin] prepare release 
org.apache.sling.discovery.oak-1.0.0
     new cf00b6e  [maven-release-plugin] prepare for next development iteration
     new 76cc1ee  update discovery dependencies to next snapshot versions until 
release versions available in maven central
     new 680771e  SLING-5214: include millis in testing log formats
     new ed30aaa  SLING-5215 : fixed getTopology to return the correct, 
previous oldView when the view is undefined, ie not current. This is achieved 
by making sure OakDiscoveryService sets the oldView whenever the view changes
     new 9ef7c5d  SLING-5216 / SLING-5195 : more test cases added
     new 122527a  @no-jira : adjusted discovery.base and .commons dependency to 
1.0.2
     new 524b1a9  [maven-release-plugin] prepare release 
org.apache.sling.discovery.oak-1.0.2
     new 155b4a1  [maven-release-plugin] prepare for next development iteration
     new ba02791  @no-jira : adjusted discovery.base and .commons dependency to 
1.0.3-SNAPSHOT
     new 917cac3  SLING-5256 : change in localClusterSyncTokenId should always 
trigger a TOPOLOGY_CHANGED - ensured by adjusting 
ViewStateManager.onlyDiffersInProperties and 
DefaultTopologyView.compareTopology accordingly including new tests for both - 
plus added OakDiscoveryServiceTest.testDescriptorSeqNumChange to verify that 
discovery.oak now properly detects otherwise-equal topologies when their 
sequence_number==localClusterSyncTokenId differs (unlikely to happen under 
normal load sit [...]
     new 8cc6d0f  SLING-5278 : adding a 2sec safety sleep to avoid failing test 
on jenkins - plus more logging in case it reoccurs
     new 9c09dd4  SLING-5284 : use dedicated PeriodicBackgroundJob-thread 
instead of scheduler
     new 1495890  SLING-5286 : re-activate fast topology change propagation
     new 65e191e  SLING-5284 : new PeriodicBackgroundJob requires upping of 
version to 1.1.0
     new e660d0b  @no-jira using discovery.commons 1.0.4 and discovery.base 
1.1.0
     new db51f6d  [maven-release-plugin] prepare release 
org.apache.sling.discovery.oak-1.1.0
     new 5c615a6  [maven-release-plugin] prepare for next development iteration
     new bd43c5c  @no-jira using discovery.commons 1.0.5-SNAPSHOT and 
discovery.base 1.1.1-SNAPSHOT
     new 7a100d5  no-jira : fixing a log.info message that did not print out 
all parameters
     new e9ab194  SLING-5328 : add missing documentation
     new 5808792  SLING-5326 : adding time-difference health-check 
'ClocksInSyncHealthCheck'
     new 4615883  SLING-5326 : removing unnecessary import
     new c9c8f13  SLING-5326 : adjusted health-check name to be more human 
readable
     new 2b08fde  SLING-5326 : renamed ClocksInSyncHC to SynchronizedClocksHC - 
like that better..
     new aae4a2f  SLING-5326 : corrected peer slingId for outgoing connectors 
that is shown in health-check messages
     new a6311ab  no-jira : switching to discovery.commons 1.0.6 and 
discovery.base 1.1.2
     new 8215919  [maven-release-plugin] prepare release 
org.apache.sling.discovery.oak-1.2.0
     new d808ccd  [maven-release-plugin] copy for tag 
org.apache.sling.discovery.oak-1.2.0

The 39 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


-- 
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].

Reply via email to