Changes between Version 12 and Version 13 of EclipseInterface

Timestamp:

Apr 21, 2015, 12:03:55 AM (10 years ago)

Author:

manualwiki

Comment:

--

EclipseInterface

@@ -17 +17 @@
 While not required, it's recommended to install [http://www.erlide.org the Erlide plugin] in Eclipse. Erlide enhances features of the !RefactorErl plugin and transforms Eclipse into a complete Erlang IDE.
 
-A short list of frequently experienced problems relating to the installation can be found in the [#troubleshooting troubleshooting] section.
+A short list of frequently experienced problems relating to the installation and usage can be found in the [#troubleshooting troubleshooting] section.
 
 [=#install]
@@ -28 +28 @@
 [=#instdep]
 == Dependencies
-* GNU/Linux, or Windows (with MinGW-W64) operating system. (Mac OSX was not tested.)
+* GNU/Linux or Windows (with MinGW-W64) operating system. (Mac OSX was not tested.)
 * Java 7 JRE/JDK or newer. (Tested with Oracle and OpenJDK).
 * Eclipse 4.4.0 Luna or newer.
@@ -317 +317 @@
 [=#troubleshooting]
 = Troubleshooting
-This section describes some of the most frequently experienced problems relating to the installation and starting of the plugin. If the proposed solutions aren't working or you have a problem not in this list, feel free to [https://plc.inf.elte.hu/erlang/refactorerl-contact.html contact us.]
+This section describes some of the most frequently experienced problems relating to the installation, starting and usage of the plugin. If the proposed solutions aren't working or you have a problem not in this list, feel free to [https://plc.inf.elte.hu/erlang/refactorerl-contact.html contact us.]
 * **The installation won't finish and shows an error message** - Make sure you have the correct Eclipse version listed in the [#instdep dependencies section].
 * **There is no !RefactorErl menu after the installation** - You need to open the !RefactorErl perspective or the Erlide perspective to access the !RefactorErl menu. 
@@ -325 +325 @@
   1. Try ticking the **Debug mode** button in the **Preferences** window. When you attempt to connect, a console view will appear, where you can check the output of the process. If there is no output, you're likely not supplied the correct path of the !RefactorErl process.
   1. If the process starts, but the connection doesn't, you can try checking the logs. These files are containing the Erlang-formatted communication between the plugin and the !RefactorErl process.
+* **I get error messages when I try to use any of the dependency analysis features** - This is likely caused by using an older version of the !RefactorErl tool. Make sure the path in the **Preferences > !RefactorErl Base Directory** field points to the correct version listed in the [#instdep dependencies section].