Bug #1954
File system search depth for components does not work in GitCR
Start date:
25.07.2016
Due date:
% Done:
0%
Estimated time:
origin:
Description
As observed by Victor: Even when setting fscr.checkDepth=-1, the repos (FS and Git) do not recognize nested module structures.
To Do:¶
- Make depth search possible again
Related issues
Updated by Henning Blohm over 7 years ago
- Subject changed from File system search depth for components does not work to File system search depth for components does not work in GitCR, GitCR too inflexible
- Description updated (diff)
Updated by Henning Blohm over 7 years ago
- Subject changed from File system search depth for components does not work in GitCR, GitCR too inflexible to File system search depth for components does not work in GitCR
- Description updated (diff)
Updated by Henning Blohm over 7 years ago
- Related to Improvement #1958: Enhance GitCR for multiple module locations in one repo added
Updated by Henning Blohm almost 7 years ago
- Status changed from In Progress to Rejected
This is actually a misunderstanding, as checkDepth is about the depth for last modification checks.
Module discovery depth does not work this way. We use gitcr.roots for nested, deeply organized repos in Git.