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

[MNG-6450] - Allow importing a POM with a classifier #175

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

yborovikov
Copy link

This fixes MNG-6450

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 [MNG-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MNG-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 Core IT successfully. (There's no run-its profile, though...)

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.


assertContains( result.getErrors().get( 0 ),
"'dependencyManagement.dependencies.dependency.classifier' for test:a:pom:cls must be empty" );
assertViolations( result, 0, 0, 0 );

Choose a reason for hiding this comment

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

If this is meant to signify that a violation is not thrown, would it be possible to create a method assertNoViolations( result ) ? Personally I feel as though it parses better.

Copy link
Author

Choose a reason for hiding this comment

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

Hi @KathrynN, thank you for looking at the diff!

The assertViolations( result, 0, 0, 0 ); is used in 5 other test methods in addition to the one I've edited. Changing these would expand the scope of this concise diff to those unrelated test cases - is it, in your opinion, justified?

Choose a reason for hiding this comment

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

Possibly in another story/issue, not here! Maybe mark that refactoring as good for beginners too :)
Thanks for the swift response

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