Argh!
Yes, we probably should have made that configurable. Where were you when
I was asking about throwing an exception on fragment install? ;-)
I guess the short answer is "no, there is no way to change it". You have
two options at this point:
1. Roll your own release that disables the exception (pretty easy to
do, I guess I might actually be able to make this configurable in
trunk and create a new snapshot that will eventually become 1.2.2
and you could use that for the time being).
2. Keep using 1.0.4 until we do another release that makes this
configurable.
I don't see any reason why we couldn't make this configurable, perhaps
someone sees something that I don't. The fact that your apps worked at
all before I guess was just luck, since we ignored fragments altogether
in 1.0.4.
-> richard
Daniel Rubio (OSGI Mailing List) wrote:
I just upgraded to Felix 1.2+ from 1.0.4, only to realize some of my
(library) bundles are fragments.
I'm getting a warning that in 1.2 there is partial support for
fragments, which I of course appreciate. However, the application now
ceases to work since it apparently doesn't import any classes in the
fragment....
Is there some way to get things to work as in 1.0.4 and get the warning ?
I realize full support for fragments may be well down the road, but is
there any plan for a release like 1.0.4 (import class from the
fragment ) and getting a warning ?
Thanks for any information on the subject.
Daniel Rubio
P.S- I realize the simple answer is keep using 1.0.4, but the reason
for my question is because I'm in the process of writing a book (for
Apress on Spring-OSGi) which is using Apache Felix, and some things
are already based on the v.1.0.4 and the upgrade to the newer v.1.2
breaks a few of the apps.
