Re: [PROPOSAL] Apache Karaf runtime releases and roadmap

Hello, To be fair, I am a bit surprised by idea of dropping pax projects, because this is the area where Karaf as a project, have at least slight chance to share workload with other OSGi users. I agree, that pax-exam is burden, and it doesn't fit very well to JUnit 5. I've made an attempt to po

Re: [PROPOSAL] Migrate to GitHub Issues/Actions

I am not entirely happy with github issues as they are vendor specific. However, I also acknowledge that it eases contribution path and reduces troubles with sign ups. As for github actions - I've recently ported own builds and made couple reusable workflows for maven build and release [1] whi

Re: [INFO] main branch has been updated to 4.5.0-SNAPSHOT

I guess we could lift version, other projects (ie. ActiveMQ) aim jakarta in next major version. For them its more of the JMS API change, for us its more of other dependencies. However, it is not entirely clear to me how the osgi specs will go, cause we have there some to follow. I know pax stuff

Re: karaf-4.5.x?

I am reactivating this thread because I just ran into issue with dependency which pulls slf4j 2.0.x API. Given it is already 6 months since last message in this topic, is it right time to start 4.5.x branch? Cheers, Łukasz On 13.01.2023 07:23, Jean-Baptiste Onofré wrote: Hi Robert, It makes

Re: [VOTE] Accept karaf-camel as new Apache Karaf subproject

-1 from my side Given the scope of work and possible improvements I do not see a strong reason to move camel-karaf into karaf-camel hence my veto on the proposal. This vote opens up a dangerous path where Karaf gains more fat and moves into direction of integration product on its own while, til

Re: karaf-4.5.x?

It might depend on compiler behavior. AFAIR Java constants can be written down in class files as a literals which makes it still compatible with Java 8 since bytecode version is set to that version. You can cross check that with decompiler output if you are curious. :-) Cheers, Łukasz On 8.01.

Re: [DISCUSS] Accepting K5 in the Karaf ecosystem

to primary project/use. Best Łukasz Dywicki -- Code-House http://code-house.org > On 7 Oct 2022, at 12:57, Jean-Baptiste Onofré wrote: > > My preference is Apache Karaf Minho. > > What do you think to rename Karaf 4.5.0 with a different name too ? In > order to avoid any confu

Re: [DISCUSS] Accepting K5 in the Karaf ecosystem

hem into K5 without refactoring? I've worked on numerous projects which started at Karaf 2, and have updated progressively to K3, K4. Does K5 represent a roadblock to evolution? On Thu, Oct 6, 2022 at 9:36 AM Łukasz Dywicki wrote: Hello, Looking forward towards donation of it as a subproje

Re: [DISCUSS] Accepting K5 in the Karaf ecosystem

Hello, Looking forward towards donation of it as a subproject with clear name. Tehhnically speaking it is not Karaf 5 since it is not based on earlier principles. Dropping osgi is large change which will confuse existing users. Hence following the ActiveMQ Artemis story we should be clear it is a

Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

I see problem similar to Achim. We still didn't hear anything about solving a community trouble. We definitely do not solve a trouble of ops4j community which probably do not overlap 100% with Karaf. We may be solving some trouble for Karaf community, however we probably ask about shifting even

Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

Hi Jean, hello ops4j participants. Given recent rush hours with log4j issues I can understand some of the concerns. However, looking at practical aspects, these issues were handled as good as they would be at the ASF. Time it took Grzegorz to release updated pax-logging was pretty short. If

Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

I am not sure if concerns about PAX projects are fully justified, simply because they are being released and still worked on. While team of people working on it have shrunk over time, I haven't had any troubles with them for long time. The contribution regulation is not an issue. It does work as

Re: Karaf 5 shell and native

I did have some small attempts turning basic apps into native images and I believe it is very good idea, yet I am not sure if Karaf (or OSGi per say) is ready for that. I am glad you are opening this topic as I am interested in anyone succeeded in making a native image which can keep OSGi seman

Re: [PROPOSAL] Apache Karaf 4.4.0 release

Since there are new things coming into area, maybe we could also include KARAF-7325 in there? Cheers, Łukasz On 3.02.2022 21:45, Jean-Baptiste Onofré wrote: Hi, I will ping you tomorrow about Pax Web 8.0.1 and will help on some issues. +1 to include Pax Web 8.0.1 in Karaf 4.4.0. Regards JB

