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

Fixed #488 - Upgrade Maven-4.0.0-beta-4 #489

Merged
merged 1 commit into from
Sep 2, 2024
Merged

Fixed #488 - Upgrade Maven-4.0.0-beta-4 #489

merged 1 commit into from
Sep 2, 2024

Conversation

khmarbaise
Copy link
Owner

@khmarbaise khmarbaise commented Sep 2, 2024

  • Upgraded to Maven 3.9.9

This checklist will help us to incorporate your contribution quickly and easily:

  • Make sure you have read the contributing guide.
  • Make sure there is a issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Name your branch which contains the pull request accordingly with the issue.
    Best is to follow: issue-Number where Number has be replaced with the issue
    number of the appropriate issue you are offering a pull request for.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like Fixed #Nr - Fixed IT execution.,
    where you replace Nr with the appropriate issue number. It is required
    to use the issue title in the commit message title and in the first line of the
    commit message. They should very similar like the following: Fixed #64 - Automatic site publishing
    You can of course take a look into the existing commit history.
  • Make an appropriate entry into the release notes. Follow the examples
    of the existing release notes.
  • 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 via a comment on the appropriate isseu.

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.

 - Upgraded to Maven 3.9.9
Copy link

github-actions bot commented Sep 2, 2024

Unit Test Results

109 tests  ±0   106 ✅ ±0   4s ⏱️ ±0s
 39 suites ±0     3 💤 ±0 
 39 files   ±0     0 ❌ ±0 

Results for commit 7d3f7a9. ± Comparison against base commit 58dfdd4.

Copy link

github-actions bot commented Sep 2, 2024

Integration Test Results

95 tests  ±0   89 ✅ ±0   9m 45s ⏱️ + 1m 32s
62 suites ±0    6 💤 ±0 
62 files   ±0    0 ❌ ±0 

Results for commit 7d3f7a9. ± Comparison against base commit 58dfdd4.

Copy link

github-actions bot commented Sep 2, 2024

Unit Test Results Maven 4.0.0

109 tests  ±0   106 ✅ ±0   4s ⏱️ ±0s
 39 suites ±0     3 💤 ±0 
 39 files   ±0     0 ❌ ±0 

Results for commit 7d3f7a9. ± Comparison against base commit 58dfdd4.

Copy link

github-actions bot commented Sep 2, 2024

Integration Test Results Maven 4.0.0

95 tests  ±0   89 ✅ ±0   12m 23s ⏱️ + 4m 10s
62 suites ±0    6 💤 ±0 
62 files   ±0    0 ❌ ±0 

Results for commit 7d3f7a9. ± Comparison against base commit 58dfdd4.

@khmarbaise khmarbaise merged commit 7d3f7a9 into master Sep 2, 2024
6 checks passed
@khmarbaise khmarbaise deleted the issue-488 branch September 2, 2024 19:10
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.

1 participant