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

[MSHARED-1151] Upgrade parent to version 39 #58

Merged
merged 2 commits into from
Dec 15, 2022

Conversation

psiroky
Copy link
Contributor

@psiroky psiroky commented Dec 8, 2022

The changes are big because of the required reformating (since the new parent brings in new code style via spotless). I did simply run mvn spotless:apply, no manual changes have been made.

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 [MSHARED-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MSHARED-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.

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.

pom.xml Show resolved Hide resolved
.git-blame-ignore-revs Outdated Show resolved Hide resolved
@slawekjaranowski
Copy link
Member

@psiroky - I have just release parent 39, so workarounds will not needed

I will need two final commits in PR - one with upgrade of parent and one with code reformat only

 * versions of both maven-pmd-plugin and taglist-maven-plugin are now
   coming from the parent
@psiroky
Copy link
Contributor Author

psiroky commented Dec 15, 2022

@slawekjaranowski I believe the PR should be ready. There are 2 commits and the build is passing locally. I have also checked the checkstyle report using mvn site -Preporting (looks good - no errors).

@psiroky psiroky changed the title [MSHARED-1151] Upgrade parent to version 38 [MSHARED-1151] Upgrade parent to version 39 Dec 15, 2022
@slawekjaranowski slawekjaranowski merged commit 5ac32c6 into apache:master Dec 15, 2022
@slawekjaranowski
Copy link
Member

@psiroky thanks

@psiroky psiroky deleted the MSHARED-1151 branch December 15, 2022 16:03
@slawekjaranowski slawekjaranowski added the dependencies Pull requests that update a dependency file label May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants