Skip to content

Commit 9893048

Browse files
committed
Merge branch '6.5.x' into 7.0.x
2 parents 4f97217 + e17d85e commit 9893048

1 file changed

Lines changed: 21 additions & 0 deletions

File tree

README.adoc

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,27 @@ The https://github.com/spring-projects/spring-security/tree/docs-build[playbook
6868

6969
Discover more commands with `./gradlew tasks`.
7070

71+
=== IDE setup (IntelliJ)
72+
73+
No special steps are needed to open Spring Security in IntelliJ.
74+
75+
=== IDE setup (Eclipse and VS Code)
76+
77+
To work in Eclipse or VS Code, first generate Eclipse metadata so you can import the project into Eclipse or VS Code:
78+
79+
[indent=0]
80+
----
81+
./gradlew cleanEclipse eclipse
82+
----
83+
84+
If you have not built the project yet, run `./gradlew publishToMavenLocal` first so dependencies are resolved.
85+
86+
*VS Code:* Open the repository root as a folder. The repository includes `.vscode/settings.json` which disables automatic Gradle import so that the generated Eclipse metadata (`.classpath`, `.project`) is used. Do not use the Gradle for Java extension to import the project.
87+
88+
*Eclipse:* File → Import → General → Existing Projects into Workspace, then select the repository root.
89+
90+
The build uses a custom Eclipse plugin to work around Gradle dependency cycles that confuse IDE metadata generation. You may see Eclipse warnings about `xml-apis` from some test dependencies; those are excluded in the build and can be ignored.
91+
7192
== Getting Support
7293
Check out the https://stackoverflow.com/questions/tagged/spring-security[Spring Security tags on Stack Overflow].
7394
https://spring.io/support[Commercial support] is available too.

0 commit comments

Comments
 (0)