On 2019-05-14T14:02:27 +0000 "Thomas Watson" <tjwat...@us.ibm.com> wrote:
> I don't recall the blog post, but I would be curious if you find the Equinox > Framework error message more usable. We try to format the generic > requirements into the syntax used for the Import-Package header. For example > if you have two bundles one that exports a package from another and the other > bundle cannot be resolved because of a missing package you would get a > message like this: > > > org.osgi.framework.BundleException: Could not resolve module: z.resolveError > [9] > Unresolved requirement: Import-Package: unresolved.exporter > -> Export-Package: unresolved.exporter; > bundle-symbolic-name="z.unresolved.exporter"; > bundle-version="1.0.0.qualifier"; version="0.0.0" > z.unresolved.exporter [10] > Unresolved requirement: Import-Package: does.not.exist > > Where we indent the chains until we get to a requirement that has no > available candidates. That looks pretty good to my eyes. I'd love to see this same thing in Felix. I might open a ticket... -- Mark Raynsford | http://www.io7m.com
pgpWYymBwRAXN.pgp
Description: OpenPGP digital signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
