Remove / replace convention mapping from packaging plugins

[breskeby]

We use the system packaging plugins for Deb and Rpm creation. What I noticed is that these plug-in heavily rely on the deprecated and always internal mechanism of convention mappings. Do be compatible with newer Gradle versions a lot of those are wrapped with whileDeprecationDisabled blocks. For us this is a ticking timebomb as we always use the latest Gradle versions and not sure at what time this will be actually removed. Also it would make supporting Gradle configuration cache way easier IMO. Convention mapping has always been a sort of internal hack for dealing with configuration ordering and these days there is the provider api available that should replace the mechanism of convention mapping.

Two questions:

1. Are there plans to port this plugin to replace convention mapping by provider api?
2. would you be open for a bigger contribution taking care of that at least for parts of the plug-ins. Also what are the backwards compatibility constraints here? The easiest would be to make a clean cut. I’m not completely sure yet what the user facing implications would be yet. There is likely a way to make this compatible with 99% of the builds out there.

Curious about your input.

[rpalcolea]

Hey @breskeby , sorry I missed this

I guess to answer your questions in order 😓

1. We know we have to do it but we just haven't done it due to other priorities but something we want to have before 9.0 RCs are available for example
2. Definitely open and I think it makes sense to make it a major release with no backwards compatibility as it will make things just complex to address and/or maintain. Clean cut is the best avenue imo