Hi,
On Fri, Nov 2, 2012 at 10:06 AM, Mike Müller mike...@mysign.ch wrote:
...The integration tests now fail, because the SortingServiceTracker could
not be
found in the released version of commons/osgi.
Am I correct, that the only way to correct this is to release Commons OSGi
bundle in
On Fri, Nov 2, 2012 at 10:06 AM, Mike Müller mike...@mysign.ch wrote:
...The integration tests now fail, because the SortingServiceTracker could
not be
found in the released version of commons/osgi.
Am I correct, that the only way to correct this is to release Commons OSGi
bundle in
On Fri, Nov 2, 2012 at 11:21 AM, Mike Müller mike...@mysign.ch wrote:
...Is this the right list.xml which will be used by the integration tests
from installer/it?...
Of course not, but you didn't say you had failures in the *installer*
integration tests ;-)
AFAIK the bundles that the
I haven't followed all the changes, but so far the installer did
inline the classes from OSGi commons. Maybe this new class needs to be
added to be inlined?
Carsten
2012/11/2 Bertrand Delacretaz bdelacre...@apache.org:
On Fri, Nov 2, 2012 at 11:21 AM, Mike Müller mike...@mysign.ch wrote:
...Is
I haven't followed all the changes, but so far the installer did
inline the classes from OSGi commons. Maybe this new class needs to be
added to be inlined?
Carsten
2012/11/2 Bertrand Delacretaz bdelacre...@apache.org:
On Fri, Nov 2, 2012 at 11:21 AM, Mike Müller mike...@mysign.ch
Hi,
as I wrote :) the OSGi commons classes are inlined, therefore there
shouldn't be any need to update the hard-coded version of commons osgi
in the test classes. In fact it shouldn't even be needed.
I've just committed a fix which inlines the new class as well.
Regards
Carsten
2012/11/2 Mike
as I wrote :) the OSGi commons classes are inlined, therefore there
shouldn't be any need to update the hard-coded version of commons osgi
in the test classes. In fact it shouldn't even be needed.
I've just committed a fix which inlines the new class as well.
Regards
Carsten
thanks
