I have a problem with M2M 2.0.0 Here are steps to reproduce it:
- Create new workspace (W1), create new project (hello world). Change build target to Release.
- Close M2M
- Create new workspace (W2), copy our “hello world” project in to this workspace.
- Open M2M, selecting W2 as workspace. Import project “hello world” viaFILE->IMPORT->Development Studio->Existing Developer Studio projects.
- Observe that target has changed to Debug by itself.
Same sequence works OK in previous versions of M2M. Problem only happens for project that is application. libraries maintain correct build configuration.
I thought that all the project information is kept local to the project. Something has changed. Either some information is now stored in workspace .metadata or M2M tries to be too smart.
You would probably ask me why do I do that. It is simple. I have large system (27 projects, 26 are libraries, 1 is application). For example, I have to make a release. I would create new workspace, check out all projects from SVN, import them into workspace and rebuild. OK, it is not a big deal to remember to change project type. Except when build system is automated. Our build system for releases automatically checks out code and runs Eclipse in headless mode to produce binary.