Integration to validate new upstream
The most common set up for Continuous Integration systems is the HEAD to HEAD, for mavenized projects this generally means the trunk of many artifacts installed as SNAPSHOT's. Using the version range as specified here
<dependency>
<groupId>net.stickycode.composite</groupId>
<artifactId>sticky-composite-logging-deploy</artifactId>
<version>[1,2)</version>
</dependency>
I can easily commit a change to the head of the sticky-composite-logging-deploy project and have it affect CI built projects but not developers as I have not released it. No forcing a complete rebuild of all projects we can see whether or not any projects no longer compile and/or pass their tests. Obviously changing the logger has less risk of breaking things that other libraries but the principle holds true.
Say a new version of logback comes out 0.9.25, i would changecommit it and force a full CI rebuild - if there were no dependency base hooks of course - and watch for any alerts.
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>[0.9.25]</version>
</dependency>
