Releases: GradleUp/nmcp
1.5.0
Nmcp 1.5.0 adds nmcpPublishDeployment() to publish an existing deployment to the Central Portal (#251):
./gradlew nmcpPublishDeployment -PnmcpDeploymentId=$deploymentId'
Many thanks @marcphilipp for the contribution!
v1.4.4
Nmcp 1.4.4 retries more aggressively when Sonatype is flaky, and makes it more explicit that publishAllProjectsProbablyBreakingProjectIsolation() is still OK to use if you don't mind about project isolation.
v1.4.3
v1.4.2
Version 1.4.2 fixes snapshots returning 400 on XML 1.1 and handles some configuration errors more gracefully.
👷♂️ All changes
v1.4.1
Nmcp 1.4.1 refines the aggregation dependency resolution to avoid including by mistake projects that do not apply com.gradleup.nmcp.
👷 All changes
- Fix zip files could contain unexpected files #227
- Bump Kotlin, OkHttp, xmlutil and a bunch of other dependencies #228
Full Changelog: v1.4.0...v1.4.1
v1.4.0
Nmcp can now be 100% configured from settings.gradle[.kts]:
// settings.gradle.kts
plugins {
id("com.gradleup.nmcp.setting").version("1.4.0")
}
nmcpAggregation {
centralPortal {
username = TODO()
password = TODO()
// ...
}
}This makes it easy to centralize configuration for simple projects.
1.4.0 also contains a few quality of life improvements courtesy of @SimonMarquis and fixes an issue that could sometimes cause maven-metadata.xml to be out of sync.
📚 New docs
There is now a dedicated site with more details about different ways to configure nmcp: https://gradleup.com/nmcp/
👷♂️ All changes
- Clamp remaining time to seconds #213
- maven-metadata.xml: make sure the base version is always added to the list of versions #214, #222
- Set an explicit configuration name to load nmcp-tasks #215
- Register tasks earlier so that they are generated as typesafe tasks accessors #219
- Expand the zip files when passing it to
allFiles#218 - Publish to nmcp repo tasks should never be up-to-date #221
- Allow to configure the whole build from the settings script #223
v1.3.0
This version enables classloader isolation to fix issues such as #210.
v1.2.1
Version 1.2.1
A few fixes mostly around the settings plugin + publishing timeout and a new API for those using the plugin programmatically.
All Changes
- Settings plugin: only apply to subprojects if the maven-publish plugin is applied by @martinbonnin in #196
- Settings plugin: allow the root project to apply both the regular and aggregation plugins by @martinbonnin in #198
- Use allprojects {} instead of subprojects {} by @martinbonnin in #199
- Fix publishing timeout by @martinbonnin in #201
- Add publishFileByFile(File, File) helper function by @martinbonnin in #207
v1.2.0
Bunch of fixes + you can now call nmcpPublishAggregationToMavenLocal to verify your publishing process and/or test locally.
All changes:
- Add plugin marker for the settings plugin by @martinbonnin in #184
- Update to gratatouille 0.1.1 and use
@GPluginfor the settings plugin by @martinbonnin in #185 - Use the snapshot version of the gratatouille plugin by @martinbonnin in #187
- Add nmcpPublishAggregationToMavenLocal by @martinbonnin in #192
- Always populate snapshotVersions manually by @martinbonnin in #193
- Bump bootstrapped version by @martinbonnin in #194
v1.1.0
This version uploads SNAPSHOTs publications in parallel by default (inside a single publication, files are still uploaded serially, which means this is only useful for multi-publications uploads).
On the Apollo Kotlin repo, this made the snapshot CI workflow down to ~30min from ~1h previously.
If you notice any issue, you can roll back to the previous behaviour with uploadSnapshotsParallelism:
nmcpAggregation {
centralPortal {
uploadSnapshotsParallelism.set(1)
}
}You may also experiment with different values of parallelism (current default is 8). If you do, let us know your findings!
What's Changed
- Improve comment and error message #176
- Add option to upload snapshots in parallel by @martinbonnin in #180
- Update compat-patrouille #179
- Enable parallelism by default by @martinbonnin in #181