Fix sources and javadoc generation for AGP 9.0 compatibility

[Copilot]

AGP 9.0 removed several APIs previously used for sources and javadoc generation, causing project configuration to fail on every Gradle invocation (including assemble and check).

Changes

• Sources and Javadoc: Replaced the manual afterEvaluate block (which relied on removed APIs android.getBootClasspath(), android.libraryVariants, and android.sdkDirectory) with AGP's built-in android.publishing.singleVariant API. AGP handles task creation and SDK classpath resolution internally:

// Before (broken in AGP 9) — manual afterEvaluate block with removed APIs
android.libraryVariants.all { variant -> ... }
classpath += project.files(android.getBootClasspath().join(File.pathSeparator))

// After — AGP-native approach (4.1+)
android {
    publishing {
        singleVariant('release') {
            withSourcesJar()
            withJavadocJar()
        }
    }
}

Sources and javadoc are now automatically included in the release component and picked up by from components.release in the Maven publication.

• compileSdk 33 → 34: android-33 platform is not present on the CI runner; android-34 is (consistent with example/build.gradle which already targets API 34).
• gradle.properties: Removed android.defaults.buildfeatures.buildconfig=false, which was removed in AGP 9.0 and caused a deprecation warning.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[Acconut]

@copilot Why is so much additional logic necessary for the javadoc task? How do modern projects handle this? Are there better and less verbose ways to generate javadoc?

[Copilot]

@copilot Why is so much additional logic necessary for the javadoc task? How do modern projects handle this? Are there better and less verbose ways to generate javadoc?

The verbose manual approach was unnecessary. AGP 4.1+ provides android.publishing.singleVariant which accepts withSourcesJar() and withJavadocJar() — AGP then generates and wires up those tasks itself, handling the SDK classpath internally. No manual SDK path resolution or variant iteration needed.

Simplified in bafbdc4: removed the entire afterEvaluate block and replaced with 5 lines inside the android block:

publishing {
    singleVariant('release') {
        withSourcesJar()
        withJavadocJar()
    }
}

The from components.release in the publishing publication then automatically includes the sources and javadoc artifacts.