.releng

automation, application, assembly, and angst

Workspace Workarounds

« Jar Signing Tips
Next: p2: Managing Plugins & Features »

Here are a couple pains and their band-aid solutions, which will hopefully be addressed in Eclipse 4.0.

  1. Currently dealing with multiple projects with the same name (a project from the
    trunk and a branch) is cumbersome because multiple workspaces are needed. [200097#c2]

    In supporting 5 branches of EMF, I’ve found an easy workaround here. Rename the old branch project in your workspace from org.eclipse.emf to org.eclipse.emf_R23. However, doing so changes the .project file. I’d love to see a way for Eclipse to allow the folder name and project name (in .project) to not match for these scenarios.

  2. [N]ested projects, the next major version simply needs to support them. [200097#c2]

    Again, there’s a workaround here but it’s clunky. If you have this structure:

    /cvsroot/org.eclipse.project/plugins/org.eclipse.project.*

    and you want each of those org.eclipse.project.* plugins to be respected as plugin projects but also want to have the whole org.eclipse.project project checked out in one folder, do this:

    1. Check out the /cvsroot/org.eclipse.project project.
    2. Use ‘Import > from existing project‘ to add them to your workspace. Now you get the benefit of both worlds.

    However, the issues here are that:

    1. Refreshing or building one project doesn’t necessarily refresh the other one (use F5 to refresh manually).
    2. Changes to BOTH container and plugin projects appear in the Synchronize view, even though they’re the same physical file on disk (commit one then hit F5 on the other project in the Explorer view).
    3. Navigating around the workspace can be confusing — you might search for a method in a file (CTRL-H), and find the .java file in the container project as well as the plugin project. If you accidentally open the container project version, the JDT editor won’t do CTRL-SPACE completions because as far as Eclipse is concerned, the container project is not a java project and the file is not in a source folder.

workspace_multiples.png

Anyone else have any pains or band-aids to contribute?

Posted March 8th, 2008 by in category: usability, workflow
You can skip to the end and leave a response. Pinging is currently not allowed.

One Response to “Workspace Workarounds”


  1. Antoine Toulm Says:
    March 8th, 2008 at 07:50 pm

    As commented on the bug, see
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=163601

Leave a Reply

You must be logged in using your Eclipse Bugzilla account to post a comment.

Recent Posts

Archives

Categories

Meta