Closed
Description
- There is Spring Integration Framework Code Style that documents import statements.
- There is also Spring Framework Code Style that also documents import statements.
And they are different. Is this intended?
Maybe this is not a problem in itself, but the same document suggests:
Some code conventions you can pick up for your IDE from the Spring Framework templates: InteglliJ IDEA or Eclipse.
I tried to import the template into InteglliJ IDEA and found out that imports are really in different order. For example static imports are last according to this commit (and it looks like this is right for Spring Framework Code Style, but wrong for Spring Integration Framework Code Style).
Maybe it's worth to add dedicated templates for IDEs with Spring Integration Framework Code Style? Or change the code style to match Spring Framework Code Style, I don't know.