Re: Simplification for user specific configuration handling in custom assemblies

11 juin 2021 à 10:34, Łukasz Dywicki a écrit : Hey all, I recently been going over few Karaf assemblies I created in past years and I realized that in many cases I had to copy entire configuration shipped by Karaf distribution in order to include a new config in bootstrap process. Quite often my

Re: Simplification for user specific configuration handling in custom assemblies

> > Regards > JB > >> Le 11 juin 2021 à 10:34, Łukasz Dywicki a écrit : >> >> Hey all, >> >> I recently been going over few Karaf assemblies I created in past years >> and I realized that in many cases I had to copy entire configuration >> sh

Simplification for user specific configuration handling in custom assemblies

Hey all, I recently been going over few Karaf assemblies I created in past years and I realized that in many cases I had to copy entire configuration shipped by Karaf distribution in order to include a new config in bootstrap process. Quite often my requirements were quite small, yet I had to crea

Re: Thinking about Karaf 5 modulith runtime

I am quite late for this discussion and haven't watched your ApacheCon talk, hence pardon my points if they're wrong. Reorganizing code base is highly appreciated since karaf source tree grew since 2.x without any major changes in directory structure. Till these days it is confusing to me where "e

Re: Features resolver investigation for 4.3.0 and 4.2.11

http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > > Le jeu. 15 oct. 2020 à 17:28, Łuk

Re: Features resolver investigation for 4.3.0 and 4.2.11

I am not sure if that's feature resolver issue. It is rather related to bundle resolver which determines installation order. As far I remember from my last debugging session in this area bundles are installed in computed "dependency" order. It might be that leaf/1 has no direct dependencies on any

Re: [HEADS UP] Three new features proposal this week

On the resolver thingy. I believe that the main problem we need to address is a format of error messages spit from our code. In quite many cases error takes half of the screen. Failure reason is at the end. Going over spaghetti causation in between is a challenge. Making that readable in a tree f

Re: [UPDATE] Karaf Virtual Meetup preparation

Any updates on this? On 25.04.2020 07:37, Jean-Baptiste Onofre wrote: > Hi everyone, > > Just a quick update to let you know that we will have a call with Achim > on Monday to prepare the Karaf Virtual Meetup scheduled on Thursday. > > I will share the schedule and details on Monday evening both

Re: How to certificate a distribution version

e not digitally signed so only one check you can use there is a checksum against official releases as JB suggested. Cheers, Łukasz Dywicki -- Code-House http://code-house.org > On 22 Jan 2020, at 15:06, leonardchicco wrote: > > Hi, > I have a custom distribution of Karaf, an

Re: [HEADS UP] Preparing Karaf 4.2.6 and 4.3.0.RC1

Does any of these is intended to provide early support for JDK 12? Its quite early for 12, however PLC4X guys for whom I made integration test against "edge" versions. They currently put Karaf integration on hold because of that. If there is anything I can do to help with adoption of Java 12 with

Re: [PROPOSAL] Introduce "static" resolver

My 0.02€. I had an attempt to use static assemblies and had to step back from it. There is very little documentation on how to adjust tooling and example which was pointed earlier does not answer all questions. Second, also important thing, is having a static feature resolution doesn't mean that w

Re: Android

Dear Joern, I think there was no test for this so far. We need to take into consideration few things. First of all Karaf is usually ran against regular JRE/JDK distributions. Second big point is that some extensions might pull things which will not be present on Android. My proposal for you is to

Re: [PROPOSAL] Add spotless to Karaf and subprojects

I'm not entirely sure if style which gets promoted is not too "wide". I love approach as it reduces to bare minimum fights between IDEs and their way of ordering imports and so on and makes PR review process just simpler. Some points for formatter and verbosity of some elements: 1. Two extra tabs

Re: [PROPOSAL] Create karaf-4.2.x branch and move master to 4.3.x supporting R7

I think it would be good to cut 4.1.7 release (I am actually depending on it now). I messed up tooling in few minor releases (.5, and .6) by single commit. After that we could let 4.1.x go into low maintenance mode. My reasoning is that migration between minor releases of Karaf become a problem -

Re: [PROPOSAL] - Stories page on website

> As we discuss on Slack, Did you mean IRC maybe? I haven't noticed that we have any Slack channel. > I pushed a PR about adding a stories page on the > website to talk about Karaf ecosystem : > > https://github.com/fpapon/karaf-site/tree/STORIES > > I made a proposal structure of the page and

