Build with Tycho 2.7.4 #1113
Merged
Build with Tycho 2.7.4 #1113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #1113 +/- ##
=========================================
Coverage 33.21% 33.21%
Complexity 356 356
=========================================
Files 1161 1161
Lines 25700 25700
Branches 1589 1589
=========================================
Hits 8535 8535
+ Misses 16660 16659 -1
- Partials 505 506 +1
Continue to review full report at Codecov.
|
|
@ruspl-afed can you please review this PR? |
|
@HannesWell Alexander is on vacation |
ruspl-afed
approved these changes
Jul 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The today released version 2.7.4 of Tycho is shipped with embedded M2E lifecycle-mapping-metadata.
This makes the
org.sonatype.tycho.m2eM2E-connector obsolete and allows to remove it from Passage's Oomph setup. That connector is incompatible with the upcoming M2E 2.0 release (and likely won't be adjusted).