Running requireUpperBoundDeps.
<!-- Should only need to override these if using timestamped snapshots: -->
<jenkins-core.version>${jenkins.version}</jenkins-core.version>
<jenkins-war.version>${jenkins.version}</jenkins-war.version>
- <jenkins-test-harness.version>2.22</jenkins-test-harness.version>
+ <jenkins-test-harness.version>2.23-20170612.232140-1</jenkins-test-harness.version> <!-- TODO https://github.com/jenkinsci/jenkins-test-harness/pull/62 -->
<hpi-plugin.version>2.0</hpi-plugin.version>
<stapler-plugin.version>1.17</stapler-plugin.version>
<java.level>7</java.level>
</plugin>
<plugin>
<artifactId>maven-enforcer-plugin</artifactId>
- <version>1.4.1</version>
+ <version>1.4.2-20170612.231258-1</version> <!-- TODO https://github.com/apache/maven-enforcer/pull/23 -->
</plugin>
<plugin>
<artifactId>maven-install-plugin</artifactId>
<message>No Snapshots Allowed For Release Versions</message>
<onlyWhenRelease>true</onlyWhenRelease>
</requireReleaseDeps>
+ <requireUpperBoundDeps>
+ <excludes>
+ <exclude>com.google.guava:guava</exclude> <!-- TODO Stapler requests 14 while Jenkins requests 11; should backdate the Stapler version -->
+ <exclude>commons-logging:commons-logging</exclude> <!-- TODO jenkins-test-harness-htmlunit requests 1.2, newer than 1.1.x in core -->
+ <exclude>com.google.code.findbugs:jsr305</exclude> <!-- Stapler requests 2.x while core requests 1.x; anyway not used at runtime -->
+ </excludes>
+ </requireUpperBoundDeps>
</rules>
</configuration>
</execution>