Re: issues while using Spring 5.0.4 with latest KARAF 4.2.0

My suggestion out of scope. Shouldn't you have just one Aries Blueprint Spring bundle? > 75 | Active | 80 | 0.6.0 | Apache Aries Blueprint Spring > 76 | Active | 80 | 0.4.0 | Apache Aries Blueprint Spring If you have 0.6.0 and 0.4.0 versions installed in parallel

Re: Karaf-4 : ConfigurationAdmin returns Managed Properties as null

? Kind regards, Łukasz Dywicki -- Code-House http://code-house.org > On 18 Jun 2018, at 23:17, sathish_alwar wrote: > > We are using Karaf-4 (Opendaylight Nitrogen version). > > Our beans implement ManagedService and we register them using blueprint.xml. > We have placed the confi

Re: FYI, OSGi Features RFP

Hey David & Christian & Guilliame & Grzegorze Great to hear that from David, as an insider. It is super cool to have Christian watching things from karaf side. I am sending this reply to share my personal view on the past and hope in future standard. I rely on our features mechanism since its earl

Re: [VOTE] Apache Karaf (Container) 4.1.4 release

+1 (binding) Tested with OH2 build - no issues found. Cheers, Lukasz On 18.12.2017 10:52, Grzegorz Grzybek wrote: > +1 (non-binding) > > regards > Grzegorz Grzybek > > 2017-12-18 10:07 GMT+01:00 Roedl Lukas : > >> +1 (non-binding) >> >> regards, >> Lukas >> >> -Ursprüngliche Nachricht

4.1.4 release in December

ever handled release, despite of having such possibility, I could try to do it and offload „standard” team members handling this task. Cheers, Łukasz Dywicki

Re: [DISCUSS] Living on the edge... of version range

er to do the > downloads. > > 2017-02-01 14:49 GMT+01:00 Łukasz Dywicki : > >> It is fine for me too, but we still need this piece of code embeddable >> in maven build as maven core extension. That's why I didn't opt for >> pax in first place. >> >> Che

Re: [DISCUSS] Living on the edge... of version range

e version resolver >> is >> in pax-url-aether, as it's really the only place it will be used afaik, >> but >> again, it's no big deal. >> >> 2017-02-01 14:14 GMT+01:00 Łukasz Dywicki : >> >>> What I was thinking about was something like t

Re: [DISCUSS] Living on the edge... of version range

ntation is mutable as Grzegorz pointed out. Since we will be in internal package getResources should behave properly in both cases. Cheers, Lukasz 2017-02-01 12:54 GMT+01:00 Guillaume Nodet : > 2017-02-01 12:35 GMT+01:00 Łukasz Dywicki : > >> @Guillaume you are right on findEntries part

Re: [DISCUSS] Living on the edge... of version range

ra.plugin.system.issuetabpanels:comment-tabpanel#comment-37006 > [3]: http://ggrzybek.blogspot.com/2016/10/using-maven-with-osgi-part-3.html > > 2017-02-01 11:44 GMT+01:00 Guillaume Nodet : > >> 2017-02-01 11:31 GMT+01:00 Łukasz Dywicki : >> >> > Thanks for your repi

Re: [DISCUSS] Living on the edge... of version range

ersion range support in > Maven URL, and after in the feature resolver. > > Correct ? > > Regards > JB > > > On 02/01/2017 02:05 AM, Łukasz Dywicki wrote: >> >> Dear receivers, >> I would like to summarize my research and fight to align version range >&

[DISCUSS] Living on the edge... of version range

Dear receivers, I would like to summarize my research and fight to align version range handling in different parts of karaf related projects. As some of you might not know version ranges are working differently depending on context we are working in. In general most of logic stays the same while th

Re: Hawto declare MBean using Blueprint on karaf 3.0.X ?

Dear sekaijin, You are right - 2.3.x and earlier versions of Karaf internally used org.apache.karaf.management.MBeanRegistrer for all JMX related stuff. This class was visible to everyone and could be referenced from user bundles. Starting from 3.x Karaf switched to aries-jmx and uses whiteboard

Re: Discuss: Use DS for karaf bundles

dencymanager/org.apache.felix.dependencymanager.lambda.samples/src/org/apache/felix/dm/lambda/samples/hello <https://github.com/apache/felix/tree/trunk/dependencymanager/org.apache.felix.dependencymanager.lambda.samples/src/org/apache/felix/dm/lambda/samples/hello> Best regards, Łukasz Dywic

