Move Keycloak builtin-users-spi jar to its own repo
Open
Nobody has claimed this yet.
FY27 Sprint 3
Size: 30
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
As discussed in standup, we plan to move conf/keycloak/builtin-users-spi to its own repo.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing conf/keycloak/builtin-users-spi and the surrounding repository configuration to understand how this jar is built and referenced. Check the discussion mentioned in the issue for the intended destination and migration constraints. Done should mean the component is moved to its own repository without leaving unresolved references in Dataverse.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100