Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excluded match prevents goal from running when non-excluded match also exists #4

Open
udalrich opened this issue Feb 16, 2017 · 1 comment

Comments

@udalrich
Copy link

I have the watcher set up to not match on auto-save files created by my editor. When I save a file, the editor saves the file (obviously) and then deletes the auto-save file. If I run with mvn -X fizzed-watcher:run, I see output including both Watcher - matches=false and Watcher - matches=true, but then the goals are not run.

It looks like the loop over modified files should break if it finds a positive match, rather than looping over everything and preventing the run if it finds an excluded match.

@cinlloc
Copy link

cinlloc commented Jul 22, 2020

+1
I have the same issue, my editor is IntelliJ.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants