make all imports optional for test-services bundle

[Justin Edelson <ju...@justinedelson.com>]

While trying to run the IT I added yesterday for SLING-2136 on a
Sling-based application that used an older bundle set, I ran into a
problem where the test-services bundle depended on some Jackrabbit
APIs and a newer version of exported packages from the POST servlet.

Although I generally thing that
<Import-Package>*;resolution:=optional</Import-Package> is a code
smell, it seems like in this case, it might be appropriate. If certain
test components don't work because they depend upon unavailable
packages, then the tests which use those components fail, but it
doesn't block ALL of the test components.

WDYT?

Justin

Re: make all imports optional for test-services bundle

[Felix Meschberger <fm...@adobe.com>]

Hi,

Am 30.11.2011 um 16:42 schrieb Justin Edelson:

> While trying to run the IT I added yesterday for SLING-2136 on a
> Sling-based application that used an older bundle set, I ran into a
> problem where the test-services bundle depended on some Jackrabbit
> APIs and a newer version of exported packages from the POST servlet.
> 
> Although I generally thing that
> <Import-Package>*;resolution:=optional</Import-Package> is a code
> smell, it seems like in this case, it might be appropriate. If certain
> test components don't work because they depend upon unavailable
> packages, then the tests which use those components fail, but it
> doesn't block ALL of the test components.
> 
> WDYT?

Agreed and we can loosen scrutiny on test-only bundles probably.

Regards
Felix