-
Notifications
You must be signed in to change notification settings - Fork 114
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
org.osgi.service.http: Unable to satisfy dependency #969
Comments
It would be so nice to have warning free builds. After all, a warning is a cry to be fixed. |
Se the current ongoing work here
Because it happens on each project when it gets resolved and for each platform and then maybe when tests are resolved as well, this is similar to another warning you you repeatedly in the logs
|
Can we please either fix these maven warnings or to disable the "quality" gate? |
Feel free to contribute if you want to fix the issue reported here: Anyways these reported here are not "maven" warnings but warnings reported by P2 because the resolution might be incomplete, Tycho just forwards these warnings to the user so they got not lost unnoticed. Beside that the ones that are reported at the build you recently referenced are cause because platform+platform.ui has heavy cyclic dependencies and test might give different results as they do not specify the reactor dependencies directly but only indirect, what might be an issue that one could/should fix, se the message for details about the offending plugins. |
I vote disable quality gate for maven until issue is fixed if ETA not soon
Jörg Kubitz
… Am 12.12.2023 um 16:30 schrieb Andrey Loskutov ***@***.***>:
Can we please either fix these maven warnings or to disable the "quality" gate?
It makes no sense to keep reporting errors that are not caused by PR's on every PR.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
I've checked this code and I'm not qualified to work on that.
I second that. I can't see these errors anymore (for no obvious reason). |
…#969 should be revert if eclipse-platform#969 is fixed
If something is unclear please ask, these warnings won't go away by just ignoring them. This issue and the linked one are about multiple warnings about "Unable to satisfy dependency from org.osgi.service.http 1.2.2.202109301733 to", this is already fixed here: so one should only ever see this warning once per project and as such it should never be any "new" (in comparison to the reference build). |
…platform#969" This reverts commit 5a4d891.
This is now fixed temporarily with eclipse-platform/eclipse.platform.releng.aggregator#1672 and permanently with eclipse-equinox/equinox#403 so #1007 can be reverted. |
…platform#969" This reverts commit 5a4d891.
…platform#969" This reverts commit 5a4d891.
…platform#969" This reverts commit 5a4d891.
…#969 should be revert if eclipse-platform#969 is fixed
The jenkins console log contains 525 times the same warning https://ci.eclipse.org/platform/job/eclipse.platform/job/master/lastBuild/console
Can someone solve that? I also get a similar warning when i start workspace locally
minor: why is it printed so many times?
The text was updated successfully, but these errors were encountered: