Andres Almiray

> It's somehow more complicated. We don't have that mechanism out of the box. Probably, it will be implemented once better support for monorepos is requeted (and provided). At the...

Yes, but no. I do want the `maven-publish` plugin for other reasons. I simply do not wish a specific subset of modules to be published to Maven Central. current the...

I'd prefer if the include/exclude lists were provided by the plugin's extension. Less code to copy around by consumers IMHO.

It depends. What is `mavenCentralProjects`? If it's a list of `String` or `Project` then the value must be calculated eagerly. If it's a predicate then the list is calculated on...

Ping. Wondering if the team has circled back to @marcphilipp's latest idea on this topic.

I understand the current conditional on `maven-publish` and that doesn't work for my use case as that plugin is applied to all subprojects by default. Would your suggestion to split...

The `org.kordamp.gradle.publishing` plugin applies the `mavne-publish` plugin to all projects in a particular multi-project setup. See https://github.com/kordamp/kordamp-gradle-plugins/blob/e744cb7197e8ae0d9cc66c4b064f50776f08723d/plugins/publishing-gradle-plugin/src/main/groovy/org/kordamp/gradle/plugin/publishing/PublishingPlugin.groovy#L66-L109 The idea is to let subprojects determine if publication should be enabled or...

Perhaps I explained myself badly. The core maven-publish plugin uses `afterEvaluate` to realize all publications, there is no workaround for it unless Gradle core changes. GNPP in turn could use...

FYI This was recently discussed at the Maven user list https://lists.apache.org/thread.html/r7c8b6e6b219cd3fb144b990f1b88d95d7d53ea54c7b9cec8944e5a0a%40%3Cusers.maven.apache.org%3E

Yes, I’ll rebase the PR with `develop` and apply the suggestion by @svenreimers. Give me 1 day and it’ll be done :smile: