| << Back to previous view |
|
[QB-194] Non-Recursive Subversion Checkout
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Matthew Inger | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 2 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
It would be helpful to have the ability to do non-recursive subversion checkouts. Our repository is rather large, and our master build script is at the top level. However, we don't need all the submodules checked out for all our applications. We'd like to checkout / non-recursively, and then checkout the other modules we need for building. Right now, we have to checkout the entire tree. |
| Comments |
| Comment by John Allen [ 15/Feb/07 07:45 AM ] |
|
We would also like this functionality, more specifically we would like to be able to use some kind of 'exclude filters' that applied to a configuration prevent either the checkout,or the detection of changes in the repository, for directories/files masked by the 'excludes filters'. To implement the feature described above by Matthew one would simply apply a '**/* style exclude filter. We will use this functionality to exclude any 'child' maven projects which we prefer to build as their own configurations. Thus we could specify something like: <exlcudeDirectories>**/pom.xml</exlcudeDirectories> And not have any subdirectories that include a pom.xml file, no matter how deep they are found included in the svn checkout/status/log. |