common4j: don't tie sourcesJar/javadocJar to assemble

These tasks are already wired into the publish graph through
components.java + the maven-publish plugin, so they will be
generated automatically when publish runs.

Tying them to assemble made every CI flow that just compiles or
runs tests also build javadoc, which is one of the slowest tasks
in the common4j build. Local developers who want the artifacts
can still run ./gradlew sourcesJar javadocJar explicitly.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: fadidurah

common4j/build.gradle

@@ -339,8 +339,11 @@ buildConfig {
 }
 
 afterEvaluate {
-    assemble.dependsOn sourcesJar, javadocJar
-
+    // sourcesJar and javadocJar are wired into the publish graph via components.java + maven-publish,
+    // so they will run automatically as part of `publish`. There is no need to also tie them to
+    // `assemble`, which made every CI build (including test-only / spotbugs-only flows) generate
+    // javadoc unnecessarily. Generating javadoc for common4j is one of the slower tasks in the build.
+    // Local devs who explicitly want the artifacts can still run `./gradlew sourcesJar javadocJar`.
     // these tasks are generated by the buildconfig plugin..for more details, read comment about it
     // above in the plugins block.
     compileJava.dependsOn generateBuildConfig, generateTestBuildConfig