This message was deleted.

The answer for this is not too easy, so I am pinging better developers than me and they will answer tomorrow probably.

Hey René, The reason we went down that path was to simplify plugin publication setup. With that flag, old recipes remain applicable without folks always realising that they make

.pom

and

.module

out of sync, etc … But maybe we missed a use case. What kind of custom things are you doing? Can you looking into tweaking the

java

component instead, adding and removing variants?

@Louis Jacomet did you look in the next thread? Unfortunately René split it and there is a bit of additional information.

No, I did not. Thanks!

We have a plugin that takes care of all our publications that we for the elasticsearch artifacts. Now We need to use a different publication here and tweak it again. It's not a big issue it's just imo less flexbile to use. I don't see how this is a simplification for us

Can you share some of the specific things you are changing? What are the things that

MavenPluginPublishPlugin

do that are not compatible with your setup?