Create eclipse preference files

Nanoware / Terasology

Terasology is an open source project started by Benjamin "begla" Glatzel to research procedural terrain generation and efficient rendering techniques in Java using the LWJGL. The engine uses a block-based voxel-like approach as seen in Minecraft. After proving itself as a solid tech demo begla was joined at first by Anton "small-jeeper" Kireev and Rasmus "Cervator" Praestholm and a full-fledged game concept was born. Our goal is a game that pays ample tribute to Minecraft in initial look and origin, but stakes out its own niche by adopting the NPC-helper and caretaker feel from such games as Dwarf Fortress and Dungeon Keeper, while striving for added depth and sophistication in the foundation systems akin to DF.

http://terasology.org/

Apache License 2.0

4 stars 1 forks source link

Create eclipse preference files #55

Open msteiger opened 11 years ago

msteiger commented 11 years ago

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 commented 11 years ago

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 commented 10 years ago

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

https://github.com/MovingBlocks/Terasology/pull/783#issuecomment-31279872

Cervator commented 10 years ago

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 commented 10 years ago

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 commented 10 years ago

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.