Gradle scripts changes to enable plugin signing #9
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.
Splits the buildPlugin Gradle task into a two-phase build process to support external code signing of plugin artifacts
(DLLs and JARs) between the build stages.
New Gradle tasks:
preparePluginForSigning- compiles all artifacts, copies them to a staging directory (build/plugin-staging/), andgenerates a
files-to-sign.txtmanifest listing files that need signing (our own JARs and DLLs, excluding third-partydependencies)
assemblePlugin- packages the staged (optionally signed) files into the final plugin ZIP and creates the NuGetpackage
How it works:
./gradlew buildPlugincontinues to work as before - it runs both phases sequentially with nosigning step in between
middle:
./gradlew preparePluginForSigning → sign server signs files → ./gradlew assemblePlugin