-
Notifications
You must be signed in to change notification settings - Fork 26
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
[MSHARED-1158] make DependencyCollectorBuilder more configurable #28
[MSHARED-1158] make DependencyCollectorBuilder more configurable #28
Conversation
Signed-off-by: Olivier Lamy <olamy@apache.org>
8d42b77
to
a8b40f5
Compare
new DirectScopeDependencySelector( JavaScopes.TEST ), | ||
new DirectScopeDependencySelector( JavaScopes.PROVIDED ), | ||
new OptionalDependencySelector(), | ||
new ExclusionDependencySelector() ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well TBH this empty ExclusionDependencySelector doesn't have any effect. we could simply remove it and the code not will not pass tru to do nothing :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that we build Repository System Session
from scratch here ... can we use prepared session by Maven ... in org.apache.maven.internal.aether.DefaultRepositorySystemSessionFactory#newRepositorySession
It is to investigate ...
src/main/java/org/apache/maven/shared/dependency/graph/DependencyCollectorRequest.java
Show resolved
Hide resolved
Yup but should be part of another change? |
Signed-off-by: Olivier Lamy <olamy@apache.org>
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[MSHARED-XXX] - Fixes bug in ApproximateQuantiles
,where you replace
MSHARED-XXX
with the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean verify
to make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.