Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 379122 - Juno compatibility: Object Mapping Editor: Rename of Component Names not implemented
Summary: Juno compatibility: Object Mapping Editor: Rename of Component Names not impl...
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: 1.2.0   Edit
Hardware: PC Windows Server 2008
: P3 major (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-10 09:53 EDT by Katrin Hofmann CLA
Modified: 2012-06-15 04:44 EDT (History)
2 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 Katrin Hofmann CLA 2012-05-10 09:53:46 EDT 
Steps to reproduce:
1. Open Object Mapping Editor for any Test Suite with unassigned component names
2. Call Rename (per Shortcut or context menu item) for a component name in unassigned component names view or in assigned names view

result: nothing happens

Hint: It's not a problem of context menu enablement. Renaming works fine in GUIdancer version.

Tested with:
 Eclipse SDK 4.2.0.I20120503-1800	
 Jubula	1.2.1.201204271118
Comment 1 Zeb Ford-Reitz CLA 2012-05-15 11:58:38 EDT 
Not really blocked by bug 379573, but there's an explanation there as to why this is occurring.
Comment 2 Zeb Ford-Reitz CLA 2012-05-21 07:54:17 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 I-builds as of I20120515-2200.
Comment 3 Oliver Goetz CLA 2012-05-23 08:06:34 EDT 
I am not able to reproduce the described erroneous behavior using EPP Build 20120523-0430-juno-RC1 Eclipse for Testers.
Comment 4 Alexandra Schladebeck CLA 2012-06-15 04:44:22 EDT 
Behaviour also correct on 1.2.1 release.