Better naming for deployment name for Central Portal

[krizzu]

For context: the name of deployment to Central Portal is groupdId + deployment Id (UUID).

With multiple artifacts under one group ID, it is hard to tell, in Central Portal's dashboard, which deployment refers to which artifact, unless one inspects content of it . I think it'd be good to also include artifact name as part of deployment name, to improve readability. I'm happy to open a PR. Thoughts?

[gabrielittner]

Our main issue is that if you have a multi module project that the deployment will contain the artifacts of all modules, so there isn't just one artifact name. Even the way we're using group right now is slightly opportunistic since technically you could use different groups within one project. I'm generally happy to improve this though if you have an idea on how to solve that part.

[krizzu]

I feel like adding a new property to mavenPublishing extension could satisfy the needs for all situations, something like:

mavenPublishing {
  // ...others
  deploymentName = "$group-$artifactName-$version-${UUID.randomUUID()}"
}

[MFlisar]

@gabrielittner does anything speak against a manual option like @krizzu suggested just to provide this function for those who want it? I would need that as well...

In a multi module setup I do define each artifact ids manually because they do not match the structure of my projects and I would like to provide a custom name for the deployment as well like "$libraryName-$version" instead of a random name that only contains my groupId an a guid...

[kibotu]

I've seen a profil-id branch, any progress? :D

[kibotu]

can anyone explain to me how to publish a gradle plugin? jitpack is apparently not enough