-
Notifications
You must be signed in to change notification settings - Fork 82
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
Include org.eclipse.equinox.slf4j in the repository #2815
Include org.eclipse.equinox.slf4j in the repository #2815
Conversation
I guess the license checker can't find it until it's included:
Otherwise it seems fine. When this is merged, it would be good to kick off a I-build I think. The sooner we check that it's properly published to Maven and properly aggregated into SimRel the better... |
Good question... I think the licence checker do not force update the submodules so it is not "visible" there unless the next ibuild would update it. |
eclipse.platform.releng.tychoeclipsebuilder/eclipse.platform.repository/category.xml
Outdated
Show resolved
Hide resolved
... but not in the product ... This way it can be installed from the site but is not available by default.
1bb21ab
to
264cc3d
Compare
Build triggered here: https://ci.eclipse.org/releng/job/Builds/job/I-build-4.35/125/ |
I have the impression that adding it breaks all verification builds that use api-tools...
|
Is this a problem of the equinox bundle or PDE or p2? With coming M3 and RC builds we should have working API tooling. If that means reverting this PR, I'm for it for M3. |
It looks like a bug in Equinox resolver because it does not correctly wire the double export of the SLF4j bundle. I looked at the slf4j-simple bundle and they just use 2.0 as lower bounds, I'll try the same with the equinox provider now. Another difference is that they have no uses constraint on the capability even though this problematic as it allows things to be wired to incompatible providers. |
Didn't resolved the issue, completely, looks like
is what actually make it fail now, I'll check whats the problem here... |
Interestingly, I was able to install this bundle into latest SDK build, also osgi bundle has the right version. |
The problem is that Tycho currently uses an "older" version and for obivous reasosn one can't replace the framework itself, I now replaced it with import package here: |
Looks like everything is working again! |
... but not in the product ...
This way it can be installed from the site but is not available by default.