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

Make dependency exclusion on classpath configurable #53

Closed
szpak opened this Issue Jan 26, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@szpak
Owner

szpak commented Jan 26, 2017

Currently some kinds of dependencies (namely *.pom, *.so, *.dll, *.dylib as of 1.1.11) are filtered to not to fail during PIT execution (#52). That list could be made configurable if needed.

As there are some implementation issues to handle it in a flexible way please comment here if you need it in your project.

@mdietz198

This comment has been minimized.

mdietz198 commented Oct 20, 2017

Hi, I'm running into this with *.xml files. It would be great to be able to specify extensions.

szpak added a commit that referenced this issue Nov 14, 2017

[#53] More file extensions excluded from classpath
.xml and .orbit - quick workaround.

szpak added a commit that referenced this issue Nov 14, 2017

szpak added a commit that referenced this issue Nov 14, 2017

szpak added a commit that referenced this issue Nov 14, 2017

@szpak szpak closed this in a78e764 Nov 14, 2017

@szpak szpak added this to the 1.2.4 milestone Nov 14, 2017

@szpak

This comment has been minimized.

Owner

szpak commented Nov 14, 2017

I abandon the idea to use regexps in favor of a list of extensions. In 1.2.4 (which is just being released on Travis) it is possible to add extra extensions to filter with:

pitest {
    ...
    fileExtensionsToFilter += ['xml', 'orbit']
}

Do not hesitate to comment here if you encounter any filtering related issue with the new version.

@mdietz198

This comment has been minimized.

mdietz198 commented Nov 15, 2017

Thank you! I will give this a try as soon as I can!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment