44a474a014
Remove the 'final' modifier from SingletonBeanFactoryLocatorTests to work around the "cannot extend final class" error issued when running all tests. The error was due to confusion with IDEA between the two variants of SingletonBeanFactoryLocatorTests across spring-context and spring-beans. Rename one of the GroovyMessenger classes to GroovyMessenger2. Previously there were multiple Groovy classes named 'GroovyMessenger', causing a compilation error in certain IDE arrangements. Update import-into-idea.md documentation Add various IDEA artifacts to .gitignore - ignore derby.log wherever it is written - ignore IDEA's test-output directory - ignore IDEA's Atlassian connector config file
1.3 KiB
1.3 KiB
The following has been tested against Intellij IDEA 12.0
Steps
Within your locally cloned spring-framework working directory:
- Generate IDEA metadata with
./gradlew :spring-oxm:compileTestJava cleanIdea idea - Import into IDEA as usual
- Set the Project JDK as appropriate
- Add git support
- Code away
Known issues
spring-aspectsdoes not compile out of the box due to references to aspect types unknown to IDEA. See http://youtrack.jetbrains.com/issue/IDEA-64446 for details. In the meantime, you may want to excludespring-aspectsfrom the overall project to avoid compilation errors.- While all JUnit tests pass from the command line with Gradle, many will fail when run from IDEA. Resolving this is a work in progress. If attempting to run all JUnit tests from within IDEA, you will likely need to set the following VM options to avoid out of memory errors: -XX:MaxPermSize=2048m -Xmx2048m -XX:MaxHeapSize=2048m
Tips
In any case, please do not check in your own generated .iml, .ipr, or .iws files. You'll notice these files are already intentionally in .gitignore. The same policy goes for eclipse metadata.
FAQ
Q. What about IDEA's own Gradle support?
A. Keep an eye on http://youtrack.jetbrains.com/issue/IDEA-53476