Re: Proposal - Lightweight standalone remote OSGi implementation for karaf-cellar

> Wiadomość napisana przez Guillaume Nodet w dniu 22 lut > 2016, o godz. 09:33: > > 2016-02-12 16:42 GMT+01:00 Sascha Vogt >: > >> Hi all, >> >> we (a colleague of mine and myself) started searching for a >> high-performance / lightweight remote OSGi implementat

Re: bnd files in Decanter Project

Since entire thing is going slowly into end I just wanted to clarify one statement from Christian’s earier mail: > Wiadomość napisana przez Christian Schneider w dniu > 16 lut 2016, o godz. 10:29: > > On 16.02.2016 08:46, Guillaume Nodet wrote: >> Fwiw, if I had to do it again from scratch, I

Re: bnd files in Decanter Project

is stage will be repeated. Kind regards, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org > Wiadomość napisana przez Morgan w dniu 13 lut > 2016, o godz. 11:22: > > Hi, > > After discussing with Christian I

Re: Known Karaf users

possible ofc. Just to let people know how widely our project is used. Best regards, Łukasz Dywicki — l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org > Wiadomość napisana przez Achim Nierbeck w dniu 10 > lut 2016, o godz. 11:04: > > Hi S

Re: [VOTE] Promote the new website look'n feel

+2 (binding) Go for it ;-) Cheers, Lukasz > Wiadomość napisana przez Freeman Fang w dniu 15 sty > 2016, o godz. 04:28: > > +1 (binding) > － > Freeman(Yue) Fang > > Red Hat, Inc. > FuseSource is now part of Red Hat > > > >> On Jan 14, 2016, at 1:58 AM, Jean-Baptiste Onofré wro

RPM packaging once again

generated during maven build by rpm-maven-plugin. Is it worth spending time on that? Kind regards, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org

Re: [VOTE] Remove Apache Karaf WebConsole

Hey, Since it’s not maintained and there is now will to continue it it’s the best to shut it down. Keep sources for further generations, but put repository in read only mode. +1 from my side Kind regards, Lukasz > Wiadomość napisana przez Jean-Baptiste Onofré w dniu 24 > sie 2015, o godz. 13

Re: [VOTE] Release Apache Karaf 4.0.1

Good work guys, here you have my: +1 (binding) Cheers, Lukasz > Wiadomość napisana przez Achim Nierbeck w dniu 17 > sie 2015, o godz. 22:46: > > +1 (binding) > > regards, Achim > > 2015-08-17 11:38 GMT+02:00 Christian Schneider : > >> I think a workaround might be to build karaf on your ma

Re: [VOTE] Switch manual (documentation) to asciidoctor

+1 (binding) It looks much better. :-) > Wiadomość napisana przez Freeman Fang w dniu 28 maj > 2015, o godz. 00:12: > > +1 > > Thanks > － > Freeman(Yue) Fang > > Red Hat, Inc. > FuseSource is now part of Red Hat > > > > On 2015-5-28, at 上午4:18, j...@nanthrax.net wrote: > >>

Exploded WAR in 4.0.0-M1

if behavior of it was changed in mean time? Cheers from sunny Oman, Łukasz Dywicki -- l...@code-house.org <mailto:l...@code-house.org> Twitter: ldywicki Blog: http://dywicki.pl <http://dywicki.pl/> Code-House - http://code-house.org <http://code-house.org/>

Re: [VOTE] Create/donate Apache Karaf Decanter subproject

+1 (biding, I guess) 2014-10-16 5:01 GMT+02:00 Freeman Fang : > +1 (binding) > － > Freeman(Yue) Fang > > Red Hat, Inc. > FuseSource is now part of Red Hat > > > > On 2014-10-16, at 上午1:19, Jean-Baptiste Onofré wrote: > > > Hi all, > > > > following the discussion about Karaf Decanter,

Re: [PROPOSAL] Karaf Decanter monitoring

I think that there is project which might have similar scope - sirona. I like general idea but I do not like idea of embedding kibana. Forcing usage of any particular tool is just wrong. It also makes sense to start supporting codehale metrics since early beginning as this library gets more and mor

Re: [Discuss] Release Apache Karaf Webconsole 0.3.0.alpha

Not sure about WC stage, however 0.3.0.alpha will be fine start. Big +1 from me. > Wiadomość napisana przez Jean-Baptiste Onofré w dniu 23 > wrz 2014, o godz. 07:08: > > No problem for me. > > +1 > > Regards > JB > > On 09/22/2014 07:20 PM, Jamie G. wrote: >> Hi All, >> >> Apache Karaf web

Re: The future of the Spring with Fabric8

remains in main development branch for this project I suppose it is somehow supported by project team. Kind regards, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Thomas Diesler w dniu 11 cze 2014, o

Re: [HEADS UP] Region support in Karaf 4.x

. But again, I didn’t try it since a while. If we could push new bundles to subsystems easily without that then it would make sense to integrate with it instead of writing everything from scratch. Kind regards, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-

Fwd: [jira] [Commented] (INFRA-6708) Migrate Karaf (and sub-projects) to git

Seems we finally have git repos! :-) Początek przekazywanej wiadomości: > Od: "Jake Farrell (JIRA)" > Temat: [jira] [Commented] (INFRA-6708) Migrate Karaf (and sub-projects) to git > Data: 16 grudnia 2013 21:33:07 CET > Do: l...@code-house.org > > >[ > https://issues.apache.org/jira/brows

Re: A Blueprint Free Karaf

icated use case, we now have in Karaf, other things should raise smaller issues. On configuration side - declarative services are all about services, so we'll need to register ManagedService instance anyway and handle updaes on our own. Cheers, Łukasz Dywicki -- l...@code-house.org Twitte

Re: A Blueprint Free Karaf

nestly, most of complications we have is hiden in service implementations. That's why I do consider dropping of dependency injection framework. It is something which can be done, it's just matter of balance between cons and pros. Best regards, Łukasz Dywicki -- l...@code-house.org Twi

Re: A Blueprint Free Karaf

n Dec 6, 2013, at 2:05 PM, Łukasz Dywicki wrote: > >> Yes Joed, >> You got the point I wanted to reflect. DS and SCR is still dependency which, >> for sure, may be optional. Switching to poorer replacement from feature rich >> blueprint will bring bigger cost tha

Re: A Blueprint Free Karaf

pic, which install necessary features is very good. It might be used in similar way as deployers or feature resolvers to preprocess bundles before installation to automatically enable certain features. Łukasz Dywicki -- Code-House http://code-house.org Dnia 6 gru 2013 o godz. 21:12 Johan Edstrom

Re: A Blueprint Free Karaf

I am late for this discussion, however will try to put my fingers here. :) I think that doing souch change in Karaf 3.1 will be good steep, since it's too late for closest release. If we would step off blueprint then I do not consider DS or SCR as an alternative to blueprint since it's just anot

Re: Which config.properties and startup.properties with admin:create ?

profiles. That's my 0.02 PLN. ;-) Cheers, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Gert Vanthienen w dniu 25 paź 2013, o godz. 16:14: > Hey Achim and Jean-Baptiste, > > > Ye

Re: [VOTE] Switch from svn to git

Can we finish this vote and move forward to git? :) Cheers, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Christian Müller w dniu 17 lip 2013, o godz. 00:00: > Apache Camel is using Git since a

Re: Suggestion : Pax XML Features file hosted by karaf

*after* 3.0 release. Cheers, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Achim Nierbeck w dniu 17 lip 2013, o godz. 10:59: > Hi guys, > > I'd rather would like to see 3.0 next instead

Re: [VOTE] Switch from svn to git

+1 from me Switching to git will let us process pull requests in easier way. Maven is not afraid of git as well. I'm not scared by Camel issues with git since they have more modules than they need. ;-) Cheers, Lukasz Wiadomość napisana przez Achim Nierbeck w dniu 25 cze 2013, o godz. 11:54

KARAF-1305 and 2.3.x branch

Hey, I just saw an issue related to SMX (SM-2185), and KARAF-1305. I didn't drive deeper into it, however I checked the 2.3.x jetty.xml and it looks that we still point to old principal class name: https://github.com/apache/karaf/blob/karaf-2.3.x/assemblies/apache-karaf/src/main/resources/extra/j

Re: [VOTE] Release Apache Karaf version 3.0.0.RC1

I have mixed feelings about putting my vote here.. but I have to do this: -1 From me Minimal distro have broken instance script, basically it doesn't work. Best regards, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-hous

Re: fuse source repos are down

