| Summary: | Extensive SVN update checks for generated code | ||
|---|---|---|---|
| Product: | [Technology] Subversive | Reporter: | Andrey Loskutov <loskutov> |
| Component: | Core | Assignee: | Alexander Gurov <a.gurov> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.0.2 | ||
| Target Milestone: | 4.6.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 392750 | ||
|
Description
Andrey Loskutov
Yes, there is a reason and the reason is that the one in FileUtility is named poorly. They should serve a different purpose: the one in FileUtility should validate if the resource could be managed by SVN plug-in or not, while the one in SVNUtility should match resource against different ignore conditions (except svn:ignore which is actually managed by an SVN client library). I'm working on refactoring the code now. There is also related tasks like this one - bug 480041 or possibly this one - bug 392750. By the way, you're right, the IResource.CHECK_ANCESTORS flag should be used. Thanks for the fast fix! Going to test it now :-) |