This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 263453 - Rename issues for module artifacts
Summary: Rename issues for module artifacts
Status: CLOSED FIXED
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Diagrams (show other bugs)
Version: 0.4.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-03 08:19 EST by Richard Craddock CLA
Modified: 2011-12-06 17:50 EST (History)
1 user (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 Richard Craddock CLA 2009-02-03 08:19:49 EST 
If you have the *same* package in a module and in your project, then renaming artifacts form a diagram throws errors.

I think the basic issue is that somehow the rename action is trying to update the containing artifact (not sure why it would need to), and it finds the package that is in the module.... which is read only and has no tsProject.
Comment 1 Navid Mehregani CLA 2011-05-18 15:00:17 EDT 
I wasn't able to reproduce this issue on my end.  Are you still able to reproduce it with the latest TS?