Repository navigation
Consolidate combined releases into the original plugin for 2.4.0 - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Combined-only roots currently need a second plugin ID to avoid registering single-publication release tasks. Consolidate that workflow into
se.alipsa.nexus-release-pluginthroughnexusReleasePlugin { combinedRelease { } }, with shared path, credential and endpoint conventions. The root-onlynexusReleasePlugin.rootSinglePublicationTasks=falseproperty preserves unqualified subprojectbundle/releaseselectors and custom root tasks; existing single-publication behavior remains the default.Shared properties are created before task registration, so eager convention rules work. The registrar is constructor-supplied and private, and combined task providers are read-only. Remove the separate plugin declaration/marker and
ReleaseAllSupportPluginclass, document Groovy/Kotlin migration and unchanged timeout behavior, and set the development version to2.4.0-SNAPSHOT.Validation:
-PrequireShellHarness=true, including charset and shell checks.releaseAll.publishPlugins --validate-only -Pversion=2.4.0passed without upload. The version override is required because the Portal rejects SNAPSHOT validation.See
req/verification/v2.4.0-single-plugin.mdfor the commands and results. Matrix's external build and guide need the documented consumer migration separately; no external repository or real Portal deployment was changed.