Skip to content

Commit d0f493c

Browse files
committed
Fix InteliJ code formatter instructions
Update CONTRIBUTING.adoc with improved code formatter instructions. Fixes gh-1271
1 parent 650e326 commit d0f493c

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

CONTRIBUTING.adoc

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,10 +16,12 @@ given the ability to merge pull requests.
1616
None of these is essential for a pull request, but they will all help. They can also be
1717
added after the original pull request but before a merge.
1818

19-
* Use the Spring Framework code format conventions. Import `eclipse-code-formatter.xml`
20-
from the `eclipse` folder of the project if you are using Eclipse. If using IntelliJ,
21-
copy `spring-intellij-code-style.xml` to `~/.IntelliJIdea*/config/codestyles` and select
22-
spring-intellij-code-style from Settings -> Code Styles.
19+
* Use the Spring Framework code format conventions. If you use Eclipse and you follow
20+
the ``Importing into eclipse'' instructions below you should get project specific
21+
formatting automatically. You can also import formatter settings using the
22+
`eclipse-code-formatter.xml` file from the `eclipse` folder. If using IntelliJ, you can
23+
use the [Eclipse Code Formatter Plugin](http://plugins.jetbrains.com/plugin/6546)
24+
to import the same file.
2325
* Make sure all new `.java` files to have a simple Javadoc class comment with at least an
2426
`@author` tag identifying you, and preferably at least a paragraph on what the class is
2527
for.

0 commit comments

Comments
 (0)