On Fri, Dec 4, 2009 at 8:13 AM, Charles Moulliard <cmoulli...@gmail.com> wrote: > I have tested with logging defined as DEBUG or TRACE but no particular info > has been reported in the log. > > For me, that was working before. I tried one of my fragment bundle and it works on 2.0.0 and 2.0.1.
If you provide log information, it may helps to identify the problem. You should see "DEBUG: FRAGMENT WIRE: 86.0 -> hosted by -> 89.0" if it works. Otherwise, you should see something like: DEBUG: Excluding fragment XXX from YYY due to conflict with imported package ZZZ A question for framework developer not related to this mail: do we need log the conflict as ERROR level message instead of DEBUG level? Because when there is conflict happens, it means there are something wrong and user need attention immediately instead of start a debug session. There are a few mail conversation asked about fragment, our response are always turn on debug log and see what happens. -Guo --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
