Appears to be what Nat was last thinking, evidence of hamcrest-1.3RC1 jars in SCM
Olis jmock commit of hamcrest 1.3.0CR2 libs
JavaSE-1.5, Type Erasure Issues, Source
JavaSE1.6, Eclipse Compiles Fine, Ant has 2 compile errors in 1.5 compliance mode
jmock 2.6.0-RC2 requires hamcrest 1.2, java.lang.NoClassDefFoundError: org/hamcrest/TypeSafeDiagnosingMatcher
Sonatype
Central, http://mvnrepository.com/artifact/org.jmock/jmock
Request
GPG
commands, mvn -Pjmock2 release:clean, or it may use the wrong release name from previous prepare, check pom.xml, mvn -Pjmock2 release:prepare, release, 2.6.0-RC2, TAG, 2.6.0-RC2-PKGOIBX, branch, package-2.6.0-RC2, Does not run tests, so doesn't check depenedencies!, So manually check them comparing the source branch to the package branch, Nexus UI, Close, Makes available for stage testing, ~/.m2/settings.xml, Following profile can be added to any build to check the new staged artefacts, <profiles> <profile> <id>CodehausStage</id> <repositories> <repository> <id>CodehausStage</id> <name>Codehaus Stage</name> <releases> <enabled>true</enabled> <updatePolicy>always</updatePolicy> <checksumPolicy>fail</checksumPolicy> </releases> <snapshots> <enabled>false</enabled> <updatePolicy>never</updatePolicy> <checksumPolicy>fail</checksumPolicy> </snapshots> <url>https://nexus.codehaus.org/content/repositories/staging</url> <layout>default</layout> </repository> </repositories> </profile> </profiles>, Test Stage, mvn -PCodehausStage versions:display-dependency-updates, hamcrest 1.1, pulled in by junit, Consider this article, consider exclude like junit-dep in jmock-junit4 pom.xml