felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Meschberger <fmesc...@gmail.com>
Subject OBR Web Console Plugin (was: trunk/webconsole fails to build)
Date Mon, 22 Mar 2010 08:08:18 GMT

The bundlerepository bundle has been disbanded into the core
bundlerepository stuff and the Manifest parsing stuff moved to the new
commons library/project.

This creates some grieve for downstream users like Web Console but also
other users of the bundlrepository.

As for the Web Console, I think we should move the OBR support plugin
out of the Web Console over to the bundlerepository plugin. This solves
the more general problem of the current bundlerepository refactoring for
the web console (and only for the web console).

The more general problem is that of removing existing API: The old
org.osgi.service.obr API has been replaced in the bundle repository
trunk by the new o.a.felix.bundlerepository API. There may be very good
reasons to do this. But it leeaves current users of the o.o.s.obr API
out in the dark.

WDYT of moving the obr bundle ? In the short term this looks to my like
the only feasible solution to be able to cut a Web Console release soon.

What do we do about the now missing API ? To we provide backwards
compatible wrappers (including an o.o.service.obr.RepositoryAdmin
service) ? Do we simply abandon the old API and raise the bundle
repository bundle to a new major version number ?


On 21.03.2010 04:27, Sahoo wrote:
> This failure is introduced in rev #925279.
> Thanks,
> Sahoo
> Sahoo wrote:
>> Hi,
>> After updating my workspace to svn rev#925708, I am doing a clean
>> build and I see compilation failures like this:
>> /src/main/java/org/apache/felix/webconsole/internal/core/BundlesServlet.java:[904,54]
>> cannot find symbol
>>     [exec] symbol: class R4Package
>> /
>> I don't see any R4Package.class in
>> bundlerepository-1.5.0-SNAPSHOT.jar, that's recently built.
>> Is there a continuous integration job running for trunk? Can I see its
>> log?
>> Thanks,
>> Sahoo

View raw message