SEC-1161: is missing #1404

spring-issuemaster opened this Issue May 11, 2009 · 6 comments


None yet
1 participant

Luke Taylor said:

There hasn't been (and won't be) a 2.5 release therefore this schema name is now considered invalid. The next schema will be spring-security-3.0.xsd.

Luke Taylor said:

This shouldn't be a critical issue in any case, as it will only impact the use of an XML editor which pulls the schema from the site. The code uses the version from the jar and you can set up an XML catalog in most IDEs and XML editors.

What is the actual problem?

Georgy Bolyuba said:

For some reason the spring security jar I have (using Maven) does not have xsd. As the result all CI builds failed yesterday. Update to 3.0.0 seems to work, so, it is not critical.

Luke Taylor said:

So you are building against a snapshot of the trunk? If so that must be a bit of a bumpy ride at the moment :). Certainly bleeding edge...

Georgy Bolyuba said:

Actually no :) Just looked at pom.xml. It is 2.0.4, but in configs it is Currently I am trying to figure out why this was done.

Luke Taylor said:

OK. It may have been some confusion with Spring namespace versions. The next release will have aligned version numbers which should help.

Closing the issue.

spring-issuemaster added this to the 3.0.0 M1 milestone Feb 5, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment