Perhaps the Felix implementation of Bundle.toString
displays resolution results?
Benson Margulies <benson@xxxxxxxxxxxxx>
mailing list <equinox-dev@xxxxxxxxxxx>
07/09/2015 06:03 PM
Can I get logging corresponding to 'diag'?
I built a test case. What it proves is that there is no
Equinox problem here, there's a pax-exam problem.
When I run Equinox directly from my own code, I get:
org.osgi.framework.BundleException: Could not resolve
module: com.basistech.equinox-logging-demo-problem 
Unresolved requirement: Import-Package: org.apache.commons.io;
which is perfectly fine.
pax-exam manages to obfuscate this to:
1065 [main] ERROR org.ops4j.pax.exam.nat.internal.NativeTestContainer
- Bundle [com.basistech.equinox-logging-demo-problem_0.0.1.SNAPSHOT
] is not resolved
So, I'll be taking this up with them.
On Thu, Jul 9, 2015 at 3:49 PM, Benson Margulies <benson@xxxxxxxxxxxxx>
In an effort to get a clearer picture, I tried:
On Thu, Jul 9, 2015 at 2:58 PM, Thomas Watson <tjwatson@xxxxxxxxxx>
I suggest you open a bug against Equinox
with step you used to launch the framework and install/start the bundles.
I'm still a bit confused by how the errors are being logged.
Clearly a better error message should be getting logged that describes
the unsatisfied requirement.
When I make a mistake in a manifest, and a bundle has unresolvable dependencies,
the error message logged is not detailed. (For comparison purposes, felix
will log the whole story.) The shell command does not help me; the situation
is failing pax-exam tests, and while I could load up in the shell, I'd
rather just get the sad story when the test fails.
equinox-dev mailing list equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev