Sourced from com.gradleup.shadow's releases.

9.2.2

Fixed

• Fix the regression of registering ShadowJar tasks without ShadowPlugin applied. (#1787)

9.2.1

Added

• Support relocating Groovy extensions in Module descriptors. (#1705)
• Add extensions for Iterable<Relocator>. (#1710)
• Support relocating list of types in RelocatorRemapper. (#1714)
• Add mainClass property into ShadowJar. (#1722)

  tasks.shadowJar {
    // This property will be used as a fallback if there is no explicit `Main-Class` attribute set.
    mainClass = "my.Main"
  }
  

• Honor executableDir and applicationName in application extension. (#1740)
  This is useful when you want to customize the output directory of the start scripts and the application distribution.
• Provide more task accessors in ShadowApplicationPlugin.Companion. (#1771)
• Support relocating Kotlin module files. (#1539)
  The current implementation relocates all properties in KotlinModuleMetadata but KmModule.optionalAnnotationClasses due to very limited usage of it. See more discussion here.
• Allow overriding BUNDLING_ATTRIBUTE in GMM. (#1773)
  The org.gradle.dependency.bundling in shadowed JAR's Gradle Module Metadata is set to shadowed by default. You can override it for now by:

  shadow {
    bundlingAttribute = Bundling.EMBEDDED
  }
  

Changed

• Merge Gradle Module descriptors into the modern META-INF path. (#1706)
  The Gradle Module descriptors (org.codehaus.groovy.runtime.ExtensionModule files) defined under META-INF/services/ and META-INF/groovy will be merged into META-INF/groovy/org.codehaus.groovy.runtime.ExtensionModule.
• Move injecting Class-Path manifest attr logic from doFirst into copy. (#1720)
• Move injecting Main-Class manifest attr logic from doFirst into copy. (#1724)
• Deprecate InheritManifest and inheritFrom. (#1722)

  tasks.shadowJar {
    // Before (deprecated):
    manifest.inheritFrom(tasks.jar.get().manifest)
    // After (recommended):
    manifest.from(tasks.jar.get().manifest)
  // Note: You don't need to inherit the manifest from jar task as it's done by default for the shadowJar task.
  
  // But if you want to inherit the manifest for your custom ShadowJar task, you still need to do it explicitly.
  
  

... (truncated)

• 1245cda Prepare version 9.2.2
• a9bf7b5 Fix the link for 9.2.1
• 722b9b8 Fix the regression of registering ShadowJar tasks without ShadowPlugin applie...
• f36fadf Tweak manifest attribute tests (#1786)
• 21f2613 Document more about deprecated inheritFrom (#1783)
• bd7f137 Inline suppressions for InternalGradleApiUsage (#1780)
• 3474bea Update plugin spotless to v8 (#1778)
• 8f3a5e7 Prepare next development version
• 75e4e0f Prepare version 9.2.1
• 698ff03 Prepare next development version
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)