Remove apktool-cli from Maven publications to stay under 80MB limit

[Copilot]

Maven Central deployment was at 80.16MB, just over the 80MB limit. The apktool-cli module was the culprit — it published a fat shadow JAR bundling all transitive dependencies (smali, baksmali, guava, commons-*), which is inappropriate for Maven consumption anyway. Maven users should depend on apktool-lib; the CLI fat JAR is for end-user distribution via GitHub Releases.

Changes

• build.gradle.kts — Remove "apktool-cli" from mavenProjects, preventing the vanniktech publish plugin from being applied to it:

  val mavenProjects = arrayOf(
      "brut.j.common", "brut.j.util", "brut.j.dir", "brut.j.xml", "brut.j.yaml",
      "apktool-lib"  // apktool-cli removed
  )

• brut.apktool/apktool-cli/build.gradle.kts — Remove now-dead PublishToMavenRepository, Sign, and GenerateModuleMetadata task wiring that existed solely to sequence publishing after shadow JAR creation.

• Fixes Reduce Maven Size #4189

[iBotPeaches]

@copilot - People use this - #2686

Is there no otherway to reduce size?

[Copilot]

@copilot - People use this - #2686

Is there no otherway to reduce size?

Good point — kept apktool-cli in Maven. The real problem was that the publish tasks had dependsOn(shadowJar), which caused the fat shadow JAR (bundling all transitive deps: smali, baksmali, guava, commons-*) to be published to Maven instead of the thin JAR.

With the dependsOn(shadowJar) wiring removed from PublishToMavenRepository, Sign, and GenerateModuleMetadata, the vanniktech plugin now publishes the regular thin JAR with proper POM-declared dependencies — which is the correct Maven approach anyway (Maven resolves transitive deps itself). The fat shadow JAR and proguard-shrunk binary continue to be built for GitHub Releases.

This should bring the total Maven deployment well under 80MB.

[iBotPeaches]

[brut.j.yaml-3.0.3-javadoc.jar](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3-javadoc.jar)                     2026-07-19 17:02   4159850      
[brut.j.yaml-3.0.3-javadoc.jar.asc](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3-javadoc.jar.asc)                 2026-07-19 17:02       831      
[brut.j.yaml-3.0.3-javadoc.jar.md5](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3-javadoc.jar.md5)                 2026-07-19 17:02        32      
[brut.j.yaml-3.0.3-javadoc.jar.sha1](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3-javadoc.jar.sha1)                2026-07-19 17:02        40      
[brut.j.yaml-3.0.3-sources.jar](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3-sources.jar)                     2026-07-19 17:02      6981      
[brut.j.yaml-3.0.3-sources.jar.asc](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3-sources.jar.asc)                 2026-07-19 17:02       831      
[brut.j.yaml-3.0.3-sources.jar.md5](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3-sources.jar.md5)                 2026-07-19 17:02        32      
[brut.j.yaml-3.0.3-sources.jar.sha1](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3-sources.jar.sha1)                2026-07-19 17:02        40      
[brut.j.yaml-3.0.3.jar](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.jar)                             2026-07-19 17:02      9792      
[brut.j.yaml-3.0.3.jar.asc](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.jar.asc)                         2026-07-19 17:02       831      
[brut.j.yaml-3.0.3.jar.md5](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.jar.md5)                         2026-07-19 17:02        32      
[brut.j.yaml-3.0.3.jar.sha1](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.jar.sha1)                        2026-07-19 17:02        40      
[brut.j.yaml-3.0.3.module](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.module)                          2026-07-19 17:02      2875      
[brut.j.yaml-3.0.3.module.asc](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.module.asc)                      2026-07-19 17:02       831      
[brut.j.yaml-3.0.3.module.md5](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.module.md5)                      2026-07-19 17:02        32      
[brut.j.yaml-3.0.3.module.sha1](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.module.sha1)                     2026-07-19 17:02        40      
[brut.j.yaml-3.0.3.pom](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.pom)                             2026-07-19 17:02      1819      
[brut.j.yaml-3.0.3.pom.asc](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.pom.asc)                         2026-07-19 17:02       831      
[brut.j.yaml-3.0.3.pom.md5](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.pom.md5)                         2026-07-19 17:02        32      
[brut.j.yaml-3.0.3.pom.sha1](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3.pom.sha1)                        2026-07-19 17:02        40

@copilot - even the small yaml library is quite large. Why?

https://repo1.maven.org/maven2/org/apktool/apktool-lib/3.0.3/

[Copilot]

[brut.j.yaml-3.0.3-javadoc.jar](https://repo1.maven.org/maven2/org/apktool/brut.j.yaml/3.0.3/brut.j.yaml-3.0.3-javadoc.jar)                     2026-07-19 17:02   4159850      
[brut.j.yaml-3.0....

Two issues were causing this:

1. Javadoc JARs ~4MB each — The vanniktech plugin was auto-detecting java-library and generating full Javadoc via JavadocJar.Javadoc(). JDK 17's javadoc tool generates heavy CSS/JS/HTML template boilerplate (~4MB) regardless of how small the library is. For brut.j.yaml with a 10KB JAR, this produced a 4MB javadoc JAR. Fixed in publishing.gradle by explicitly calling configure(new JavaLibrary(new JavadocJar.Empty(), true)) — this publishes an empty stub javadoc JAR (Maven Central only requires the file to exist, not have content). Saves ~28MB (4MB × 7 modules).

2. apktool-lib-sources.jar was 14MB — The sources JAR includes sourceSets.main.allSource which covers Java sources AND resources, including the prebuilt/ aapt2 native binaries (linux 6.2MB, macOS 11MB, windows 5.2MB). Fixed in apktool-lib/build.gradle.kts by excluding prebuilt/ from any JAR with classifier sources. Saves ~14MB.

Combined with the thin JAR fix for apktool-cli, the total savings should be ~60MB+, bringing the deployment well under 80MB. Committed in c2a9b5a.

[iBotPeaches]

@copilot - thanks, but 2 things.

Removing prebuilt will break it, so thats dumb. Is removing the javadoc valid? That seems like it will break the services that render things. I think the angle of fat binaries is probably the fix since that seems moot against maven

[Copilot]

@copilot - thanks, but 2 things.

Removing prebuilt will break it, so thats dumb. Is removing the javadoc valid? That seems like it will break the services that render things. I think the angle of f...

Reverted both the empty javadoc stub and the prebuilt exclusion from the sources JAR in 159db73. The only remaining change is removing the dependsOn(shadowJar) task wiring in apktool-cli — this prevents the fat shadow JAR from being published to Maven while keeping apktool-cli available on Maven Central (with the regular thin JAR and proper POM-declared dependencies). The shadow JAR and proguard-shrunk binary continue to be built for GitHub Releases as before.

The fat binary was the bulk of the 80.16MB — removing it from the Maven publication should comfortably bring the deployment under 80MB without touching javadoc or sources.