[qos-ch/logback-contrib] f56560: Specify release-sign-artifacts profile in release....

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-contrib Commit: f565605b29bec5888f7c9224bb4df17394d2c9c4 https://github.com/qos-ch/logback-contrib/commit/f565605b29bec5888f7c9224bb4... Author: Tony Trinh <tony19@gmail.com> Date: 2016-06-10 (Fri, 10 Jun 2016) Changed paths: M release.sh Log Message: ----------- Specify release-sign-artifacts profile in release.sh The artifacts are only signed when the `release-sign-artifacts` profile is activated, which is normally done by the maven-release-plugin for the release:perform task. That's not happening for some reason, so as a workaround, we're now explicitly setting the profile when using the release script. We're soon switching to Gradle, so no further effort will be put in to fix this in Maven configs. This patch also allows passing mvn arguments to release.sh, which is useful for setting -DdryRun=true. Commit: 4176e79bae17dcf5377b7e373414bc1161c0ea2f https://github.com/qos-ch/logback-contrib/commit/4176e79bae17dcf5377b7e37341... Author: Tony Trinh <tony19@gmail.com> Date: 2016-06-10 (Fri, 10 Jun 2016) Changed paths: M eclipse/pom.xml M jackson/pom.xml M janino-fragment/pom.xml M json/access/pom.xml M json/classic/pom.xml M json/core/pom.xml M json/pom.xml M mongodb/access/pom.xml M mongodb/classic/pom.xml M mongodb/core/pom.xml M mongodb/pom.xml M pom.xml M xmpp/pom.xml Log Message: ----------- [maven-release-plugin] prepare release v_0.1.5 Compare: https://github.com/qos-ch/logback-contrib/compare/39cd5a5f975e...4176e79bae1...
participants (1)
-
Tony Trinh