Community hub release parent

Development
1

Hello,

the keycloak plugin has a dependency to

Should we fork this and push it to mavencentral like it was done with GitHub - operaton/operaton-release-parent ?

Cheers,
Julian

3 Likes
2

i created a test fork here: GitHub - hauptmedia/community-hub-release-parent: Pom which can be inherited for community hub maven releases defining some common release properties

3

Hey, thanks for the initiative! I’m not able to check on a computer right now, but I wonder what the difference between the community-hub-release-parent and the (former) camunda-release-parent is. I’m not sure if we need the differentation in the future and maybe it would be beneficial if we manage to only have one release parent in the future? Hope to be able to diff those two tommorow :crossed_fingers:

1 Like
4

I didn’t spend to much time to look why it’s even there. I guess it has something to do with their internal artifact repositories and github action runners for community projects. I just made it work to to get everything we need running for a fully working replacement with operaton.

5

We talked about this here: Keycloak Plugin - #8 by javahippie

I think there should be two types of projects:

  1. Extensions maintained by Operaton, they inherit the existing operaton-release-parent, as they will be deployed in the org.operaton Namespace in central Nexus, which we control. They are hosted in the GitHub org of Operaton, so they can access secrets for automated deployment from GitHub Workflows (later in time)
  2. Extensions from the community. These won’t have any requirements for a parent pom, as it is the maintainers decision how and where they will be published. The Operaton GitHub org has no responsibilities or rights on those repositories, they are 100% under the control of the maintainer.

If a maintainer decides to move a library / plugin to the Operaton org, this can be discussed, imho. Does this sound like a sensible approach?

1 Like
6

i think this is a good way to do it. So the concrete todos are:

  • Rebase keycloak plugin to the operaton-release-parent
  • Move keycloak repo to operaton

Then basically this issue can be closed - we will not have a community hub release parent

1 Like
7

I have removed the community-hub-release-parent fork, as it is no longer needed and to avoid any confusion

1 Like