Either that or some piece of pax-exam is filter-feeding log messages. I found a way to customize it to just install a framework listener to get the data.
Meanwhile, could you possibly deconfuse me about starting up the shell with java -jar? I assume that I'm missing something pretty minimal. On Thu, Jul 9, 2015 at 9:48 PM, Thomas Watson <tjwat...@us.ibm.com> wrote: > Perhaps the Felix implementation of Bundle.toString displays resolution > results? > > Tom > > > > > > From: Benson Margulies <ben...@basistech.com> > To: Equinox development mailing list <equinox-dev@eclipse.org> > Date: 07/09/2015 06:03 PM > Subject: Re: [equinox-dev] Can I get logging corresponding to 'diag'? > Sent by: equinox-dev-boun...@eclipse.org > ________________________________ > > > > 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 [2] > Unresolved requirement: Import-Package: org.apache.commons.io; > version="[1.4.0,1.4.1)" > > 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 [14]] is > not resolved > > So, I'll be taking this up with them. > > > On Thu, Jul 9, 2015 at 3:49 PM, Benson Margulies <ben...@basistech.com> > wrote: > In an effort to get a clearer picture, I tried: > > java -jar > ~/.m2/repository/org/eclipse/osgi/3.10.0-v20140606-1445/osgi-3.10.0-v20140606-1445.jar > -console > > as per the getting started page, but it just sits there. I am sure this is > density on my part. > > > On Thu, Jul 9, 2015 at 3:01 PM, Benson Margulies <ben...@basistech.com> > wrote: > Tom, > > I can do that. > > Thanks. > > > > On Thu, Jul 9, 2015 at 2:58 PM, Thomas Watson <tjwat...@us.ibm.com> wrote: > 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. > > Tom > > > > > > From: Benson Margulies <ben...@basistech.com> > To: Equinox development mailing list <equinox-dev@eclipse.org> > Date: 07/09/2015 01:46 PM > Subject: Re: [equinox-dev] Can I get logging corresponding to 'diag'? > Sent by: equinox-dev-boun...@eclipse.org > ________________________________ > > > > > > On Thu, Jul 9, 2015 at 2:39 PM, Thomas Watson <tjwat...@us.ibm.com> wrote: > What version of Equinox are you using? Can you give the example of the > error message equinox does give you? > Tom > > I'm embarrassed to report that I've misplaced the log. I can, however, try > to surround the question, as follows. > > > I am using, in Maven terms: > > org.eclipse:osgi:jar:3.10.0-v20140606-1445 > > The problem was the following. > > Bundle 'fred' imports com.basistech.george;version=[34.0.0,35.0.0) > > I stupidly included bundle 'george' with version 35.0.0. > > The error message simply said that 'fred' could not be resolved, and cited a > number in [] brackets. > > Later on I can reconstruct this stupidity by checking out from the right > (wrong) commit and running the build, but perhaps this is helpful? > > In comparison, when I swapped in Felix, I got a lengthy diagnosis that the > problem was the lack of com.basistech.george at the required version. > > > > > > > > > > From: Benson Margulies <ben...@basistech.com> > To: equinox-dev@eclipse.org > Date: 07/09/2015 12:31 PM > Subject: [equinox-dev] Can I get logging corresponding to 'diag'? > Sent by: equinox-dev-boun...@eclipse.org > ________________________________ > > > > 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@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > _______________________________________________ > equinox-dev mailing list > equinox-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev > _______________________________________________ > equinox-dev mailing list > equinox-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > _______________________________________________ > equinox-dev mailing list > equinox-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > _______________________________________________ > equinox-dev mailing list > equinox-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > _______________________________________________ > equinox-dev mailing list > equinox-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev