spring-projects / spring-projects/spring-ldap
Consider splitting repositories into separate XSD
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 375
- Forks
- 501
- Avg merge
- 6h 4m
- Merged PRs (30d)
- 63
Description
spring-ldap.xsd imports spring-repository.xsd. This means that spring-data-commons is a required dependency for Spring LDAP XML configuration, even if no Spring Data features are used in an application.
One way to solve this would be to move the repositories definition into a separate XSD.
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
Inspect spring-ldap.xsd and its import of spring-repository.xsd, then locate the repository definitions and their XML configuration tests. Determine how the schemas can be separated without requiring spring-data-commons for LDAP-only configuration; done means the repository definitions have an independent schema and the dependency is no longer required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100