Community
Participate
Working Groups
In some cases, projects have opted to host their subproject source code repositories inside the parent project repository. The rap.incubator project's CVS directory, for example, is contained within the rap project's CVS directory (the incubator has a different UNIX group/permissions, so this should be okay from a intellectual property standpoint). When Dash runs on the RAP project's directory, it rolls up all the info from the rap.incubator project's information. At least that's what I'm observing. The rap.incubator project does not declare an SCM URL, so I can't be sure if any pruning occurs. We either need to forbid this sort of thing, or make Dash smarter.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
WONTFIX for Dash. The Git processor that we use for charts and other statistics matches repositories to the project closest to the leaf. If, e.g., a container project claims repositories that belong to the subprojects, those repositories are assumed to be directly owned by the subprojects. For container and parent projects, we now automatically roll up repositories from subprojects for charts and stuff. So, commits, committer, and company involvement charts all display a roll up of data from the subprojects.