please file Jira issues for this if they are not already there (vote for them in that case). That helps more then just posting here.
I will do that.. but I was waiting some feedback.. to know that are not only my problems.
The issue is discussed in this closed jira issue:
It seems that the participants thought that everything would be OK while it is not (at least not in 3.2.6.SP1).
This is actually not really a GPD issue but an issue with the runtime. The runtime publishes information (contained in the version.info.xml file and some other locations) on which the GPD relies to create the project and the sample files.
The problem is that this file was moved and that the info was not kept up to date by Thomas at the moment when he restructured the project and it's build.
So far the explanation. As for the solution, I can build one hundred new GPD releases but as long as these are going to be used with the flawed runtime release the problem is goint to persist. So either the runtime needs to be patched per the described procedure or the GPD has to be used with a runtime release that publishes the correct information. If you guys know of any runtime that produces the flaw please report it in JIRA with the correct versioning information.