[Build] Update to cbi-plugins 1.5.4#3691
Merged
iloveeclipse merged 1 commit intoMar 1, 2026
Merged
Conversation
HannesWell
force-pushed
the
cbi-plugins-update
branch
from
fe4f1d7 to
38d0452
Compare
Member
Author
|
@iloveeclipse this should fix the current failure of I-builds and verification builds. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It seems like version 1.5.4 of the Eclipse cbi-plugins was released.
At least the snapshot repository is is empty
https://repo.eclipse.org/content/repositories/cbi/org/eclipse/cbi/maven/plugins/eclipse-jarsigner-plugin/1.5.4-SNAPSHOT/
and the release folder is not:
https://repo.eclipse.org/content/repositories/cbi/org/eclipse/cbi/maven/plugins/eclipse-jarsigner-plugin/1.5.4/
But I find it strange that there was no corresponding preparation of the subsequent development cycle in