Subproject selection behaviour [message #1785087] |
Mon, 09 April 2018 10:41 |
Felix Dorner Messages: 392 Registered: December 2015 |
Senior Member |
|
|
I got some time for oomph again :) For capella, I have organized the setup model as follows:
Capella
|
|- Capella Developer
|- Capella Addon Developer
| -Capella Tools Developer
Basically, under "Capella" I define a common target platform, and the subprojects just clone different source code repositories.
Both, the toplevel project and the subprojects define different streams. It seems like the subprojects don't 'inherit' the available streams in the parent, so I have them duplicated. When installing from this model, the developer has to select consistent streams for the toplevel and the subproject, but the toplevel streams only show if one first selects the top project and then deselects the unneeded subprojects. If one selects the subproject directly, the toplevel project doesn't show up in the stream selection part on the bottom. So I arrive at two different states with identical visual tree selection, just with a different selection order. I made a series of screenshots to illustrate:
https://imgur.com/a/iiE9N
The fear is, that a developer will select the subproject only, and thus, won't get the target platform and settings from the toplevel project.
Do you have any ideas on how I could improve this structure?
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04040 seconds