Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332220 - [compare] Model compare/sync does not work for non-leaf logical/hierarchical package
Summary: [compare] Model compare/sync does not work for non-leaf logical/hierarchical ...
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 205035 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-12-09 11:20 EST by kurt CLA
Modified: 2020-04-11 03:38 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kurt CLA 2010-12-09 11:20:51 EST 
Build Identifier: M20100909-0800

Selecting a package with no files, sub-packages only, in package-explorer, with hierarchical view activated, brings no result ("No changes in 'CVS Compare...") although there are changed files in sub-packages.
Then doing a compare from source-folder or project-folder brings the expected diffs.


Reproducible: Always

Steps to Reproduce:
1. activate hierarchical view in package-explorer
2. select a package with no files, only sub-packages (where the "diff-files" are)
3. do a cvs-compare with ... (latest from HEAD, or any version you know there should be diffs)
4. compare tells you that there are no changes
Comment 1 kurt CLA 2010-12-09 11:22:47 EST 
version 3.4 has the same problem
Comment 2 Olivier Thomann CLA 2010-12-09 11:30:01 EST 
Moving to JDT/UI. Might be a Eclipse Platform CVS issue.
Comment 3 Dani Megert CLA 2010-12-14 08:10:16 EST 
*** Bug 205035 has been marked as a duplicate of this bug. ***
Comment 4 Eclipse Genie CLA 2020-04-11 03:38:37 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.