Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consistent order of import statements for IDEs #2117

Closed
msteiger opened this issue Jan 9, 2016 · 0 comments
Closed

Consistent order of import statements for IDEs #2117

msteiger opened this issue Jan 9, 2016 · 0 comments
Labels
Category: Build/CI Requests, Issues and Changes targeting gradle, groovy, Jenkins, etc. Category: Doc Requests, Issues and Changes targeting javadoc and module documentation
Milestone
Alpha 1 - v1.0.0

Comments

@msteiger
Copy link
Member

msteiger commented Jan 9, 2016

This is based on the discussion in the forum: http://forum.terasology.org/threads/order-of-import-statements.1323/#post-12064

I believe we should stick with the IntelliJ default, since this is what the majority uses and how 90% of the code is currently formatted. So what is needed is a config file for eclipse that changes the order so that it matches that of IntelliJ.
@Cervator Cervator added Category: Doc Requests, Issues and Changes targeting javadoc and module documentation Category: Build/CI Requests, Issues and Changes targeting gradle, groovy, Jenkins, etc. labels Jan 10, 2016
@rzats rzats mentioned this issue Feb 29, 2016
Merged
@Cervator Cervator added this to the v1.0.0 milestone Feb 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Category: Build/CI Requests, Issues and Changes targeting gradle, groovy, Jenkins, etc. Category: Doc Requests, Issues and Changes targeting javadoc and module documentation
Projects
None yet
Milestone
Alpha 1 - v1.0.0
Development

No branches or pull requests
2 participants
@Cervator @msteiger