Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344435 - Renaming project does not change the project ID
Summary: Renaming project does not change the project ID
Status: CLOSED INVALID
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: 0.9.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.0   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-02 07:19 EDT by Alexandra Schladebeck CLA
Modified: 2011-05-02 07:33 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandra Schladebeck CLA 2011-05-02 07:19:47 EDT
If you change the name of a project in the "General" project properties, then the GUID for the project does not get changed. 

1. Import a project into the database and change its name in the properties.
 - In the open project dialog, the old name is no longer available as a project to open
2. Try to import the same project into the database

The message given is that the project with the name n already exists. This is confusing - the project with that name doesn't exist, but the GUID does. 

I'm not sure that we would want to change the GUID for a project when we rename it (as the GUID gets used for referencing this project in other projects). However, the current behaviour is quite confusing from a user perspective.
Comment 1 Achim Loerke CLA 2011-05-02 07:33:31 EDT
(In reply to comment #0)
> 
> I'm not sure that we would want to change the GUID for a project when we rename
> it (as the GUID gets used for referencing this project in other projects).

When this feature was realized we decided to make the GUID the one and only identifier for a project. If one renames the project no harm is done if this was a mistake. If the GUID would be changed too, all references would be destroyed.

> However, the current behaviour is quite confusing from a user perspective.

With the above said, the project still is in the DB but with another (irrelevant) name.