>>>>> Tatu Saloranta <[email protected]>: > I also think that at this point I will need to go back and really > learn how to use Sonatype's Nexus plug-in:
> https://blog.sonatype.com/maven-deploy-to-nexus > as it should be more reliable mechanism for making releases (and > possible more convenient). FWIW These projects contain config for maven-release-plugin and nexus-staging-maven-plugin that has let me successfully deploy to OSSRH with "mvn release:prepare" and "mvn release:perform". I arrived at them with a lot of broken deploys and increment of minor version numbers: https://github.com/steinarb/authservice/blob/master/pom.xml#L567 https://github.com/steinarb/sonar-collector/blob/master/pom.xml#L365 When a release work I just do (swap the version numbers with the actual versions used. developmentVersion is the next snapshot version after the release): mvn release:prepare -DautoVersionSubmodules=true -DdevelopmentVersion=1.6.0-SNAPSHOT -DreleaseVersion=1.5.3 mvn release:perform and an unspecified time after "release:perform" completes (but less than 24h) the artifacts are available from maven central. (however when/if they break I usually have no idea what went wrong, and just have to try again. The last couple of times a relase have failed I have rolled back the release, scrubbed the commits made by maven-release-plugin, force pushed the change to the remote (github) and deleted the release tag both locally and on the remote, and then run "mvn release:prepare" and "mvn release:perform" again and this time it has gone through) -- You received this message because you are subscribed to the Google Groups "jackson-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-user/86eezq6x8z.fsf%40dod.no.
