Skip to content

[MSHADE-368] - Preserve one-sided Groovy extensions - #832

Open
wilx wants to merge 2 commits into
apache:masterfrom
wilx:issue-572-groovy-resource-transformer
Open

[MSHADE-368] - Preserve one-sided Groovy extensions#832
wilx wants to merge 2 commits into
apache:masterfrom
wilx:issue-572-groovy-resource-transformer

Conversation

@wilx

@wilx wilx commented Jul 31, 2026

Copy link
Copy Markdown

Fixes #572.

Summary

Preserve Groovy extension-module descriptors that declare only instance
extension classes or only static extension classes.

Groovy permits either extension category to be empty. The
GroovyResourceTransformer previously reported a transformed resource only
when both categories were populated. Shade had already consumed the original
descriptor by that point, so it wrote neither the original descriptor nor an
aggregated replacement.

The transformer now reports output when either category contains extension
classes. A new MSHADE-368 integration test shades the real
groovy-sql:3.0.0 artifact and verifies that its instance-only extension
descriptor and implementation class survive in the shaded JAR.

Tests

  • mvn -Prun-its clean verify
    • 72 unit tests passed;
    • 84 integration projects passed; and
    • two JRE-gated integration projects were skipped.

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MSHADE-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MSHADE-XXX with the appropriate JIRA issue. Best practice
    is to use the JIRA issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

wilx added 2 commits July 31, 2026 12:30
Reproduce shading an extension module that only declares instance extension classes. Verify that the transformed descriptor and its extension class survive in the shaded JAR.
Write the aggregated descriptor when either instance or static extension classes were collected. Groovy extension modules do not need to declare both kinds.

Fixes apache#572.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[MSHADE-368] GroovyResourceTransformer fails for some extensions

1 participant