|Re: How to successfully exclude paths from context? [message #600304 is a reply to message #600294]
||Wed, 30 December 2009 05:10
| Jörg Thönnes
Registered: July 2009
AFAIK this feature just works on file names, not on complete paths.
I.e. in your case just using "gen" should work.
I agree with you that this matching on file / directory names is too simple and should be extended.
We also hit by unwanted updates of generated files, but since their happen inside the normal class
hierarchy, we have no way to exclude them.
I am not sure whether there is already a bug tracking enhancements here, maybe someone of the Mylyn
guys (Steffen?) will answer here.
On 12/30/09 01:19, David M. Karr wrote:
> Occasionally I have to do an "svn update" on projects that weren't
> previously in my task context. As a result, every file touched in the
> update goes into my context. I can understand that, but I've attempted
> to add exclusions so that certain paths won't be automatically added.
> For instance, all of my projects have a "gen" directory which I want to
> completely ignore, with respect to my task context. I tried adding
> "gen/*" to the "Resource Monitoring Exclusions" list, but this appeared
> to have no effect. Files in the "gen" tree still got added to the
> context when I updated a project. I also tried "*/gen/*", but that
> didn't work either (and isn't exactly what I wanted to specify).
Powered by FUDForum
. Page generated in 0.01935 seconds