On Sun, May 3, 2009 at 3:41 PM, Richard S. Hall <he...@ungoverned.org> wrote: > The specification is somewhat vague on what it means for a fragment and host > (or other fragments) to conflict. Initially I have taken a conservative view > of this, so if there is any overlap at all I consider them to be in > conflict. > > It would be possible to loosen this up by allowing overlap if they the have > exact same requirement, for example. You could even go further and try to > see if you can find candidates that resolve overlapping requirements and > only consider them conflicting if you cannot.
I don't know the implementation details, but if the fragment imports a package that is already imported by the host, I would consider it just redundant and not a conflict (maybe a WARNING to explain that the import is not needed). Implementation wise, maybe you can just ignore the redundant import (?). Just noticed that the (infamous, by now ;-) hibernate bundle example has the same problem for exports: f.i. the "org.hibernate.cfg" package is exported by the host bundle and by 2 fragments. Haven't tested this use case yet. Do you think it's complicated to support? -- Filippo Diotalevi
