Filippo,
As it turns out, the use case I was trying to solve for GF also had
overlapping requirements, so I was forced to loosen up conflict
determination to some degree. I did as I said below, which is to check
if the requirements are identical, if so I allow it, otherwise it is a
conflict and the fragment doesn't attach.
New snapshots of framework and main have been deployed...
-> richard
On 5/3/09 4:06 PM, Richard S. Hall wrote:
On 5/3/09 1:45 PM, Filippo Diotalevi wrote:
If redundant imports (same package, same version range) could be
simply ignored it would be great; but if it's too much work to
implement it now, for me it's not a big problem. The support is
definitely good enough (and specification-compliant, for what I can
understand) to start writing fragments.
Well, it wouldn't be sufficient to just check version range, you need
to check if all attributes were the same.
It depends on how much time I have after doing my other testing. If I
have time, I will look into it more. If I don't, it will have to wait
for the next release.
-> richard
