Re: javax.annotation 1.2.0 and KARAF-2660

Hi, we just stumbled over that topic again. In Karaf 4.0.x, javax.annotation version in jre.properties are set to 1.0 - fine. However, in the default config.properties, the javax.annotation packages are added to org.osgi.framework.system.packages.extra with version 1.2. If a bundle wants to use

Re: bnd files in Decanter Project

Hi Achim, I am glad to resolve this. The second round of beers is on me. I would like to work on building some more trust. How about doing a coding session together on a weekend. I think there is nothing better than working together while having a good time to gain some mutual trust. Perhaps

Re: bnd files in Decanter Project

Hello, some related questions: You are talking about the bnd-maven-plugin (e.g. Neil Bartlett). I recently read this pages: * https://github.com/bndtools/bnd/issues/629 * https://github.com/bndtools/bndtools/wiki/Maven-Integration-Requirements So, I would assume I should not move my projects to

Re: bnd files in Decanter Project

Hi Christian, thank you for your answer. I want to state, that there are no feelings from my side what is better. I want to collect the technical details for further decisions on the projects I maintain. So, let's assume I do not use the configuration in a parent project (just add

Re: bnd files in Decanter Project

I would love to join too ! Regards JB On 02/12/2016 09:21 AM, Christian Schneider wrote: Hi Achim, I am glad to resolve this. The second round of beers is on me. I would like to work on building some more trust. How about doing a coding session together on a weekend. I think there is nothing

Re: Karaf 4.1 switch to Java 8

Hi Arnaud, it's already done: master (4.1.x) is Java 8 only (and it's the way it's configured on Jenkins). On the other hand, Karaf 4.0.x fully supports Java 8 (but also Java 7). Regards JB On 02/12/2016 09:38 AM, Arnaud Vandyck wrote: Hi, According to this discussion "Karaf 4.0 switch to

Re: Karaf 4.1 switch to Java 8

Jetty 9.3 and PAX Web will demand Java8 so yes karaf 4.1 will only run with Java 8 while all other versions also support "older" versions. Regards, Achim sent from mobile device Am 12.02.2016 11:15 vorm. schrieb "David Daniel" < david.daniel.1...@gmail.com>: > Many of the new osgi bundles

Karaf 4.1 switch to Java 8

Hi, According to this discussion "Karaf 4.0 switch to Java 8"[0], and the fact that Karaf master is 4.1.0-SNAPSHOT[1], is there a plan to switch to Java 8? Is there an improvment request about it? Have a nice day, [0] http://karaf.922171.n3.nabble.com/Karaf-4-0-switch-to-Java8-tt40380

Re: bnd files in Decanter Project

Hi Markus, we had this configuration (and in most modules still have it) in Aries. The big problem is that if you setup for example an Import-Package in the parent pom then you can not change it back to the default in a submodule. This caused a lot of problems in Aries. If you look into the

Re: bnd files in Decanter Project

If there is an open seat and not having a football match I'm in also! Regards, Morgan On Feb 12, 2016 09:28, "Jean-Baptiste Onofré" wrote: > I would love to join too ! > > Regards > JB > > On 02/12/2016 09:21 AM, Christian Schneider wrote: > >> Hi Achim, >> >> I am glad to

[GitHub] karaf pull request: [KARAF-4330] Instance script doesn't return co...

GitHub user oscerd opened a pull request: https://github.com/apache/karaf/pull/144 [KARAF-4330] Instance script doesn't return correct PID number if roo… …t instance is started two times I submit this little PR for review. In case we start root instance two times, the

DISCUSS - how to handle different projects setup

Now that we have a defacto discrepancy in project setup how are we going to handle this? Karaf container and all other submodules besides decanter have the maven-bundle-plugin configuration in one place. Is it planned to move to the same setup for all other projects too? Are we planning on moving

Re: bnd files in Decanter Project

Hi, > - You typically do not need a plugin definition at all in each module pom. > So the definition just in the bnd file is much more concise. I set the plugin with "<_dsannotations>*" and set extensions in the parent POM and so no child pom that is using the defaults does need to contain the

Re: bnd files in Decanter Project

Sorry JB I think you are wrong with this perception. A lot of the dev decisions do influence users, especially the ones were people build on top. sent from mobile device Am 12.02.2016 12:53 nachm. schrieb "Jean-Baptiste Onofré" : > Hi David, > > For now, we are talking on the

Re: [VOTE] Apache Karaf 3.0.6 release

New gently reminder (especially for the PMC members ;)). Thanks, Regards JB On 02/09/2016 05:19 PM, Jean-Baptiste Onofré wrote: Hi all, I submit Apache Karaf 3.0.6 release to your vote. Release Notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12333641

Re: DISCUSS - how to handle different projects setup

Hi Achim, for now, each project has its own setup. So I guess you mean a parent pom shared by all projects ? For now, we still use maven-bundle-plugin (with different configuration). Regards JB On 02/12/2016 11:34 AM, Achim Nierbeck wrote: Now that we have a defacto discrepancy in project

Re: [VOTE] Apache Karaf 3.0.6 release

+1 (non-binding) Regards Krzysztof On 09.02.2016 17:19, Jean-Baptiste Onofré wrote: > Hi all, > > I submit Apache Karaf 3.0.6 release to your vote. > > Release Notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12333641 > > Staging Repository: >

Re: bnd files in Decanter Project

For me personally IDE support is irrelevant. BND is a command like tool and while support for it in IDEs is different at the end of the day all you need is a properties file editor. You don't get code competition for POMs neither so there is absolutely no difference (in terms of amount of work

Re: bnd files in Decanter Project

Maybe yes. Not sure. It's not obvious to me that using bnd files has an impact on end users. For instance, for Decanter, users just do feature:install, however the bundles have been created. Maybe I'm wrong. Regards JB On 02/12/2016 01:02 PM, Achim Nierbeck wrote: Sorry JB I think you are

Re: Karaf 4.1 switch to Java 8

Hi Arnaud, Thanks for the hint, yes this should be upgraded. Regards, Achim sent from mobile device Am 12.02.2016 2:39 nachm. schrieb "Arnaud Vandyck" : > On Fri, 2016-02-12 at 09:43 +0100, Jean-Baptiste Onofré wrote: > > Hi Arnaud, > > > > it's already done: master (4.1.x)

Re: Karaf 4.1 switch to Java 8

On Fri, 2016-02-12 at 14:46 +0100, Jean-Baptiste Onofré wrote: > Hi Arnaud, > > yes, it should be updated (I'm doing it now), but you can see: > > http://karaf.apache.org/download.html > > in the table about Java Version Support, that the min is 8. I was trying to work on KARAF-4273,

Re: [DISCUSS] Release Decanter 1.1.0

It makes sense. +1 (non-binding). -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Friday, February 12, 2016 3:31 PM, Jean-Baptiste Onofré wrote: Hi

Re: Karaf 4.1 switch to Java 8

It's already done. Regards JB On 02/12/2016 03:24 PM, Arnaud Vandyck wrote: On Fri, 2016-02-12 at 14:46 +0100, Jean-Baptiste Onofré wrote: Hi Arnaud, yes, it should be updated (I'm doing it now), but you can see: http://karaf.apache.org/download.html in the table about Java Version

[DISCUSS] Release Decanter 1.1.0

Hi guys, I'm doing deeper and larger test on Decanter with Elasticsearch 1.x and 2.x, with the "new" elasticsearch rest appender. Unfortunately, elasticsearch 2.x introduced an important change compare to elasticsearch 1.x: '.' is no more allowed in field name. So, it means that field name

Re: Karaf 4.1 switch to Java 8

On Fri, 2016-02-12 at 09:43 +0100, Jean-Baptiste Onofré wrote: > Hi Arnaud, > > it's already done: master (4.1.x) is Java 8 only (and it's the way > it's configured on Jenkins). According to the pom > > [1] https://github.com/apache/karaf/blob/master/pom.xml I see this configuration for the

Re: [VOTE] Apache Karaf 3.0.6 release

+1 (binding) On Fri, Feb 12, 2016 at 9:59 AM, Sobkowiak Krzysztof wrote: > +1 (non-binding) > > Regards > Krzysztof > > On 09.02.2016 17:19, Jean-Baptiste Onofré wrote: >> Hi all, >> >> I submit Apache Karaf 3.0.6 release to your vote. >> >> Release Notes: >>

Re: Karaf 4.1 switch to Java 8

On Fri, 2016-02-12 at 15:32 +0100, Jean-Baptiste Onofré wrote: > It's already done. Cool, thanks ;-) And congratulations for the new website ;-) -- Arnaud Vandyck

Re: [VOTE] Apache Karaf 3.0.6 release

+1 (non binding) Christian On 11.02.2016 12:56, Jean-Baptiste Onofré wrote: Gently reminder. Regards JB On 02/09/2016 05:19 PM, Jean-Baptiste Onofré wrote: Hi all, I submit Apache Karaf 3.0.6 release to your vote. Release Notes:

Re: bnd files in Decanter Project

From my point of view the arguments for and against the bnd file extraction. Pro: - You typically do not need a plugin definition at all in each module pom. So the definition just in the bnd file is much more concise. - If you use bndtools you get a nice view and editor for the bnd file. This

Re: [DISCUSS] Release Decanter 1.1.0

Sounds OK to me. +1 Regards, Achim sent from mobile device Am 12.02.2016 4:31 nachm. schrieb "Morgan Hautman" : > +1 > On Feb 12, 2016 15:47, "Andrea Cosentino" > wrote: > > > It makes sense. > > > > +1 (non-binding). > > -- > >

Re: [DISCUSS] Release Decanter 1.1.0

+1 On Feb 12, 2016 15:47, "Andrea Cosentino" wrote: > It makes sense. > > +1 (non-binding). > -- > Andrea Cosentino > -- > Apache Camel PMC Member > Apache Karaf Committer > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github:

Proposal - Lightweight standalone remote OSGi implementation for karaf-cellar

Hi all, we (a colleague of mine and myself) started searching for a high-performance / lightweight remote OSGi implementation. We have a requirement that the implementation has to /also/ (in addition to Karaf) run on a heavily customized JBoss 7.1.1 as well, so the lightweight part was kinda

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

Hi Sascha, On 2/12/2016 7:42 AM, Sascha Vogt wrote: Hi all, we (a colleague of mine and myself) started searching for a high-performance / lightweight remote OSGi implementation. We have a requirement that the implementation has to /also/ (in addition to Karaf) run on a heavily customized

Re: [DISCUSS] Release Decanter 1.1.0

+1 sounds good. On Fri, Feb 12, 2016 at 1:30 PM, Achim Nierbeck wrote: > Sounds OK to me. > > +1 > > Regards, Achim > > sent from mobile device > Am 12.02.2016 4:31 nachm. schrieb "Morgan Hautman" >: > >> +1 >> On Feb 12, 2016 15:47, "Andrea

Re: Known Karaf users

A list of users of karaf would be nice but I think something even better would be to have a short success story for each user. The story could show an overview of the architecture and technologies they use as well as their business case. We could then showcase one user in a round robin fashion

Re: Known Karaf users

I can add couple more projects: Atricore Identity Bus (company behind is Atricore) OpenHab 2 - starting from this version Karaf is used as new runtime From companies who uses Karaf I can point to Cumulocity. We actually could point to opensource projects which are powered by Karaf. If it’s