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

[SUREFIRE-2150] upgrade to parent pom 39 #614

Merged
merged 5 commits into from
Feb 27, 2023
Merged

[SUREFIRE-2150] upgrade to parent pom 39 #614

merged 5 commits into from
Feb 27, 2023

Conversation

olamy
Copy link
Member

@olamy olamy commented Feb 13, 2023

Signed-off-by: Olivier Lamy [email protected]

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

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.

Copy link
Member

@michael-o michael-o left a comment

Choose a reason for hiding this comment

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

This produces now the same issue as everywhere else: License header is duplicated. You need to remove the old license comment. I used sed(1) to cut out those lines combined with find(1).

@olamy olamy marked this pull request as draft February 13, 2023 09:13
@olamy
Copy link
Member Author

olamy commented Feb 13, 2023

yup sorry I didn't create this as a draft but it's still WIP

@slawekjaranowski
Copy link
Member

@olamy - I can finish it, do you want to work on it

@olamy
Copy link
Member Author

olamy commented Feb 25, 2023

Oh yes I can finish that. I was on it this morning but had to go to the beach. I will resume work tomorrow

@slawekjaranowski
Copy link
Member

I'm starting work on SUREFIRE-2154, so I want to avoid feature merge conflicts I will do it.
Have a rest on beach.

@olamy
Copy link
Member Author

olamy commented Feb 25, 2023

I have stuff already done locally!!

@slawekjaranowski
Copy link
Member

I will wait for you - sorry for mess.

@olamy olamy marked this pull request as ready for review February 26, 2023 05:01
@olamy olamy merged commit 052ce53 into master Feb 27, 2023
@olamy olamy deleted the parent-39 branch February 27, 2023 02:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants