This document will guide you through the process of importing the Spring Framework projects into Eclipse or the Spring Tool Suite (STS). It is recommended that you have a recent version of Eclipse. As a bare minimum you will need Eclipse with full Java 8 support, Eclipse Buildship, the Kotlin plugin, and the Groovy plugin.
The following instructions have been tested against STS 4.3.2 (download) (based on Eclipse 4.12) with Eclipse Buildship. The instructions should work with the latest Eclipse distribution as long as you install Buildship. Note that STS 4 comes with Buildship preinstalled.
When instructed to execute
./gradlew from the command line, be sure to execute it within your locally cloned
spring-framework working directory.
Info.plistfile located in the
Contentsfolder of the installed Eclipse or STS application (e.g., the
spring-aspectsproject. The AspectJ Development Tools available in the Eclipse Marketplace have been tested with these instructions using STS 4.5 (Eclipse 4.14).
spring-oxmfrom the command line with
./gradlew eclipseBuildshipfrom the command line.
spring-frameworkdirectory -> Select Finish).
spring-aspectsproject from the import, if prompted, or close it after the import.
spring-oxmproject and wish to have the generated sources available, add the
build/generated-sources/jaxbfolder to the build path (right click on the
jaxbfolder and select
Build Path -> Use as Source Folder).
buildfolder in the
spring-oxmproject, ensure that the "Gradle build folder" is not filtered out from the view. This setting is available under "Filters" in the configuration of the Package Explorer (available by clicking on the small downward facing arrow in the upper right corner of the Package Explorer).
spring-oxmshould be pre-compiled due to repackaged dependencies.
*RepackJartasks in the build.
spring-aspectsdoes not compile due to references to aspect types unknown to Eclipse.
-XX:MaxPermSize=2048m -Xmx2048m -XX:MaxHeapSize=2048m
In any case, please do not check in your own generated
.settings folder. You'll notice these files are already intentionally in
.gitignore. The same policy holds for IDEA metadata.
：Code submit frequency
：React/respond to issue & PR etc.
：Well-balanced team members and collaboration
：Recent popularity of project
：Star counts, download counts etc.