Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 378478 - Juno compatibility: Merge component names item is disabled in Component Name Browser
Summary: Juno compatibility: Merge component names item is disabled in Component Name ...
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: UI (show other bugs)
Version: 1.2.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: Juno   Edit
Assignee: Zeb Ford-Reitz CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on: 379573
Blocks:
  Show dependency tree
 
Reported: 2012-05-04 07:37 EDT by Katrin Hofmann CLA
Modified: 2012-06-15 04:44 EDT (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 Katrin Hofmann CLA 2012-05-04 07:37:54 EDT
tested in Eclipse SDK 4.2.0.I20120502-1800 (Juno M7 candidate)

Steps to reproduce:
1. Create two new component names in Component Name Browser
- new names occur as unassigned component names in component name tree
2. select both nodes and right click to open context menu
result: merge component names item is disabled
Comment 1 Oliver Goetz CLA 2012-05-11 05:58:40 EDT
This behavior still occurs using Juno M7 Eclipse for Testers
Comment 2 Zeb Ford-Reitz CLA 2012-05-15 12:00:05 EDT
Not really blocked by bug 379573, but there's an explanation there as to why
this is occurring.
Comment 3 Zeb Ford-Reitz CLA 2012-05-16 02:15:09 EDT
Marking bug 379573 as blocks after all, just to document that they are related. Also, resolving as fixed, since the fix for bug 379573 should also resolve this issue. I'm not 100% sure, but I think that fix is in the latest I-build (I20120515-2200).
Comment 4 Oliver Goetz CLA 2012-05-23 08:22:51 EDT
I am not able to reproduce the described erroneous behavior using EPP Build 20120523-0430-juno-RC1 Eclipse for Testers.
Comment 5 Oliver Goetz CLA 2012-05-23 08:23:19 EDT
Closing due to comment 4.
Comment 6 Alexandra Schladebeck CLA 2012-06-15 04:44:44 EDT
Behaviour also correct on 1.2.1 release.