Marc Speck wrote
ok, let's walk that path. One state I reached was for example with adding
the following to the pom (besides the dependencies and rep mentioned above):
<Private-Package>
org.apache.abdera,
org.apache.abdera.factory,
org.apache.abdera.i18n.iri,
org.apache.abdera.model,
org.apache.abdera.parser,
org.apache.abdera.util,
org.apache.abdera.writer,
org.apache.abdera.xpath,
org.apache.abdera.filter,
org.apache.abdera.i18n.rfc4646,
org.apache.abdera.i18n.text,
org.apache.abdera.i18n.text.data,
org.apache.abdera.i18n.text.io,
org.apache.abdera.i18n.rfc4646.enums,
org.apache.commons.codec.binary
</Private-Package>
<DynamicImport-Package>*</DynamicImport-Package>
Using <Private-Package>org.apache.abdera.*</Private-Package> was even less
promising.
Thanks for 3. and 4.
Marc
If you want to include whole jars just use <Embed-Dependency>. It's a
lot easier as bnd will create the private package statements for you.
It seems that you have to include the commons codec lib as well. The
embed dependency directive uses the artifact id, so something like
<Embed-Dependency>commons-codec, abdera-foo,abdera-bar</Embed-Dependency>
It might be that you need to include some additional libs.
After running maven, you can have a look at the manifest and see the
required imports. So you'll see what is missing.
HTH
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
