Differences

This shows you the differences between two versions of the page.

--- documents:100825imagej_eclipse_debugging [2011/08/31 12:31] – kota
+++ documents:100825imagej_eclipse_debugging [2016/05/24 12:46] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 Following these instructions does enable you to develop nicely. With these instructions, you could probably understand how to set classpath and how to link other projects as reference.
-For myself, the most difficult configuration has been to set debug and run environment. After some experiences, I found that setting Run/Debug environment is very flexible and there could be many ways to do it: while that is great, too flexible also means that it tends to cause unsuccessful configurations.
+For myself, the most difficult configuration has been to set debug and run environment. After some experiences, I found that setting Run/Debug environment is very flexible and there could be many ways to configure: while flexibility is great, too flexible also means that it tends to cause troubles.
-I expose one of my debug/run setting of ImageJ plugin development in Eclipse. Note that this is not the only way, and also keep in mind that the most important setting is "Arguments".
+I expose one of my debug/run setting of ImageJ plugin development in Eclipse. Note that this is not the only way, and also keep in mind that the most important setting is "Arguments". I have made special emphasis on this configuration.
 Configuration below assumes that the compiled plugin (e.g. jar file) is already copied to the plugin folder of ImageJ or Fiji plugin folder. Automatic copying of compiled jar file to the plugin folder is normally done with Ant, the build.xml file. I do not explain about this here, so please refer to the fore mentioned tutorial links.
@@ Line 69: / Line 69: @@
   * [[http://rsb.info.nih.gov/ij/developer/api/ij/ImageJ.html|ImageJ javadoc ij.ImageJ]]
+**Working Directory**
+Normally, this could be set to the default location, the directory where the project files are. This directory is set by using variable **workspace_loc**, which contains OS absolute path to the workspace where you are now working with. Then **${workspace_loc:<projectname>}** returns path to the pluging project folder.
+I set this folder to **${workspace_loc:imagej}**, a path to the imagej source and compiled files of imagej. I have it in the same workspace as a project (which is cloned via git). By having working directory to this imagej folder, pluigns will be automatically recognized. Alternative of doing so is to set the -Dplugin.dir as explained above.
 ===== JRE tab =====
-{{ :documents:eclipserunconfig:runconfig_jre.png?600 |Run Configuration tab "JRE"}}
+You could choose JRE with different versions in this tab. I normally do not touch this, but if there is any indication that JRE version is causing error, you could test them around by selecting "Alternate JRE" and intentionally set VM to a specific JRE.
+[{{ :documents:eclipserunconfig:runconfig_jre.png?600 |Run Configuration tab "JRE"}}]
 ===== Classpath tab =====
-{{ :documents:eclipserunconfig:runconfig_classpath.png?600 |Run Configuration tab "Classpath"}}
+This sets the java -classpath (or -cp) options. External libraries you set in the project properties "Java Build Path - libraries" will be added to here and in the source tab (see below).
+[{{ :documents:eclipserunconfig:runconfig_classpath.png?600 |Run Configuration tab "Classpath"}}]
 ===== Source tab =====
-{{ :documents:eclipserunconfig:runconfig_source.png?600 |Run Configuration tab "Source"}}
+[{{ :documents:eclipserunconfig:runconfig_source.png?600 |Run Configuration tab "Source"}}]
 ===== Other tabs =====
-There are two more tabs, "Environment" and "Common" tabs. Up to now I have not been advanced enough to to touch the values here, and leaving them as it is has caused no problem.
+There are two more tabs, "Environment" and "Common" tabs. Up to now I have not been advanced enough to touch the values in these tabs, and leaving them as it is has caused no problem.