You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[MENFORCER-466] RequireUpperBoundDeps fails on provided dependencies since 3.2.1 #828
In particular, ResolveUtils.resolveTransitiveDependencies() will by default (that is, if no other set of exclusions is provided) use the same set of DependencyExclusions as present in MavenRepositorySystemUtils.newSession():
There is the same as in DependencyConvergence - standard ScopeDependencySelector filter dependencies at level >= 2, we need also filter direct dependencies
And BannedDependencies (there might be a problem with an integration test there if we should also ignore {}test-{}scoped dependencies there - an integration test called MENFORCER-434 actually expects the plugin to ban a test dependency).
If we have those two answered -- and especially this: should we ignore test and provided dependencies on all levels for BannedDependencies - then we can have the same selectors everywhere.
Ok, for the time being I have created a new PR for RequireUpperBoundDeps only -- #254
It's not clear to me whether direct dependencies need to be considered for other rules. It's also not mentioned in the docs -- so, leaving them as they are.
In any case, I think those other rules can be tackled in separate tickets.
Activity
jira-importer commentedon Feb 4, 2023
Andrzej J. commented
I guess I must've misunderstood Sławek's comment.
jira-importer commentedon Feb 4, 2023
Piotr Zygielo commented
MENFORCER-402
jira-importer commentedon Feb 4, 2023
Andrzej J. commented
Yup, I'm preparing a PR.
In particular, ResolveUtils.resolveTransitiveDependencies() will by default (that is, if no other set of exclusions is provided) use the same set of DependencyExclusions as present in MavenRepositorySystemUtils.newSession():
jira-importer commentedon Feb 4, 2023
Andrzej J. commented
#248
jira-importer commentedon Mar 11, 2023
Slawomir Jaranowski commented
We have the same configuration from Maven ... do last change must be verified again
jira-importer commentedon Mar 11, 2023
Andrzej J. commented
I don't follow. Should we introduce some more changes?
jira-importer commentedon Mar 11, 2023
Slawomir Jaranowski commented
There is the same as in
DependencyConvergence- standardScopeDependencySelectorfilter dependencies at level >= 2, we need also filter direct dependenciesjira-importer commentedon Mar 12, 2023
Andrzej J. commented
What about RequireReleaseDeps?
And BannedDependencies (there might be a problem with an integration test there if we should also ignore {}test-{}scoped dependencies there - an integration test called MENFORCER-434 actually expects the plugin to ban a test dependency).
If we have those two answered -- and especially this: should we ignore test and provided dependencies on all levels for BannedDependencies - then we can have the same selectors everywhere.
jira-importer commentedon Mar 15, 2023
Slawomir Jaranowski commented
We have more options with rules which use dependencies collections (tree) and we should think if is used correctly
jira-importer commentedon Mar 16, 2023
Andrzej J. commented
Ok, for the time being I have created a new PR for RequireUpperBoundDeps only -- #254
It's not clear to me whether direct dependencies need to be considered for other rules. It's also not mentioned in the docs -- so, leaving them as they are.
In any case, I think those other rules can be tackled in separate tickets.
jira-importer commentedon Mar 17, 2023
Slawomir Jaranowski commented
Yes exactly other rules should be discussed on separate issue.
I only sumarize her.
jira-importer commentedon Mar 17, 2023
Slawomir Jaranowski commented
With implementation IT was added - should be ok now.