Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311713 - switching to another branch does not update nested projects
Summary: switching to another branch does not update nested projects
Status: CLOSED DUPLICATE of bug 392882
Alias: None
Product: Subversive
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Burilo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 287556
  Show dependency tree
 
Reported: 2010-05-05 08:45 EDT by alexander.willhaug CLA
Modified: 2012-11-30 08:47 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alexander.willhaug CLA 2010-05-05 08:45:34 EDT
Build Identifier: 3.4.2

If an eclipse project contains nested projects (say, a maven eclipse project with submodules) and the master project is switched to another branch,
all directories in the subversion working copy are correctly switched (verified by looking at the URLs with TortoiseSVN).

But in the eclipse project explorer the old branch name is shown next to all nested projects. Only the master project has the new branch URL in the project explorer. Restarting eclipse causes the new branch name to be displayed
on all nested projects.
Refreshing the project explorer view does not help.

Reproducible: Always

Steps to Reproduce:
1. Create eclipse project with nested projects (e.g. a maven project with submodules).
2. Switch the master project (e.g. the one at the root of the underlying subversion working copy) from trunk to a branch.
3. Note how the eclipse project explorer shows the branch name only for the master project. Restart eclipse, now the new branch name is shown for the nested projects, too.
Comment 1 Alexander Gurov CLA 2012-11-30 08:47:09 EST
Details about how to handle the situation are here: bug #392882

*** This bug has been marked as a duplicate of bug 392882 ***