There's a bunch of sane defaults in BND. Based on that error, it sounds like your OSGi framework isn't exposing all the runtime packages it should be. You can add packages for the framework to provide by adding them to the org.osgi.framework.system.packages.extra system property.
What are you asking for in the jar/manifest version of your build? ~~ Robert. On 20 August 2010 21:49, phil swenson <[email protected]> wrote: > I'm using the osgi plugin to create a jar equivalent to what our > "production" build creates. Using the osgi plugin ends up with a > manifest that has much more stuff in it that I expect. I assume the > BND tool resolves a bunch of stuff that we don't know about as our > production build manifest is handcoded? This make sense? > > Anyway, when I try to install the OSGi bundle I get this: > > osgi> start 148 > org.osgi.framework.BundleException: The bundle could not be resolved. > Reason: Missing Constraint: I > mport-Package: com.sun.jndi.ldap; version="0.0.0" > at > org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle. > java:1313) > at > org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(Ab > > > any thoughts on where I can find the com.sun.jndi.ldap bundle (it's > not in our repo) > > and why the manifest is much bigger than what I ask for in the > jar/manifest section of the build? > > thanks > phil > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
