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

Exclude secondary source elements by matching rather than subtraction #436

Merged
merged 1 commit into from
Jul 8, 2019

Conversation

ysb33r
Copy link
Member

@ysb33r ysb33r commented Jul 8, 2019

Exclude secondary source elements by matching rather than subtraction (#410)

This is a very subtle issue. When two Filtree instances are subtracted from each other
in order to eliminate a set of files, the base directory of the tree is lost. If this is
in a CopySpec the relative paths will thus also be lost. The solution is to use a matcher
of type PatternFilterable and then to exclude by FileTreeElement.

When using

…asciidoctor#410)

This is a very subtle issue. When two Filtree instances are subtracted from each other
in order to eliminate a set of files, the base directory of the tree is lost. If this is
in a CopySpec the relative paths will thus also be lost. The solution is to use a matcher
of type PatternFilterable and then to exclude by FileTreeElement.

When using
@ysb33r ysb33r added the bug label Jul 8, 2019
@ysb33r ysb33r added this to the 3.0.0 milestone Jul 8, 2019
@ysb33r ysb33r merged commit b517072 into asciidoctor:development-3.x Jul 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant