[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orbit-dev] Fw: Reason for build failed ... now us?
|
Hi David,
2011/12/14 David M Williams <david_williams@xxxxxxxxxx>:
> I'm assuming this is a "real" build failure now? Needs some fix from us?
> Let me know if you think the "Failed to resolve" check is failing too
> aggressively and I can take it out.
I think it's too aggressive. However, I'm not really sure why it fails
now but did not fail previously.
[orbit-set1] /opt/public/orbit/basebuilders/R37_M7/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.7.0.v20110418/scripts/genericTargets.xml:111:
Processing inclusion from feature
org.eclipse.orbit.build.feature.set1: Bundle
org.slf4j.api_1.5.11.v20100519-1910 failed to resolve.:
[orbit-set1] Host plug-in org.slf4j.impl.StaticLoggerBinder_0.0.0 has
not been found.
SLF4J 1.5.11 has been in the build for a long time and I didn't touch
it that time. I removed an older Logback implementation which might be
a cause. I think the message is mis-leading, though. There is not
really a host plug-in called "org.slf4j.impl.StaticLoggerBinder".
There is a required capability/p2 requirement, though.
SLF4J 1.5 is known to break when no such implementation is available.
We had that issue back in Galileo. I wonder if I should just pull
SLF4J from active builds as well. It's really outdated anyway and now
is IMHO a good time to pull old things so that people can adapt for
M5.
Thoughts?
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/