Andrei, Please do not cross post across user/developer mailing lists with same problem. Can you point which branch you are trying to build and what fails? \o/, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana

Re: [Discuss] Let Hudson comment on jira issues

That's something really good from quality point of view. For webconsole I had local gerrit installation with hudson verifying every commit before moving to trunk. Wiadomość napisana przez Jean-Baptiste Onofré w dniu 11 mar 2013, o godz. 10:25: > Hi Christian, > > Agree with you. > > If the

Re: JAAS Modules that only provide roles (no authentication)

Hey Christian, I am not sure *if* thats really good direction. I haven't seen option like this before in other JAAS module implementations, but I may have limited view for this. A proper way to do that with JAAS is to use control flags like required, sufficient or optional. that's the way how overa

Re: Idea: Allow users to patch feature files

ate integration-pom shared between CXF and Camel to avoid version race. Kind regards, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Daniel Kulp w dniu 26 lut 2013, o godz. 14:21: > > On Feb

Re: Idea: Allow users to patch feature files

should avoid some of problems you pointed. I think in your case you may publish just updated feature file for things you want to have. Cheers, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Chris Geer w

Re: Idea: Allow users to patch feature files

I think the best way for providing bug fixes is having bundle fragments without complicating features mechanism. You may release fragment attached to bundle which must be fixed. Just by using another feature repository. Cheers, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http

Re: [RESULT][VOTE] Apache Karaf EIK 0.9.0 release

Can't we push this together with Karaf site to don't force people download ZIP? Wiadomość napisana przez Jean-Baptiste Onofré w dniu 21 lut 2013, o godz. 15:33: > Hi Timo, > > I've prepared the announce on the website. > > What you can do is to download the EIK Eclipse repository from there:

Re: Karaf with jdk 1.8.0 / jre 1.8.0

Since it's not first issue with changing java version maybe we could consider adding an default entry which will be used when there is no entry in jre.properties. An information could be printed that current version of JVM used is not yet officialy supported. WDYT? Wiadomość napisana przez Sim

Re: release by subsystem

It will not work. ServiceMix had multiple repositories/components/releases and it's always the same - to do gozilla release you still need to do submodules release too. Waiting for submodules takes same amount of time, since in ASF everything should be voted. We have very few dependencies and, i

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

Guillaume, I'll not answer for your points since my statement was clear in previous message. Made the decision what do you want to do with hawt.io, what you want to offer Karaf community and then, simply back. If you have some objections about my previous or current arguments, go ahead. We can

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

Guillaume, If I'll send a mail with announcement about my amazing project, whatever it will be, to apache mailing lists I will be treat a spamer. If I will try doing that with more mailing lists - then I'll be treat as spamer - that's for sure. And that's what have you done. You have something w

Re: [DISCUSS] Switching to Git

I am ok with switching to Git as I already use git-svn for everything. However I think the final decision should be made mainly by these who do releases. Cheers, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana

Re: Nested features using karaf-maven-plugin 3.0.0-SNAPSHOT

Features mechanism in Karaf do not support nested features. It supports only feature dependencies. You can use this to create tree of dependencies. If you install feature which have dependencies then Karaf resolves it's dependencies first. Cheers, Lukasz Dywicki -- l...@code-house.org Twitter:

Re: RFC on proposal to allow hooks into Karaf shutdown

Roman, I don't uderstand why you try to force us to introduce some code necessary for YOUR very custom secnario. As pointed before in this thread, there is plenty of ways to listen for framework shutdown - starting from FrameworkListener up to BundleListener. If you will digg deeper you will fi

Re: Securing shell commands

Wiadomość napisana przez Guillaume Nodet w dniu 12 lis 2012, o godz. 21:09: > On Mon, Nov 12, 2012 at 8:30 PM, Łukasz Dywicki wrote: > >> As far I know you can use JAAS login modules without JVM level security >> manager. It's only metter of creating the login c

Re: [Discuss] Apache Karaf 2.2.10 RC soon?

Gentlemen, It's time to make man decision. Release Karaf 3 or not!? We are sitting too long on K3. Wiadomość napisana przez Jamie G. w dniu 12 lis 2012, o godz. 14:21: > Karaf 3.0.0.RC1 is very close. > > We can do multiple releases of course - I'm sure everyone would like > to see 3.0.0.RC1 as

Re: Securing shell commands

