spring-projects / spring-projects/spring-security
Add Build Task for Incrementing Minor Version
Open
Nobody has claimed this yet.
in: build
type: enhancement
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Whenever Spring Security increments a minor version, there is some manual work to do:
- Bump the version in
SpringSecurityCoreVersion - Add an
.rncand.xsdfile - Bump the version in
schema.handlers - Bump the version in
XsdDocumentedTests - Bump the schema count in
XsdDocumentedTests - Bump the version in
security.tld - Bump the version in
gradle.properties - Replace the old What's New section with a skeleton
It would be nice to have a task that did all of this and formulated a corresponding Git commit.
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 locating SpringSecurityCoreVersion, schema.handlers, XsdDocumentedTests, security.tld, gradle.properties, the .rnc and .xsd files, and the What's New section. Trace how minor-version changes are currently made and identify the existing build-task entry point. Done means one task performs all listed updates and formulates the corresponding Git commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100