On 06/07/2016 13:47, Julian Reschke wrote: >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-release-plugin:2.1 >> :prepare (default-cli) on project jackrabbit: Execution default-cli >> of goal org. >> apache.maven.plugins:maven-release-plugin:2.1:prepare failed: An API >> incompatibi >> lity was encountered while executing >> org.apache.maven.plugins:maven-release-plug >> in:2.1:prepare: java.lang.NoSuchMethodError: >> org.apache.maven.settings.Settings. >> getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo; > > Any ideas what's wrong? Not really but...
did you follow http://jackrabbit.apache.org/jcr/creating-releases.html#Prerequisites_for_release_managers http://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_A:_Create_and_add_your_key_to_the_Jackrabbit_KEYS_file http://jackrabbit.apache.org/jcr/creating-releases.html#Appendix_B:_Maven_settings what is your maven version? My side is: Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 16:22:22+0100) Maven home: /usr/local/maven Java version: 1.7.0_60, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac" In case on OSX is easy to have more than one maven versions switching between those using env variables. Or even better, spinning up a dedicated VM with pinned packages. If it turnsout to be the maven version we have two options 1) change the plugin versions for supporting new mavens. Hopefully it won't break 2) document the maven requirements in the release doc. HTH Davide