ordering is not easy to write either. > Another option would be to use a url which would point to the xml, or text > base file. But properties are map based with no ordering guarantee. > > > On Mon, Nov 12, 2012 at 1:30 PM, Łukasz Dywicki wrote: > >> I don

Re: Securing shell commands

I don't think that storing XML data inside flat configuration file is something I would like to see in karaf. Nobody will be able to edit that to be honest. Implementation of wildcards/RBAC can be done easily with JAAS LoginModule. So from my point of view it's -1. I see no need for introducing

Re: WebConsole versioning

That's whole plan. To go beyond karaf as runtime and let others adopt console with some other container/server environment. Best regards, Łukasz Dywicki -- Code-House http://code-house.org Dnia 20 sie 2012 o godz. 10:16 Ioannis Canellos napisał(a): > That's interesting. > >

Re: WebConsole versioning

An option around this problem might be to >>> add an additional version behind; e.g. starting with 2.0.0.0 and >>> 3.0.0.0 for the first releases; or in other words >>> KARAF.WC_MAJOR.WC_MINOR.WC_MICRO. >>> >>> WDYT? >>> >>> Kind regar

Re: [DISCUSSION] OSGi core version in Karaf version

We spent one year before releasing 3.x. With this velocity we'll support OSGi 5 in same time as Java will support Jigsaw. IMHO Karaf 4 is too far to plan anything in it, especially that Equinox and Felix will be OSGi 5 compatible in more or less half year, I guess. Best regards, Lukasz Wiadomo

Re: [VOTE] Release Apache Karaf 2.2.9

+1 Tested with webconsole. Wiadomość napisana przez Ioannis Canellos w dniu 17 sie 2012, o godz. 07:12: > +1

WebConsole versioning

Once again I back with WebConsole topic. As we plan to support bot 2.x and 3.x line. Current trunk (0.3.0-SNAPSHOT) of webconsole supports 2.x and I am about to start 3.x branch to get karaf trunk also supported. The problem is that we can not have the same version for both Karaf versions due ch

Re: JIRA, old webconsole & new webconsole collision

sole is a subproject, it should have its own component (like > cellar, cave, etc). > > I can create the components if you want. > > Regards > JB > > On 08/16/2012 11:03 AM, Łukasz Dywicki wrote: >> Hey, >> We have one component in JIRA for both consoles. This

JIRA, old webconsole & new webconsole collision

Hey, We have one component in JIRA for both consoles. This may lead problems in future. Shouldn't we split it for two different eg. felix-webconsole for older console and karaf-webconsole for newer? Also we don't have any version for webconsole in JIRA. Current version in SCM points to 0.3.0-SNA

Change webconsole context path

Hey, I would like ask you (and notify) about change of webconsole context path. Current /cns path was with us since begining of prototype. It's short but not intuitive. As the Felix WebConsole uses /system/console we can use /console without conflicts. What do you think? Do you have other propos

[Result][Vote][WebConsole] Camel / CXF / ServiceMix modules

Vote was open since Friday afternoon so I believe most of interested parties got chance to express. The results are following: Should WebConsole be early released: +1: Yes we should release alpha immediately 0: We should clean up code shortly and release -1: Wait untill getting stable codebase

Re: [Vote][WebConsole] Camel / CXF / ServiceMix modules

Hey Ioannis, We can optionally load Felix plugins. The only problem is - they're servlets and handle servlet requests. That's completely doesn't fit a wicket request handling model. However, we can always use some HTML frame. It looks ugly but Glassfish was doing that. :) The more important thin

[Vote][WebConsole] Camel / CXF / ServiceMix modules

Dear all, Last year Andreas, Charles and I started working on Karaf WebConsole. Since then lots of things was done - almost complete support for OSGi management, switching to Wicket 1.5. Some of things still need to be done - complete Karaf modules, clean up or improve Config Admin / Events / Lo

Re: Second Birthday

+1 for 2nd of July. Wiadomość napisana przez Jamie G. w dniu 21 cze 2012, o godz. 10:07: > +1 will try my best to be online :) > > On Thu, Jun 21, 2012 at 1:05 AM, Achim Nierbeck > wrote: >> +/-0 since I'm gone for vacation in that week. >> I guess I'm gonna miss the third call also then

Re: Second Birthday

Can we postpone call to Monday? :) From other things, skype is not the best for open meetings, can we try another tool? I am not Google employee but google hangouts works awesome for standups. Maybe we can use something else (and free of course). Last time when we called each other there was nu

  1   2   3   >