Both --exclude and --exclude-pattern have behaviors I found strange and wanted to update the readme.
--exclude usage is particularly confusing and should probably be rewritten. It does a string starts with and so doesn't know that /my/path is the same as /my/./path.
I would expect this to work with relative directories and files.
This creates problematic behavior when the path the user provided is .
Current behavior also does stuff that doesn't quite seem right:
Yes though I do not have the project running locally so I have not tested the change to configuration.java (though it looks like it shouldnt cause any issues).
Both --exclude and --exclude-pattern have behaviors I found strange and wanted to update the readme.
--exclude usage is particularly confusing and should probably be rewritten. It does a string starts with and so doesn't know that
/my/path
is the same as/my/./path
.I would expect this to work with relative directories and files.
This creates problematic behavior when the path the user provided is
.
Current behavior also does stuff that doesn't quite seem right: