Spray projects in one workspace mess each other up

[GoogleCodeExporter]

I updated Spray last week from here 
https://spray.ci.cloudbees.com/job/spray-assembly-build/lastSuccessfulBuild/arti
fact/releng/org.eclipselabs.spray.updatesite/target/repository/

My previous version dated back to September 2012. After I fixed some syntax 
problems (You really need to update the user documentation) the following thing 
happened.

What steps will reproduce the problem?
1. I have a spray project a.b.c.mydiagram based on a.b.c.mydiagram.model
2. I create a second spray project in the same workspace 
a.b.c.mydiagram_newSpray based on the same model
3. In the first project a.b.c.mydiagram I make some change in mydiagram.spray 
and code is generated again.

What is the expected output? 
I expect small cosmetic changes to the source files

What do you see instead?
all files are generated under the package a.b.c.mydiagram_newSpray (still in 
the correct project). And ofcourse all old files from a.b.c.mydiagram are 
removed.

If I create yet another project with some other name, and change the first 
project, the naming of the third project is used.

What version of the product are you using? On what operating system?
I am using Eclipse Juno x64 with Graphiti 0.10 and Spray updated last Tuesday 
the 12th Feb. on Windows 7 Pro x64

Please provide any additional information below.

Original issue reported on code.google.com by NikMano...@gmail.com on 17 Feb 2013 at 9:30

[GoogleCodeExporter]

Please note that we did some changes how configuration is loaded and applied. 
So configuration is now expected to be in a file named spray.properties, this 
file was named differently before. That spray.properties is created when 
creating a new Spray project. So when you open your the spray file of your old 
project with the Spray editor of the current version an empty spray.properties 
file is generated as fall back. The empty spray.properties file is causing this 
strange behavior. This shall be handled. As work around you have to copy the 
content of the old properties file into the new one.

Original comment by de.abg.r...@gmail.com on 19 Feb 2013 at 7:31

[GoogleCodeExporter]

Original comment by de.abg.r...@gmail.com on 19 Feb 2013 at 7:34

• Changed state: Accepted

[GoogleCodeExporter]

The user documentation contains now a section "migration notes" that list 
breaking changes, like this one:
https://spray.ci.cloudbees.com/job/spray-docs-build/lastSuccessfulBuild/artifact
/docs/org.eclipselabs.spray.doc.user/docs/html/SprayUserGuide.html#Renamedproper
tiesfile

So no further effort for doing some magic stuff to upgrade old Spray projects 
automatically.

Original comment by de.abg.r...@gmail.com on 20 May 2013 at 1:18

• Changed state: Done