Eclipse

• Debugging problem with eclipse will not start
• Eclipse and Subversion and Tortoise
• Eclipse Workspaces
  • Using Subversion Source Code Control With Eclipse Workspaces and Projects

Tips for using Eclipse

• http://benpryor.com/blog/2006/03/03/top-10-tips-for-new-eclipse-users/
  • 1. Use Code Assist
  • 2. Navigate code with ctrl-click
  • 3. Quickly open classes and resources by name
  • 4. Know keyboard shortcuts - ctrl-shft-f4 - close all editor windows; ctrl-shift-G search for references to highlighted item; ctrol-o outline popup to navigate to method on large class; F4 hierarchy viewer; ctrl-m toggle maximize; ctrl-F11- run last launched configuration
  • 5. Set the heap size - recommend -Xmx1024M
  • 6. Configure Eclipse to use a JDK, not a JRE
  • 7. Use Eclipse Refactoring support and code generation
  • 8. Use multiple workspaces effectively - use -showlocation
  • 9. Use templates
  • 10. Set type filters
• Link - http://aspectprogrammer.org/blogs/adrian/2006/02/tips_for_using.html

Google queries:

• Open multiple copies of eclipse for different workspaces, and show workspace in titlebar:
  • Search: eclipse "-showlocation"
    • NOTE: I discovered this has to be one of the first params in the eclipse.ini. If it is the last item, it doesn't work, eclipse will not show the workspace in the title.
• Find out how to integrate with SVN, Tortoise, and stop getting "directory is locked" and other errors:
  • Search: subclipse
• When exporting to "Runnable Jar File Specification", selecting launch configuration, export destination, then checking into SVN as a project (not as a workspace), when checking the project back out and attempting to export, these settings are not remembered. Try to discover where they are stored.
  • Search: eclipse launch configuration
    • saving a launch configuration into the source so I could commit it to SVN! - http://stackoverflow.com/questions/222093/how-to-run-eclipse-launch-configurations-programmatically
    • Sharing launch configurations -
  • Search: eclipse not accessible due to restriction on required library
    • This error message can be removed by changing a setting inside Eclipse IDE. Use
      • Windows -> Preferences -> Java -> Compiler -> Errors/Warnings
      • (Project) Properties -> Java Compiler -> Errors/Warnings
    • Locate the "Forbidden reference (access rules)" option under "Deprecated and restricted API" section in the dialog box. This option decides how to handle access rules defined inside Eclipse. By default it is set to "Error" which causes Eclipse to complain about references to any restricted classes. Choosing any other option (Warning or Ignore) will remove these error messages.