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

Minimize - Excluding a project also excludes its dependencies #420

Merged

Conversation

rpalcolea
Copy link
Contributor

@rpalcolea rpalcolea commented Nov 1, 2018

Hi @johnrengelman ,

This is related to #419. Wonder if it makes sense.

Also, decided to only apply this logic on its own DependencyFilter. So moved common things to AbstractDependencyFilter and now DefaultDependencyFilter and MinimizeDependencyFilter only implement the way it's getting determine if a dependency should be included or not. This way the change doesn't impact existing users of shadow that might not want that with common filtering (not for minimize)

@rpalcolea rpalcolea changed the title Minimize - Minimize - Excluding a project also excludes its dependencies Minimize - Excluding a project also excludes its dependencies Nov 2, 2018
@rpalcolea
Copy link
Contributor Author

Hi @johnrengelman , any chance you could take a look on this one?

@johnrengelman johnrengelman added this to the 5.0.0 milestone Jan 20, 2019
@johnrengelman johnrengelman merged commit 27cfe4d into GradleUp:master Jan 20, 2019
@rpalcolea rpalcolea deleted the minimize-project-excludes-tests branch January 20, 2019 07:04
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

Successfully merging this pull request may close these issues.

2 participants