Regarding https://issues.apache.org/jira/browse/KARAF-910 is there anything
Pax URL can do ? Can someone explain how to reproduce it ?
I would imaging some race condition as aether itself is a quite complex
system running in its own little injection container. Would probably give
an upgraded aether a shot..
Any other hints ?

Toni

On Fri, Nov 25, 2011 at 12:31 AM, David Jencks <[email protected]>wrote:

> I enthusiastically applaud any idea of getting a karaf 3 out soon.
>
> I think a lot of the open issues might actually be solved already.
>
> I think that we need to solve KARAF-910 before any release.  I believe
> this is related to pax-url using aether and it being unconfigured during
> most of startup.  When I was working on geronimo I saw in the log that the
> bundle in the karaf repo and local repo were consistently ignored and
> aether would download the bundle from a remote repo first.  Since then I've
> decided to use only startup features in geronimo until this is solved.
>
> Is there a plan to upgrade to jetty 8?  would this be a pax upgrade or
> karaf upgrade?
>
> thanks
> david jencks
>
> On Nov 24, 2011, at 2:31 PM, Guillaume Nodet wrote:
>
> > I think we should start planning a 3.0 release as soon as possible.
> > I have the following big new features in mind:
> >  * regions  (KARAF-1009)
> >  * subshells  (KARAF-647)
> >  * profiles
> >  * test framework (KARAF-1004)
> > Do you guys have anything more in mind or should we start thinking
> > about releasing once those 3 big new features are included ?
> >
> > The JIRA contains more than 90 opened issues for 3.0 and I think we
> > should trim that to whatever we can do in the coming weeks.
> > Having 3.0 released in a few weeks, maybe aim for mid-december would
> > be good imho.
> >
> > Thoughts ?
> >
> > --
> > ------------------------
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> > ------------------------
> > Open Source SOA
> > http://fusesource.com
>
>


-- 
Toni Menzel Source <http://tonimenzel.com>

Reply via email to