Create eclipse preference files

[msteiger]

It would be nice to have preference files for eclipse that automatically configure

• Code formatting ( which should be too different from the default settings ). This also includes file headers, etc.
• Compiler settings ( which includes javadoc warnings, java target version, etc )

After setting it up in the eclipse IDE, I think it should be enough to store..

settings/org.eclipse.jdt.ui.prefs
settings/org.eclipse.jdt.core.prefs

..somewhere in git so that eclipse users can just overwrite their default config files with those from Terasology. This would automatically setup eclipse for Terasology code style, javadoc settings, java version, etc.

[Cervator]

Maybe customizing the eclipse block in Gradle would allow us to generate those files with appropriate values? Rather than keep them in the repository. This is another spot where IntelliJ is heavily customized that way.

http://www.gradle.org/docs/current/userguide/eclipse_plugin.html

[mkienenb]

A partial step toward a solution -- the creation of a reasonable code template file -- is located here:

MovingBlocks#783 (comment)

[Cervator]

I was just about to post a few open items myself related to Eclipse - this is probably close enough to cover some of it :D

• gradlew clean doesn't clean the engine/bin dir generated by Eclipse
• the .settings dir itself doesn't get deleted, just emptied, by gradlew cleanEclipse
• alternatively should eclipse also compile to build/classes? or would that IDE-clash?
• exclude Eclipse files better within IntelliJ (the bin dirs in various places etc - in the root build.gradle idea {} )
• Eclipse code formatting options / tabs vs. spaces etc

[msteiger]

Oh noes! I have a set of config files for eclipse, too. It contains indentation, code formatting, templates, etc. similar to the file @mkienenb posted. Code style and code templates (which contain file header comments) can also be exported as xml files, so that other people can import them. This might be a cleaner solution than using the "compiled" prefs files from the /.settings directly. But again, I'm good with either way.

Maybe @mkienenb can put the xmls in the config/eclipse folder? I can then diff with my version and discuss it with you..

• Eclipse output path can and probably should be changed. The gradle config explains how

[mkienenb]

That gradle config web site hints that we might also be able to read the xml file and create the correct settings file. It's unclear if the specific file we need to create is implemented, but the general pieces for reading the xml file and generating a .settings property file seem to be in place.