Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348727

Summary: [Project Explorer] Naming error with profile and onefile feature
Product: [Modeling] Papyrus Reporter: Sébastien Gérard <sebastien.gerard>
Component: ViewsAssignee: Mathieu Velten <mathieu.velten>
Status: CLOSED INVALID QA Contact:
Severity: trivial    
Priority: P3 CC: cletavernier
Version: 0.8.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Sébastien Gérard CLA 2011-06-08 09:20:22 EDT
When creating a profile model, the name of the folder when using the "onefile" mode of the project explorer should be modified. If I create a profile called MyProfile, the created files are MyProfile.profile.uml, MyProfile.profile.di and MyProfile.profile.notation. The resulting folder name grouping these aforementioned files is currently MyProfile.profile, wherease it would be better to name it MyProfile. In that case, the other actions on the folder (e.g. rename, delete, copy, ...) should be checked.
Comment 1 Ansgar Radermacher CLA 2013-03-18 09:57:37 EDT
Same bug as in 318147

*** This bug has been marked as a duplicate of bug 318147 ***
Comment 2 Ansgar Radermacher CLA 2013-03-18 10:08:15 EDT
Sorry, I accidentally marked this bug as duplicate of 318147.
I don't agree that the ProjectExplorer should hide a part of the model name. There are files like MyModel.library.[uml|notation|di] or the user might name it My.great.model.[uml|notation|di] and the user might get confused if he only sees a part of the filename compared to the other views or the contents of the file system. In addition, the user might override the naming proposal for profiles via save-as. Thus, I propose to mark this bug as invalid.
Comment 3 Sébastien Gérard CLA 2014-03-26 05:09:03 EDT
ok for me.