yeah, I already did grab myself a copy of it ;)
for the minimal distribution this makes a lot of sense :)
regards, Achim
2013/12/5 Jean-Baptiste Onofré
> Hi Ioannis,
>
> it sounds interesting. I gonna take a look on that.
>
> Regards
> JB
>
>
> On 12/04/2013 09:41 PM, Ioannis Canellos wrote:
Hi Ioannis,
it sounds interesting. I gonna take a look on that.
Regards
JB
On 12/04/2013 09:41 PM, Ioannis Canellos wrote:
For anyone curious on how Karaf without Blueprint would look like,
here is a karaf branch that is free of blueprint:
https://github.com/iocanel/karaf/tree/karaf-light (it'
I'm with David on this one. I would even have no problems if the minimal
distribution would really look like your fork. The only problem is that
forking isn't just the best way to maintain a project :-)
Kind regards,
Andreas
On Wed, Dec 4, 2013 at 10:00 PM, David Jencks wrote:
> Great idea! I
Great idea! I think that scr/ds is better suited to framework service wiring
than blueprint.
thanks
david jencks
On Dec 4, 2013, at 12:48 PM, Hadrian Zbarcea wrote:
> Sounds very interesting. Less is more. I absolutely need to try this :).
>
> Thanks,
> Hadrian
>
> On 12/04/2013 03:41 PM, I
Interesting project, taking a look see :)
--Jamie
On Wed, Dec 4, 2013 at 5:18 PM, Hadrian Zbarcea wrote:
> Sounds very interesting. Less is more. I absolutely need to try this :).
>
> Thanks,
> Hadrian
>
>
> On 12/04/2013 03:41 PM, Ioannis Canellos wrote:
>
>> For anyone curious on how Karaf w
Sounds very interesting. Less is more. I absolutely need to try this :).
Thanks,
Hadrian
On 12/04/2013 03:41 PM, Ioannis Canellos wrote:
For anyone curious on how Karaf without Blueprint would look like,
here is a karaf branch that is free of blueprint:
https://github.com/iocanel/karaf/tree/kar
For anyone curious on how Karaf without Blueprint would look like,
here is a karaf branch that is free of blueprint:
https://github.com/iocanel/karaf/tree/karaf-light (it's a fork of the
karat-2.3.x branch).
It is actually a refactored karaf 2.3.x that removes blueprint from
all modules (yet still
No problem, it's really easy and fast to "re-add" the Java 6 support (I
have just to add a mina-core/sshd dependency).
I do it now.
I sent the update plan on a previous e-mail.
Regards
JB
On 12/04/2013 02:30 PM, Daniel Kulp wrote:
Can we investigate how much effort it would be to re-support
FYI:
for 3.0.0: https://issues.apache.org/jira/browse/KARAF-2601
for 3.1.0: https://issues.apache.org/jira/browse/KARAF-2602
I start on it tonight.
Regards
JB
On 12/04/2013 02:26 PM, Jean-Baptiste Onofré wrote:
OK, for "transition" purpose, I propose the following plan:
1/ Karaf 2.x: Java6,
Can we investigate how much effort it would be to re-support Java6 for 3.0? I
know we (Talend) still have a lot of users using J6 with no plans to change
anytime soon.
If it’s a lot of work or one of the third party libs requires J7, that’s one
thing, but if it’s relatively simple, I’d like
OK, for "transition" purpose, I propose the following plan:
1/ Karaf 2.x: Java6, Java7
2/ Karaf 3.x: Java6, Java7
3/ Karaf 3.1.x: Java7, Java8
I gonna create the Jira and work on it.
Regards
JB
On 12/04/2013 08:55 AM, Achim Nierbeck wrote:
hmm, interesting since Karaf 3 doesn't work with Java
As I said, it's the plan, not the current situation.
We can plan Java 8 full support for Karaf 3.1.0 (or 3.0.x depending of the
impacts).
Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com
- Reply message -
From: "Achim Nierbe
12 matches
Mail list logo
