On 8/12/10 16:41, Bobby Bissett wrote:
> On Aug 12, 2010, at 4:34 PM, Richard S. Hall wrote:
>> However, due to a change in error reporting in Felix 3.0.0, this particular error message may be misleading. If you know there is an exporter for the missing package, then the real issue might be something else. You should check the log for Felix resolver errors and see if it is complaining about other missing packages and/or constraint violations. If you don't see anything, try setting Felix' log level to 4.
> Thank you. I'm fairly sure the "missing" package is there and is exported, but maybe the exporting module somehow is failing to load also and thus really isn't exporting it? I'll crank the log to check. What I'm seeing is that A depends on B, and everything works when C is present. But A doesn't find B when C is missing, and I don't see any dependency on C (or any other errors at the current log level).
Right, all of B's dependencies need to be satisfied too or else it
cannot be used to satisfy A's dependency.
We'll, change the log level and check again. If you still can't find
anything, then perhaps you can set me up to reproduce it.
-> richard
> Thanks,
> Bobby
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>