Geek Answers Handbook

Eclipse Projects and Branches / Trunks

I already have a repository with a classic structure

/branches /current /beta /tags /1.0 /2.0 /trunk

I would like to switch from my current editor to Eclipse, but how many projects should I create?

  • One for the entire repository?

    But autocomplete will detect multiple entries in the / trunk or / branch / * folders.

  • One in / trunk and one in each / branches / *?

    In this case, how can I keep the hierarchical structure of the repository in my workspace? Is there any other solution than:

    • / workspace / trunk
    • / workspace / beta
    • / workspace / current

Thanks.

+4
source share
2 answers

I propose creating a separate eclipse project for the trunk and each branch.

It was easier for me to merge and tag when the branches are split. In addition, updating one project will take longer than allocated projects, as you will have to check for new tags that you create each time.

One more note: Eclipse is based on Java. Checking the entire code base as a single project will significantly affect the performance of your system. When projects are split, you can simply close branches that you are not working on.

+7
source

@aporat has some good tips, though sometimes switching workspaces is pretty slow. I try to check multiple branches in the same workspace by overriding its name in the te.project file at checkout, usually adding the branch name.

Be sure to close all copies on which you are not actively working, save resources on your workstation.

I use a combination of this approach and having 3-5 workspaces.

0
source

More articles:


All Articles