Bug 278771 - Importing project resets Active configuration
Summary: Importing project resets Active configuration
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build-managed (show other bugs)
Version: 6.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
: 349903 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-06-02 09:10 EDT by Jim Adams CLA
Modified: 2020-09-04 15:20 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 Jim Adams CLA 2009-06-02 09:10:03 EDT
Build ID: I20090522-1710

Steps To Reproduce:
1. Create a C/C++ project (debug configuration is set to active configuration by default).
2. Set the release configuration to be active configuration.
3. Delete the project from Workspace (do not delete project contents on disk).
4. Import project back into workspace
5. Check configurations and find active configuration is set to the Debug configuration instead of the Release configuration.


More information:
Comment 1 Andrew Gvozdev CLA 2012-01-25 11:59:50 EST
*** Bug 349903 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Gvozdev CLA 2012-02-12 13:28:37 EST
There is some discussion about that in bug 340219 comment 5 and below. There are good points in there to count "active configuration" to be user preference rather than essential property of a project, and not to be considered during project migration. In particular, it triggers source control to create a new revision of project settings as developers switch active configuration while testing.
What are the arguments in favor of storing this attribute with the project other than it might be expected by some users?
Comment 3 David Pochet CLA 2012-02-13 03:21:19 EST
From our experience, this is clearly not a critical issue, but it can lead to some confusion with new CDT users, pretty not aware of how it works...
Use case:
* users A & B want to share a project (e.g. in SCM)
* user A creates it, works on a given build config (e.g. the "Debug" one), and leaves one or more unchanged (e.g. the "Release" one)
* when newbie user B imports the project, (and even each time a developer will want to setup his development environment, by re-fetching the project from the SCM), it will firstly find a project which doesn't build (because the active build configuration may be Release instead of Debug).

I agree that tuning the project to avoid this is not complicated. Actually it's just a matter of "ease of use".
Comment 4 Marc-André Laperle CLA 2012-02-13 12:39:40 EST
I think there should be a way to define which configuration is the initial active one (Default?) when the project is first opened and that could be persisted in the project. That would set the initial user preference and only the preference would be used after that.