This message was deleted.

As far as I remember it often is the cause of confusion, when people should configure the publication the plugin added and instead create an additional publication or something like that. Can't you just configure the publication the plugin is adding to your needs?

you mean the publication?

Indeed, fixed

We have an internal publishing plugin that does declare a publication and does add all kinds of stuff to it from configuration to validation. for sure we will find some sort of workaround but IMO it's just an additional pain in the a** and things are getting less and less flexible. There used to be some sort of onion pattern, where conventions are added on top of basic functionality. Now I'm forced to use a convention I don't comply with and cannot avoid this by declaring a more basic plugin without that additional convention doing all kind of stuff I don't need or want . The publication convention is hardly coupled to the java gradle plugin plugin and IMO it shouldn't.

You might be right and it might be potential for improvement. Maybe open an issue about it so they either can separate the concerns or undeprecate the setting. Wouldn't be the first time it they do it

wanted to get feedback on this here before raising a ticket

René, see questions in https://gradle-community.slack.com/archives/CAHSN3LDN/p1662371429159189 please