I think I've fixed the issue which was caused by a ClassCirculariityError.
The problem comes from Aries proxy generation using weaving hooks
which were disabled before you switched to small jars.
I've upgraded the aries proxy bundle and I've been able to start the
regions bundle at level 19 without
As I tried to say previously, I made the regions stuff start at a hight
start-level (last in framework) and then everything seems to work on both feilx
and equinox. I still have no idea why starting the regions stuff in the middle
of the startup bundles caused everything to freeze.
thanks
davi
I don't experience any problems with equinox at the moment.
Di you fix those or worked around them ?
On Sat, Dec 3, 2011 at 00:56, David Jencks wrote:
> I still don't know what the problem is, but if you start the regions jar a
> little later (start level 30) it works fine in both felix and equi
I think the problem is not really Gemini would wire against Aries, but
the opposite. If we use small bundles, the blueprint-core will wire
against a bundle and that bundle could very well be the Gemini one.
The aries uber-bundle exports the api, but does not import it, so
there's no risk to have t
On Dec 4, 2011, at 11:59 PM, Guillaume Nodet wrote:
> On Sun, Dec 4, 2011 at 23:39, David Jencks wrote:
>>
>> On Dec 4, 2011, at 11:37 AM, Guillaume Nodet wrote:
>>
>>> I think that would work, but I'm just a bit relunctant because that in
>>> the mean time (until Gemini releases a fix, which
I'll have a look today at the region stuff to see if I can find the problem.
On Sat, Dec 3, 2011 at 00:56, David Jencks wrote:
> I still don't know what the problem is, but if you start the regions jar a
> little later (start level 30) it works fine in both felix and equinox.
>
> I've committed
On Sun, Dec 4, 2011 at 23:39, David Jencks wrote:
>
> On Dec 4, 2011, at 11:37 AM, Guillaume Nodet wrote:
>
>> I think that would work, but I'm just a bit relunctant because that in
>> the mean time (until Gemini releases a fix, which I'm not sure would
>> happen in a short time frame), people won
On Dec 4, 2011, at 11:37 AM, Guillaume Nodet wrote:
> I think that would work, but I'm just a bit relunctant because that in
> the mean time (until Gemini releases a fix, which I'm not sure would
> happen in a short time frame), people won't be able to have a simple
> way to deploy Gemini on Kara
I think that would work, but I'm just a bit relunctant because that in
the mean time (until Gemini releases a fix, which I'm not sure would
happen in a short time frame), people won't be able to have a simple
way to deploy Gemini on Karaf.
What kind of advantages do you see in deploying the small
Hi Guillaume,
I'm not quite sure what you are suggesting. Hopefully we agree :-)
After looking at the gemini blueprint bundles I agree that none of them seem to
export the org.osgi.service.blueprint package. My conclusion is that the
gemini blueprint implementation is not spec compliant and t
I think the overall bundle has been designed to do exactly this and
does (or was at least) exporting the org.osgi.service.blueprint
bundle. However, Gemini does not export it, so having blueprint
bundle importing that package will only tie them to the Aries version
without any possibility to wire
On Dec 3, 2011, at 12:40 AM, Guillaume Nodet wrote:
> On Sat, Dec 3, 2011 at 00:56, David Jencks wrote:
>> I still don't know what the problem is, but if you start the regions jar a
>> little later (start level 30) it works fine in both felix and equinox.
>>
>> I've committed the regions stuff
On Sat, Dec 3, 2011 at 00:56, David Jencks wrote:
> I still don't know what the problem is, but if you start the regions jar a
> little later (start level 30) it works fine in both felix and equinox.
>
> I've committed the regions stuff and also some changes to use the little
> blueprint bundles
I still don't know what the problem is, but if you start the regions jar a
little later (start level 30) it works fine in both felix and equinox.
I've committed the regions stuff and also some changes to use the little
blueprint bundles rather than the all-in-one since using the smaller bundles
I've been cleaning up my regions code in hopes of committing it shortly, and
just pushed the current version to github (https://github.com/djencks/karaf)
(region branch).
After seeing 3 regression tests fail I discovered that karaf won't start under
equinox when the region jar is installed. If
15 matches
Mail list logo
