It is kind of embarassing that we took that long to apply the patch. The bug in the code is so obvious. From reading the issue subject I thought the underlying issue is much more complex. Therefore I have postponed it. Apologies for this late fix. I had nonetheless a closer at the underlying mechanisms. And even with this fix things do not work perfectly (e.g. project dependencies which do not belong to the default configuration). For 0.6 we have a clear plan how we can make the handling of project dependencies less enigmatic and more powerful. Another aspect of this is to define which tasks should be executed when building a project dependency.