spring-projects / spring-projects/spring-security
Automate updating schema symlinks
Open
Nobody has claimed this yet.
in: build
type: task
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
For each release, three manual steps are necessary to keep schema XSD links up to date on the docs server:
- Copy the spring-security-oauth schema files into the current release directory, e.g.
cd /var/www/domains/spring.io/docs/htdocs/autorepo/schema/spring-security
cp 5.5.0/security/spring-security-oauth-* 5.6.0/security/
- Symlink the highest-versioned XSD to
spring-security.xsd, e.g.
ln -s spring-security-5.6.0.xsd 5.6.0/security/spring-security.xsd
- Symlink the current release to the current directory, e.g.
ln -sfn 5.6.0 current
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
The issue names no repository file, test, or automation entry point. Start by locating the release process that publishes schema files to the docs server, then determine how it can perform the three listed copy and symlink steps; done means a release updates the versioned schema, spring-security.xsd, and current links without manual commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100