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

chore(#346): rename maven group names for digiwf engine #551

Merged
merged 10 commits into from
Aug 1, 2023

Conversation

lmoesle
Copy link
Contributor

@lmoesle lmoesle commented Jul 27, 2023

Description

Short description or comments

Reference

Issues #346

@codecov
Copy link

codecov bot commented Jul 27, 2023

Codecov Report

Merging #551 (1adc7ad) into dev (2c76798) will not change coverage.
Report is 3 commits behind head on dev.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev     #551   +/-   ##
=========================================
  Coverage     22.54%   22.54%           
  Complexity      934      934           
=========================================
  Files           628      628           
  Lines         10485    10485           
  Branches        715      715           
=========================================
  Hits           2364     2364           
  Misses         7992     7992           
  Partials        129      129           
Flag Coverage Δ
unittests 22.54% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

# Conflicts:
#	digiwf-engine/pom.xml
#	pom-new.xml
#	pom-old.xml
@lmoesle lmoesle merged commit 1cfbc0d into dev Aug 1, 2023
2 of 4 checks passed
@lmoesle lmoesle deleted the chore/rename-maven-group-names-2-engine branch August 1, 2023 13:39
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.

2 participants