-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider adding softlink from spring-security.xsd to latest schema #11365
Comments
Just curious if you were aware that this is used for symlink creation https://github.com/spring-io/autoln |
For sure! I discussed this with @trevormarshall recently, as we were working through gh-11353. Since the file |
@sjohnr I think this might be what you mean https://github.com/spring-projects/spring-framework/wiki/autorepo-version-updating#autoschemaln Shall we try |
Sorry for the delay on this, @trevormarshall. Your suggestion sounds good to me. Do we need to clean up the existing (manually created) symlink for spring-security.xsd first? I'm not sure how different layers of manual and automatic symlinks will interact with each other. |
No I don't believe we do @sjohnr. Let me know when you want me to enable for your directory (or feel free to enable yourselves, if a team member has shell access on the server) |
@trevormarshall Please go ahead now. I'll be available to verify once it's taken effect. |
@sjohnr done. It will be ready to verify in 20 minutes. |
Thanks! |
We should consider adding a relative softlink in
config/src/main/resources/org/springframework/security/config
so thatspring-security.xsd
points to the latest schema.Context
A configuration change was made to allow spring-security-*.xsd files available under https://www.springframework.org/schema/security/ to be automatically linked to the latest artifact extracted to
/var/www/domains/spring.io/docs/htdocs/autorepo/schema
on the web host (see gh-11353).However, the file spring-security.xsd was manually updated to be a softlink to the latest schema (e.g. spring-security-5.7.xsd).
The text was updated successfully, but these errors were encountered: