Refactoring JavaFX Builds & Sources (original) (raw)
Mario Torre neugens.limasoftware at gmail.com
Fri Oct 19 16:30:08 PDT 2012
- Previous message: Refactoring JavaFX Builds & Sources
- Next message: Refactoring JavaFX Builds & Sources
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2012/10/19 Felipe Heidrich <felipe.heidrich at oracle.com>:
Gradle can also spit out Eclipse projects and Idea projects. That is what I use personally. Since eclipse projects are fairly universal any IDE that people may want to hack in can ingest that. (JDeveloper?) This make sense to me http://gradle.org/docs/current/userguide/eclipseplugin.html I like the idea that the source in the repo is IDE neutral. Right now Steve and I make sure the eclipse related files are in good shape, but every time something changes in the repo these files get broken. Btw, I can see Tom adding e(fx)clips behavior to the plugin so I can get all the e(fx)clipse sweetness in my IDE. Felipe
I don't personally like much the idea of keeping around IDE generated projects files in the repository to be honest. I rather prefer if the IDE is smart enough to figure the setup from the tool dedicated to the build (like Eclipse, IDEA and Netbeans do with Maven and C/C++ projects for example).
Cheers, Mario
pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF
IcedRobot: www.icedrobot.org Proud GNU Classpath developer: http://www.classpath.org/ Read About us at: http://planet.classpath.org OpenJDK: http://openjdk.java.net/projects/caciocavallo/
Please, support open standards: http://endsoftpatents.org/
- Previous message: Refactoring JavaFX Builds & Sources
- Next message: Refactoring JavaFX Builds & Sources
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]