Zongle Wang

Results 555 comments of Zongle Wang

As `java-gradle-plugin` applies `com.gradle.plugin-publish`, I guess we can fix this by replacing https://github.com/vanniktech/gradle-maven-publish-plugin/blob/b4b02a655660125529d60d93ea3b390858705bae/plugin/src/main/kotlin/com/vanniktech/maven/publish/MavenPublishBaseExtension.kt#L474-L477 with ```kt project.plugins.hasPlugin("com.gradle.plugin-publish") || project.plugins.hasPlugin("java-gradle-plugin") -> configure(GradlePlugin(defaultJavaDocOption(javadocJar, plainJavadocSupported = true), sourcesJar)) ``` --------- EDIT: we can't.

I noticed a workaround for this issue: ```kt afterEvaluate { tasks.named("javadocJar") { from(tasks.dokkaGeneratePublicationJavadoc) } } ``` See https://github.com/gmazzo/gradle-buildconfig-plugin/blob/05718d048acd733450fb3ed31231bc31a375ebf8/plugin/build.gradle.kts#L112-L116. Should we patch it from the plugin side?

Need to update Spotbugs...

Something is wrong with Selfie? https://scans.gradle.com/s/faaa7fn7fbcik/tests/overview?outcome=FAILED

@Sidnioulz You can try out https://github.com/ComposeGears/Valkyrie.

If you need this CLI, I'll try to finish it in Valkyrie, so busy for now...

Now you can try out https://github.com/ComposeGears/Valkyrie instead.

This looks outdated.

May have to update the release workflow, e.g from `./gradlew publishToMavenLocal` to `./gradlew :secrets-gradle-plugin:publishToMavenLocal`.