On Thu, Apr 14, 2011 at 2:06 PM, Richard S. Hall <[email protected]>wrote:
> On 4/14/11 13:55, Steele, Richard wrote: > >> If a bundle A declares an optional dependency on package com.example.b >> that >> isn't found, I expect that import to be unresolved. However, if I then >> add >> a bundle (call it B) that exports the package com.example.b, A does not >> get >> wired to B even if I issue a refresh command (though gogo). >> > > First of all, I don't think the resolver is required to satisfy optional > dependencies, but most intuitive implementations probably will. > Are you saying that a package marked as optional might *never* be resolved even if the package is available? I never considered that interpretation of the standard, but when rereading it with that in mind in makes sense. I guess. I think most people would be surprised by that behavior. > Are you specifically refreshing bundle A? If not, then most likely nothing > is being refreshed, since a refresh with no parameters only refreshes > updated or uninstalled bundles. Um, no--and that was my problem. I assumed a refresh without any parameters would refresh everything. In fact, I get no errors from gogo when I do that, so it never dawned on me to refresh a specific bundle. This begs the question, however: assume I install a bundle that many would consider options. Do I then need to know which bundles to refresh or is there some way the runtime can do this for me? Thanks for the very fast response! Rich
