Codearte/gradle-nexus-staging-plugin
### [`v0.30.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0300---2021-02-26)
- Replace from old unsupported HTTP Builder to OkHttp 4 - [#188](https://togithub.com/Codearte/gradle-nexus-staging-plugin/pull/188) - PR by [anuraaga](https://togithub.com/anuraaga)
- **Switch project development to maintenance mode** - see below
- Switch build to Gradle 6.8.3
- Remove deprecated since 0.8.0 `promoteRepository` and `closeAndPromoteRepository` tasks
**Backward compatibility note**. Due to the internal HTTP client library change, the plugin might start behaving slightly different in certain situations.
**PROJECT DEVELOPMENT SWITCHED TO THE MAINTENANCE MODE**. To make releasing to Maven Central even easier, I and Marc Phillip (the author of nexus-publish-plugin) combined forces to create a next generation, unified 2-in-1 plugin - [gradle-nexus-publish-plugin](https://togithub.com/gradle-nexus/publish-plugin/). It is a recommended solution, as our development effort will be put in that new plugin. See my [blog post](https://blog.solidsoft.pl/2021/02/26/unified-gradle-projects-releasing-to-maven-central-in-2021-migration-guide/) and the official [migration guide](https://togithub.com/gradle-nexus/publish-plugin/wiki/Migration-from-gradle_nexus_staging-plugin---nexus_publish-plugin-duo).
Thank you for over 5 years of releasing with my plugin!
### [`v0.22.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0220---2020-08-17)
- Change default retrying time to 5 minutes - a value recommended by Sonatype (suggestion by [Mikhail Yakushin](https://togithub.com/driver733))
- Switch build to Gradle 6.6
- Bump some dependencies
- Check basic compatibility with Gradle up to 6.6
- CI server sanity check for Java 14 compatibility
### [`v0.21.2`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0212---2019-12-23)
- Workaround incompatibility with Gradle 6.0 caused by a Gradle bug ([#11466](https://togithub.com/gradle/gradle/issues/11466)) - [#141](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/141) - PR by [Lars Grefer](https://togithub.com/larsgrefer)
### [`v0.21.1`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0211---2019-09-05)
- Fix incompatibility of unsupported releasing with legacy upload task with Gradle 5
- Precise minimal supported Gradle version to 4.9
- Improve error message when applying on root project - [#122](https://togithub.com/Codearte/gradle-nexus-staging-plugin/pull/122/) - PR by [Patrik Greco](https://togithub.com/sikevux)
### [`v0.21.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0210---2019-05-19)
- Restore ability to override ban on applying plugin on subprojects - [#116](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/116)
- Workaround Gradle [limitations](https://togithub.com/gradle/gradle/issues/9386) with precompiled script plugin accessors in Kotlin - [#117](https://togithub.com/Codearte/gradle-nexus-staging-plugin/pull/117) - contribution by [@Vampire](https://togithub.com/Vampire)
- Decrease retrying messages verbosity - [#82](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/82)
- Execute e2e tests on Travis also for Java 11 - [#74](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/74)
- Automatically upgrade dependencies with Dependabot - [#79](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/79)
- CI server sanity check for Java 12 compatibility
- CI server sanity check for OpenJ9 11 compatibility
### [`v0.20.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0200---2019-01-05)
- Reuse explicitly created staging repository ID if provided by external plugin - [#77](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/77)
- Fix releasing from Travis - workaround Gradle limitation with Nexus stating repositories with external plugin - [nexus-publish-plugin](https://togithub.com/marcphilipp/nexus-publish-plugin/) [#76](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/76)
- Raise minimal required Gradle version to 4.8 due to internals modernisation
- Runtime compatibility with Gradle 5.0 and 5.1
**Deprecation note**. Support for implicitly created staging repositories is deprecated. It has been always problematic, slow and error prone
to find a proper staging repository and the recent [changes](https://togithub.com/travis-ci/travis-ci/issues/9555) in Travis just emphasised that.
Thanks to the new [nexus-publish-plugin](https://togithub.com/marcphilipp/nexus-publish-plugin/) plugin by
[Marc Philipp](https://togithub.com/marcphilipp) which seamlessly integrates with the `gradle-nexus-staging` plugin it should straightforward to use
explicitly created staging repositories in Nexus. At least in a case of using `maven-publish` (`publish...` tasks). If you still use the old `maven`
plugin (the `uploadArchives` task) please refer to [that issue](https://togithub.com/marcphilipp/nexus-publish-plugin/issues/8).
The original code has not been removed and *should* still work for the time being (if you don't use Travis), but it is no longer officially
supported (e.g. the E2E tests has been switched to the new approach).
### [`v0.12.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0120---2018-09-29)
- Java 11 compatibility (basic path verified by e2e tests) - [#73](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/73)
- Fix crash on non-upload task named 'uploadArchives' - [#67](https://togithub.com/szpak/CDeliveryBoy/issues/#67)
- Drop support for Java 7
- Drop Gradle 2.x support (not supported by used plugins)
- Upgrade project dependencies
- Upgrade Gradle to 4.10.2
### [`v0.11.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0110---2017-08-18)
- Fail when applied on non-root project - [#47](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/47)
- Less confusing log output without "info" logging enabled - [#60](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/60)
- Upgrade project dependencies
- Upgrade Gradle to 4.1 (compatibility with Gradle 2.0+ should be still maintained)
### [`v0.10.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0100---2017-08-18)
- Configurable repository description in close/release operation - [#63](https://togithub.com/Codearte/gradle-nexus-staging-plugin/pull/63) - contribution by [akomakom](https://togithub.com/akomakom)
### [`v0.9.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#090---2017-06-05)
This release provides no new features or bugfixes. It is focused on acceptance E2E testing and Continuous Delivery
with [CDeliveryBoy](https://travis-ci.org/szpak/CDeliveryBoy).
- Acceptance tests at Gradle level run before release against real Nexus - [#40](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/40)
- Automatic `CHANGELOG.md` synchronization with GitHub releases - [#52](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/52)
- Switch releasing to Continuous Delivery with CDeliveryBoy - [#54](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/54)
### [`v0.8.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#080---2017-04-08)
- Auto drop repository after release - [#37](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/37)
- Rename "promote" operation to "release" - [#50](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/50)
- Upgrade project dependencies to 2017 - [#43](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/43)
- Separate functional tests from unit tests - [#48](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/48)
- Make functional tests work also on Windows - [#39](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/39)
**Deprecation note**. The ~~promoteRepository~~ and ~~closeAndPromoteRepository~~ tasks are marked as deprecated and will be removed
in one of the future versions. `releaseRepository` and `closeAndReleaseRepository` can be used as drop-in replacements.
### [`v0.7.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#070---2017-03-27)
- Verify that repository has been really closed - [#21](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/21)
- Re-enable sharing stagingRepositoryId between close and promote - [#46](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/46)
- Basic functional tests with different Gradle versions - [#41](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/41)
- Suggest longer timeout if failed on time related operations even without `--info` enabled - [#34](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/34)
- Longer default retry period - [#12](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/12)
### [`v0.6.1`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#061---2017-03-20)
- Reusing `stagingRepositoryId` from close task bypasses retry mechanism and fails - [#44](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/44) - reusing `stagingRepositoryId` is temporary disabled
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box.
This PR contains the following updates:
0.5.3->0.30.0Release Notes
Codearte/gradle-nexus-staging-plugin
### [`v0.30.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0300---2021-02-26) - Replace from old unsupported HTTP Builder to OkHttp 4 - [#188](https://togithub.com/Codearte/gradle-nexus-staging-plugin/pull/188) - PR by [anuraaga](https://togithub.com/anuraaga) - **Switch project development to maintenance mode** - see below - Switch build to Gradle 6.8.3 - Remove deprecated since 0.8.0 `promoteRepository` and `closeAndPromoteRepository` tasks **Backward compatibility note**. Due to the internal HTTP client library change, the plugin might start behaving slightly different in certain situations. **PROJECT DEVELOPMENT SWITCHED TO THE MAINTENANCE MODE**. To make releasing to Maven Central even easier, I and Marc Phillip (the author of nexus-publish-plugin) combined forces to create a next generation, unified 2-in-1 plugin - [gradle-nexus-publish-plugin](https://togithub.com/gradle-nexus/publish-plugin/). It is a recommended solution, as our development effort will be put in that new plugin. See my [blog post](https://blog.solidsoft.pl/2021/02/26/unified-gradle-projects-releasing-to-maven-central-in-2021-migration-guide/) and the official [migration guide](https://togithub.com/gradle-nexus/publish-plugin/wiki/Migration-from-gradle_nexus_staging-plugin---nexus_publish-plugin-duo). Thank you for over 5 years of releasing with my plugin! ### [`v0.22.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0220---2020-08-17) - Change default retrying time to 5 minutes - a value recommended by Sonatype (suggestion by [Mikhail Yakushin](https://togithub.com/driver733)) - Switch build to Gradle 6.6 - Bump some dependencies - Check basic compatibility with Gradle up to 6.6 - CI server sanity check for Java 14 compatibility ### [`v0.21.2`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0212---2019-12-23) - Workaround incompatibility with Gradle 6.0 caused by a Gradle bug ([#11466](https://togithub.com/gradle/gradle/issues/11466)) - [#141](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/141) - PR by [Lars Grefer](https://togithub.com/larsgrefer) ### [`v0.21.1`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0211---2019-09-05) - Fix incompatibility of unsupported releasing with legacy upload task with Gradle 5 - Precise minimal supported Gradle version to 4.9 - Improve error message when applying on root project - [#122](https://togithub.com/Codearte/gradle-nexus-staging-plugin/pull/122/) - PR by [Patrik Greco](https://togithub.com/sikevux) ### [`v0.21.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0210---2019-05-19) - Restore ability to override ban on applying plugin on subprojects - [#116](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/116) - Workaround Gradle [limitations](https://togithub.com/gradle/gradle/issues/9386) with precompiled script plugin accessors in Kotlin - [#117](https://togithub.com/Codearte/gradle-nexus-staging-plugin/pull/117) - contribution by [@Vampire](https://togithub.com/Vampire) - Decrease retrying messages verbosity - [#82](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/82) - Execute e2e tests on Travis also for Java 11 - [#74](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/74) - Automatically upgrade dependencies with Dependabot - [#79](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/79) - CI server sanity check for Java 12 compatibility - CI server sanity check for OpenJ9 11 compatibility ### [`v0.20.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0200---2019-01-05) - Reuse explicitly created staging repository ID if provided by external plugin - [#77](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/77) - Fix releasing from Travis - workaround Gradle limitation with Nexus stating repositories with external plugin - [nexus-publish-plugin](https://togithub.com/marcphilipp/nexus-publish-plugin/) [#76](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/76) - Raise minimal required Gradle version to 4.8 due to internals modernisation - Runtime compatibility with Gradle 5.0 and 5.1 **Deprecation note**. Support for implicitly created staging repositories is deprecated. It has been always problematic, slow and error prone to find a proper staging repository and the recent [changes](https://togithub.com/travis-ci/travis-ci/issues/9555) in Travis just emphasised that. Thanks to the new [nexus-publish-plugin](https://togithub.com/marcphilipp/nexus-publish-plugin/) plugin by [Marc Philipp](https://togithub.com/marcphilipp) which seamlessly integrates with the `gradle-nexus-staging` plugin it should straightforward to use explicitly created staging repositories in Nexus. At least in a case of using `maven-publish` (`publish...` tasks). If you still use the old `maven` plugin (the `uploadArchives` task) please refer to [that issue](https://togithub.com/marcphilipp/nexus-publish-plugin/issues/8). The original code has not been removed and *should* still work for the time being (if you don't use Travis), but it is no longer officially supported (e.g. the E2E tests has been switched to the new approach). ### [`v0.12.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0120---2018-09-29) - Java 11 compatibility (basic path verified by e2e tests) - [#73](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/73) - Fix crash on non-upload task named 'uploadArchives' - [#67](https://togithub.com/szpak/CDeliveryBoy/issues/#67) - Drop support for Java 7 - Drop Gradle 2.x support (not supported by used plugins) - Upgrade project dependencies - Upgrade Gradle to 4.10.2 ### [`v0.11.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0110---2017-08-18) - Fail when applied on non-root project - [#47](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/47) - Less confusing log output without "info" logging enabled - [#60](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/60) - Upgrade project dependencies - Upgrade Gradle to 4.1 (compatibility with Gradle 2.0+ should be still maintained) ### [`v0.10.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#0100---2017-08-18) - Configurable repository description in close/release operation - [#63](https://togithub.com/Codearte/gradle-nexus-staging-plugin/pull/63) - contribution by [akomakom](https://togithub.com/akomakom) ### [`v0.9.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#090---2017-06-05) This release provides no new features or bugfixes. It is focused on acceptance E2E testing and Continuous Delivery with [CDeliveryBoy](https://travis-ci.org/szpak/CDeliveryBoy). - Acceptance tests at Gradle level run before release against real Nexus - [#40](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/40) - Automatic `CHANGELOG.md` synchronization with GitHub releases - [#52](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/52) - Switch releasing to Continuous Delivery with CDeliveryBoy - [#54](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/54) ### [`v0.8.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#080---2017-04-08) - Auto drop repository after release - [#37](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/37) - Rename "promote" operation to "release" - [#50](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/50) - Upgrade project dependencies to 2017 - [#43](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/43) - Separate functional tests from unit tests - [#48](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/48) - Make functional tests work also on Windows - [#39](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/39) **Deprecation note**. The ~~promoteRepository~~ and ~~closeAndPromoteRepository~~ tasks are marked as deprecated and will be removed in one of the future versions. `releaseRepository` and `closeAndReleaseRepository` can be used as drop-in replacements. ### [`v0.7.0`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#070---2017-03-27) - Verify that repository has been really closed - [#21](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/21) - Re-enable sharing stagingRepositoryId between close and promote - [#46](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/46) - Basic functional tests with different Gradle versions - [#41](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/41) - Suggest longer timeout if failed on time related operations even without `--info` enabled - [#34](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/34) - Longer default retry period - [#12](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/12) ### [`v0.6.1`](https://togithub.com/Codearte/gradle-nexus-staging-plugin/blob/master/CHANGELOG.md#061---2017-03-20) - Reusing `stagingRepositoryId` from close task bypasses retry mechanism and fails - [#44](https://togithub.com/Codearte/gradle-nexus-staging-plugin/issues/44) - reusing `stagingRepositoryId` is temporary disabledConfiguration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.