Re: [DISCUSS] Roadmap for 3.0 release

Hi guys, sorry was kinda off-line during the weekend :) yeah I work on a lot of improvements for pax web and I really want to see pax web 2.0 being included in Karaf 3.0. Pax Web 2.0 should contain the following: Support of Jetty 8 Support of Servlet 3.0 (including annotations) Support of JSF 2.

Re: [DISCUSS] Roadmap for 3.0 release

Well, then maybe what we need is a min, regular, full/offline and "learn" distribution? I'm not sure which additional use cases/distributions might be interesting. TBH I've never needed anything else than the regular distribution but if there is need for different types of distributions... why not.

Re: [DISCUSS] Roadmap for 3.0 release

I always find demos and samples a confusing area. On the one hand its really good to supply examples of what you can do, on the other hand it is not fun to get a server bogged down with a lot of stuff you don't want or need. If we can decide that our message is "all non-trivial uses of karaf sh

Re: [DISCUSS] Roadmap for 3.0 release

Apologies for confusion; under assemblies we have apache-karaf and apache-karaf-minimal, with an empty directory for apache-karaf-full. So two distributions that we actually build kits for. So restating my question, will kits under assemblies/apache-karaf contain demos? Cheers, Jamie On Fri, Nov

Re: [DISCUSS] Roadmap for 3.0 release

Something we need to nail down for Karaf 3.0.0 is just which distributions we'll be publishing. In assemblies we have references to standard, full, enterprise, and minimal. As the standard (apache-karaf) does not build with demos included I'll assume that we'll have those in full/enterprise editi

Re: [DISCUSS] Roadmap for 3.0 release

Thanks Guillaume ;) Regards JB On 11/25/2011 04:54 PM, Guillaume Nodet wrote: Just fixed it. On Fri, Nov 25, 2011 at 16:41, Jean-Baptiste Onofré wrote: Hi Lukasz, what do you mean list ? It's certainly due to the renaming of the commands on trunk. Regards JB On 11/25/2011 03:26 PM, Łukas

Re: [DISCUSS] Roadmap for 3.0 release

Just fixed it. On Fri, Nov 25, 2011 at 16:41, Jean-Baptiste Onofré wrote: > Hi Lukasz, > > what do you mean list ? > > It's certainly due to the renaming of the commands on trunk. > > Regards > JB > > On 11/25/2011 03:26 PM, Łukasz Dywicki wrote: >> >> Btw. currently list command on trunk display

Re: [DISCUSS] Roadmap for 3.0 release

Hi Lukasz, what do you mean list ? It's certainly due to the renaming of the commands on trunk. Regards JB On 11/25/2011 03:26 PM, Łukasz Dywicki wrote: Btw. currently list command on trunk displays list of services, shouldn't we list bundles, as it is done currently? Will subshells improve

Re: [DISCUSS] Roadmap for 3.0 release

Btw. currently list command on trunk displays list of services, shouldn't we list bundles, as it is done currently? Will subshells improve this area? Regards, Lukasz > On Friday, November 25, 2011 2:42:05 PM Guillaume Nodet wrote: >> For sure. We depend on a snapshot for now, but I think arie

Re: [DISCUSS] Roadmap for 3.0 release

On Friday, November 25, 2011 2:42:05 PM Guillaume Nodet wrote: > For sure. We depend on a snapshot for now, but I think aries trunk > is in a usable state for us, so we just need a release of that. It's getting much closer, yes. There is a little more work for ARIES-626 and we have to figure

Re: [DISCUSS] Roadmap for 3.0 release

For sure. We depend on a snapshot for now, but I think aries trunk is in a usable state for us, so we just need a release of that. On Fri, Nov 25, 2011 at 14:36, Daniel Kulp wrote: > > Well, we definitely need to get a usable blueprint.   0.4 is not (IMO). > Thus, we'd either need to back down

Re: [DISCUSS] Roadmap for 3.0 release

Well, we definitely need to get a usable blueprint. 0.4 is not (IMO). Thus, we'd either need to back down to 0.3 or work hard to get an updated 0.4.1 out first. Dan On Thursday, November 24, 2011 11:31:24 PM Guillaume Nodet wrote: > I think we should start planning a 3.0 release as soon a

Re: [DISCUSS] Roadmap for 3.0 release

Nothing to add to the Roadmap; I like the plan and the targeted release time (mid dec). My personal plan is finishing the test-framework port this week and start porting the trunks of my largest projects to karaf trunk there after to find any remaining compatibility issues and fix them before the o

Re: [DISCUSS] Roadmap for 3.0 release

Hi Toni, I started to work on it but not yet finished/fixed. I will take a look and eventually update Pax Url. I will keep you posted. Regards JB On 11/25/2011 09:36 AM, Toni Menzel wrote: Regarding https://issues.apache.org/jira/browse/KARAF-910 is there anything Pax URL can do ? Can someon

Re: [DISCUSS] Roadmap for 3.0 release

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

Re: [DISCUSS] Roadmap for 3.0 release

Awesome! Let's start focusing for mid December and see how it goes! -- *Ioannis Canellos* * FuseSource ** Blog: http://iocanel.blogspot.com ** Apache Karaf Committer & PMC Apache Camel Committer Apache ServiceMix

Re: [DISCUSS] Roadmap for 3.0 release

Hi guys, I'm agree with the Guillaume's roadmap. Regarding profiles and sub-shell, I should have something to propose on Tuesday or Wednesday next week (I have something not so bad on my private git branch). I'm going to prepare the "roadmap" on Jira by selecting the issues that we need to

Re: [DISCUSS] Roadmap for 3.0 release

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.

Re: [DISCUSS] Roadmap for 3.0 release

Just to be clear, once we have 3.0.0 out I fully expect to see 3.0.x go into the 6 to 8 week patch roll up schedule we've maintained on 2.1.x and 2.2.x branches. So if we do spot some missed item, bug, or omitted documentation then we can correct it quickly. I know that where ever we cut for 3.0.0

Re: [DISCUSS] Roadmap for 3.0 release

The additional features you're suggesting all sound find. I'd also like to hear from others as to other features we should consider required. As to time lines, I'd like to make sure that we have enough time to review / update the documentation, that includes for the several sub projects that will

[DISCUSS] Roadmap for 3.0 release

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 onc