Difference between revisions of "IDE setup"
(eclipse) |
|||
| Line 1: | Line 1: | ||
==Pre-requisites== | ==Pre-requisites== | ||
| − | Freeplane can be developed in Eclipse, IntelliJ and Netbeans and directly imported from gradle files. Configuration and manifest files needed for debugging are created when gradle build is executed. | + | Freeplane can be developed in Eclipse, IntelliJ and Netbeans and directly imported from gradle files. Configuration and manifest files needed for debugging are created when <code>gradle build</code> is executed. |
| + | |||
| + | If you executed gradle builds for previous Freeplane versions, you should manually delete all <code>MANIFEST.MF</code> files which were generated by build scripts, they are not needed any more. | ||
| + | |||
==Eclipse== | ==Eclipse== | ||
Eclipse can directly import gradle files using buildship plugin. Alternatively eclipse project files can be generated by gradle running command <pre>gradle eclipse</pre> | Eclipse can directly import gradle files using buildship plugin. Alternatively eclipse project files can be generated by gradle running command <pre>gradle eclipse</pre> | ||
| Line 11: | Line 14: | ||
==IntelliJ== | ==IntelliJ== | ||
| + | IntelliJ can directly import gradle files. After the import run configuration directory <code>freeplane_debughelper/idea/runConfigurations</code> containing run configuration files should be copied into directory <code>.idea</code> created by IntelliJ in project root | ||
| + | |||
==Netbeans== | ==Netbeans== | ||
| + | Netbeans can directly import gradle files using its Gradle support plug-in. | ||
| + | Gradle tasks needed for running and debugging from the IDE are defined in <code>freeplane_debughelper/build.gradle</code> | ||
| + | |||
[[Category:Coding]] | [[Category:Coding]] | ||
Revision as of 16:22, 26 August 2018
Contents
Pre-requisites
Freeplane can be developed in Eclipse, IntelliJ and Netbeans and directly imported from gradle files. Configuration and manifest files needed for debugging are created when gradle build is executed.
If you executed gradle builds for previous Freeplane versions, you should manually delete all MANIFEST.MF files which were generated by build scripts, they are not needed any more.
Eclipse
Eclipse can directly import gradle files using buildship plugin. Alternatively eclipse project files can be generated by gradle running command
gradle eclipse
Project freeplane_mac should be only included on Macs.
After direct import project freeplane_root should be removed.
There are eclipse launch configurations for debugging in project freeplane_debughelper. Configuration freeplane_debughelper/eclipse/freeplane.launch is the most useful one, configurations freeplane_debughelper/eclipse/freeplane dist.launch and freeplane_debughelper/eclipse/freeplane dist mac.launch are used to launch binary distributions created by gradle build.
IntelliJ
IntelliJ can directly import gradle files. After the import run configuration directory freeplane_debughelper/idea/runConfigurations containing run configuration files should be copied into directory .idea created by IntelliJ in project root
Netbeans
Netbeans can directly import gradle files using its Gradle support plug-in.
Gradle tasks needed for running and debugging from the IDE are defined in freeplane_debughelper/build.gradle
