| 92 | | * If you like to start TRex with full product branding enabled, open the file `trex.product` from the `de.ugoe.cs.swe.trex.ui` plug-in in the ''Product Configuration Editor''. As shown below, click in the ''Overview'' tab on ''Launch the product''. If you are using Eclipse Version 3.3, click on ''Launch the Eclipse Application'' instead. (This automatically selects the minimal set of required plug-ins.) If you are using a runtime JRE prior to 1.6, see the annotation below. |
| 93 | | |
| 94 | | '''Note''': If you are using a runtime JRE prior to version 1.6, you will get an exception error when trying to launch. To circumvent this, you will need to do a few extra steps in order to get things working. First, follow the previous instruction as you would normally do. By clicking on ''Launch a product'', eclipse automatically generates a new run configuration with the name ''trex.product''. Choose ''Open Run Dialog...'' from the ''Run'' menu and select this configuration from the left pane. After this step, in the list box below under the Workspace hierarchy, check all required TRex plug-ins for manually build. Next, click on ''Add required plug-ins''. Locate and uncheck the plug-ins named ''org.eclipse.jdt.compiler.apt'' and ''org.eclipse.jdt.compiler.tool''. Finally, click on ''Validate Plug-ins''. You should now get a notification that no problems were found. You can now confirm the changes by clicking on ''Apply''. |
| | 92 | * If you like to start TRex with full product branding enabled, open the file `trex.product` from the `de.ugoe.cs.swe.trex.ui` plug-in in the ''Product Configuration Editor''. As shown below, click in the ''Overview'' tab on ''Launch the product'' (Eclipse 3.2) or ''Launch the Eclipse Application'' (Eclipse 3.3) respectively. (This automatically selects the minimal set of required plug-ins.) If you are using a runtime JRE prior to 1.6, see the note below. |
| 98 | | * In order to avoid restarting the second incarnation of Eclipse after each change to the TRex sources, you may use ''Debug'' instead of ''Run''/''Launch'' to utilize the hot code replace functionality of Eclipse. (This only works for changes to Java source files, not for changes to XML configuration files. Furthermore, it works only for changing existing method bodies, but not for adding new methods or changing the signature of an existing method.) |
| | 96 | '''Note''': If you are using a runtime JRE prior to version 1.6, you will get an exception when trying to launch. To circumvent this, you will need to do a few extra steps in order to get things working. First, follow the above instruction as you would normally do: By clicking on ''Launch a product'', Eclipse automatically generates a new run configuration with the name ''trex.product''. Choose ''Open Run Dialog...'' from the ''Run'' menu and select this configuration from the left pane. After this step, in the list box below of the the Workspace hierarchy, select all required TRex plug-ins for manually build. Next, click on ''Add required plug-ins''. Locate and deselect the plug-ins named `org.eclipse.jdt.compiler.apt` and `org.eclipse.jdt.compiler.tool`. Finally, click on ''Validate Plug-ins''. You should now get a notification that no problems were found. You can now confirm the changes by clicking on ''Apply''. |
