Skip to content

[MENFORCER-466] Apply the all levels scope and optional selectors on RequireUpperBoundDeps - #254

Merged
slawekjaranowski merged 2 commits into
apache:masterfrom
andrzejj0:MENFORCER-466-provided-optional
Mar 17, 2023
Merged

slawekjaranowski merged 2 commits into
apache:masterfrom
andrzejj0:MENFORCER-466-provided-optional

Conversation

@andrzejj0

Copy link
Copy Markdown
Contributor

Summary

I have corrected the test checking scope provided for require upper bound deps. It wasn't checking anything. I have enhanced the test to check for actual upper deps for both required and optional.

Applied selectors checking for optional and scoped dependencies on all levels (that is, also including direct) for RequireUpperBoundDeps.

ASF rules

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    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.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MENFORCER-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MENFORCER-XXX with the appropriate JIRA issue. Best practice
    is to use the JIRA issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its clean verify).

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.

@andrzejj0
andrzejj0 force-pushed the MENFORCER-466-provided-optional branch 2 times, most recently from b9ea602 to bf5f920 Compare March 16, 2023 07:29
@slawekjaranowski
slawekjaranowski force-pushed the MENFORCER-466-provided-optional branch from bf5f920 to 5d29bda Compare March 17, 2023 19:10
@slawekjaranowski slawekjaranowski changed the title MENFORCER-466: Apply the all levels scope and optional selectors on RequireUpperBoundDeps [MENFORCER-466] Apply the all levels scope and optional selectors on RequireUpperBoundDeps Mar 17, 2023

private List<String> excludes;

private List<String> scopes = Arrays.asList(Artifact.SCOPE_COMPILE, Artifact.SCOPE_RUNTIME, Artifact.SCOPE_SYSTEM);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was a new parameter according to: MENFORCER-470

But ok - I will restore it as exludesScopes

@slawekjaranowski

Copy link
Copy Markdown
Member

rebased 😄

@slawekjaranowski
slawekjaranowski merged commit fb7f749 into apache:master Mar 17, 2023
@slawekjaranowski slawekjaranowski added the bug Something isn't working label Mar 19, 2023
@jira-importer

Copy link
Copy Markdown

Resolve #828

1 similar comment
@jira-importer

Copy link
Copy Markdown

Resolve #828

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

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants