From a085a12c99d1f99d9b27ca3a58b9fcfaf910a28b Mon Sep 17 00:00:00 2001 From: Andreas Falk Date: Mon, 16 Sep 2019 11:29:07 +0200 Subject: [PATCH] Fix wrong java runtime version mentioned in reference doc The reference documentation still referred to Java 5.0 as minimum runtime version which is wrong. This commit changes this to the correct Java 8 runtime version as required minimum version. In addition it corrects a fuzzy wording regarding stripping down the `spring-security-core` jar. Fixes gh-7440 --- .../_includes/servlet/architecture/technical-overview.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/manual/src/docs/asciidoc/_includes/servlet/architecture/technical-overview.adoc b/docs/manual/src/docs/asciidoc/_includes/servlet/architecture/technical-overview.adoc index de0cedb91e..12bb885d5c 100644 --- a/docs/manual/src/docs/asciidoc/_includes/servlet/architecture/technical-overview.adoc +++ b/docs/manual/src/docs/asciidoc/_includes/servlet/architecture/technical-overview.adoc @@ -5,7 +5,7 @@ [[runtime-environment]] === Runtime Environment -Spring Security 3.0 requires a Java 5.0 Runtime Environment or higher. +Spring Security {spring-security-version} requires a Java 8 Runtime Environment or higher. As Spring Security aims to operate in a self-contained manner, there is no need to place any special configuration files into your Java Runtime Environment. In particular, there is no need to configure a special Java Authentication and Authorization Service (JAAS) policy file or place Spring Security into common classpath locations. @@ -17,7 +17,7 @@ This design offers maximum deployment time flexibility, as you can simply copy y [[core-components]] === Core Components -In Spring Security 3.0, the contents of the `spring-security-core` jar were stripped down to the bare minimum. +As of Spring Security 3.0, the contents of the `spring-security-core` jar were stripped down to the bare minimum. It no longer contains any code related to web-application security, LDAP or namespace configuration. We'll take a look here at some of the Java types that you'll find in the core module. They represent the building blocks of the framework, so if you ever need to go beyond a simple namespace configuration then it's important that you understand what they are, even if you don't actually need to interact with them directly.