Skip to content

GH-369: Enforce exact Maven version is used for builds #372

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Mar 4, 2023
Merged

GH-369: Enforce exact Maven version is used for builds #372

merged 1 commit into from
Mar 4, 2023

Conversation

@ascopes
Copy link
Owner

@ascopes ascopes commented Mar 4, 2023

Closes GH-369.

@ascopes ascopes added maven Changes within Maven manifests 👕 tiny labels Mar 4, 2023
@ascopes ascopes self-assigned this Mar 4, 2023
@ascopes ascopes merged commit be53bad into main Mar 4, 2023
@ascopes ascopes deleted the task/GH-369 branch March 4, 2023 14:23
@github-actions
Copy link

github-actions bot commented Mar 4, 2023

Test Results

  1 628 files  ±0    1 628 suites  ±0   0s ⏱️ ±0s
23 540 tests ±0  23 527 ✔️ ±0  13 💤 ±0  0 ❌ ±0 
23 804 runs  ±0  23 791 ✔️ ±0  13 💤 ±0  0 ❌ ±0 

Results for commit 77e60b9. ± Comparison against base commit 20f40ff.

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

Reviewers

No reviews

Assignees

@ascopes ascopes

Labels

maven Changes within Maven manifests

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Enforce minimum coverage for unit tests and integration tests

1 participant

@ascopes