You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.adoc
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,27 @@ The https://github.com/spring-projects/spring-security/tree/docs-build[playbook
68
68
69
69
Discover more commands with `./gradlew tasks`.
70
70
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
+
71
92
== Getting Support
72
93
Check out the https://stackoverflow.com/questions/tagged/spring-security[Spring Security tags on Stack Overflow].
73
94
https://spring.io/support[Commercial support] is available too.
0 commit comments