I will need consult on this question but I think the main reason was that this is private legacy code of our client in many JARs and a million packages (@Chris: yes, we tried BND on them and it generated 200K manifest files on some of them), from which we use a few only but we wanted to skip the tedious process of mapping their dependencies. I guess the developers were just looking for a way so that they don't have to touch them. :-)
On the question of our issue being caused by a wrong import: our setup works fine in Equinox. We use Pax for testing and that fails with Felix. Also set up a usual Felix installation to try and that refuses to work as well. I know Felix is somewhat more picky on the manifest format (for example, Equinox seems to accept extension=framework while Felix needs ':=' ), so it may be some typo as well. The problem is it does not complain and debug mode doesn't give us anything out of the ordinary either. Will keep investigating. Richard S. Hall wrote: > > > However, it seems this entire approach is incorrect. The primary purpose > of bundles is to share common JAR libraries, so why don't you just > package them as a normal bundle and import them in the client bundles? > > -- View this message in context: http://old.nabble.com/Fragment-bundle-does-not-get-attached-tp28265468p28274419.html Sent from the Apache Felix - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
