Re: Board report for December 2023

[Andrea Cosentino]

The reminders hasn't been sent totally.

I reported Apache Camel just because I remembered by myself.

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, December 15, 2023 at 05:51:35 PM GMT+1, Serge Huber 
 wrote: 





+1

I didn't get notifications for the Unomi project either, so it's late too
I'll get right on it. Anybody has any clues as to what is going on ?

Regards,
  Serge...
Serge Huber
CTO & Co-Founder
T +41 22 361 3424
9 route des Jeunes | 1227 Acacias | Switzerland
jahia.com <http://www.jahia.com/>
SKYPE | LINKEDIN <https://www.linkedin.com/in/sergehuber> | TWITTER
<https://twitter.com/sergehuber> | VCARD
<http://www.jahia.com/vcard/HuberSerge.vcf>


> JOIN OUR COMMUNITY <http://www.jahia.com/> to evaluate, get trained and
to discover why Jahia is a leading User Experience Platform (UXP) for
Digital Transformation.


On Fri, Dec 15, 2023 at 2:46 PM Francois Papon 
wrote:

> +1
>
> regards,
>
> François
>
> On 15/12/2023 13:42, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > I'm sorry, we are late for the board report this month (I didn't
> > receive a reminder and forgot to create one).
> > So I quickly created a board report here:
> >
> > https://cwiki.apache.org/confluence/display/KARAF/Board+Reports
> >
> > Please take a look, I would like to send it asap (if possible tonight).
> >
> > Thanks !
> > Regards
> > JB
>

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

[Andrea Cosentino]

As a side note, it's not only aligning the features, it's also upgrading
the servicemix bundles to be able to align, JB knows what I'm talking about.

I helped there a lot too (less in the last year or so) and it's really a
mess.

Il mer 18 gen 2023, 20:43 Romain Manni-Bucau  ha
scritto:

> Le mer. 18 janv. 2023 à 20:17, Andrea Cosentino  a
> écrit :
>
> > Il mer 18 gen 2023, 20:06 Romain Manni-Bucau  ha
> > scritto:
> >
> > > Le mer. 18 janv. 2023 à 19:43, Andrea Cosentino  a
> > > écrit :
> > >
> > > > Hello,
> > > >
> > > > The point is just one in relation to OSGi metadata. The components
> will
> > > be
> > > > consumed, also, by runtimes that don't need OSGi metadata, so why all
> > the
> > > > components should be with OSGi metadata and packaged as bundles?
> > > >
> > >
> > > I'm maybe a bit dumb but why all the work and meta for quarkus and
> spring
> > > boot if the reasoning is right?
> > > I perfectly understand spring or quarkus have their own programming
> > > model/runtime so need specific code and meta but then how is OSGi
> > > different?
> > >
> > > A simple example is that you should be able to drop most jandex indices
> > if
> > > your statement is true.
> > >
> >
> > My point is related more to have the components as bundles with OSGi
> > metadata. To me they should be just JAR.
> >   Mainly the reason I'm saying this about supporting camel-karaf because
> > the work wi be on the shoulders of 1 developer and this is not right for
> me
> > and for the community.
> >
>
> Sure but osgi bundles always had been designed to be just jars as much as a
> jar with a jandex index or even with a custom manifest metadata or a json
> containing the pom description ;).
>
> But I fully share with you the ownership point.
> Any bundle (more generally meta maintenance) should be owned by the core
> code writer otherwise we end in weird state all the time, in particular
> when parts are optionals or need some specific loading mecanism
> (serviceloader for ex). The lifecycle is also an issue in time, we already
> are there with features around whiteboards for ex and camel itself has a
> hard time ensuring  components work together so fear camel can be a bit big
> to have this enrichment work done properly outside camel in a project with
> less task force than camel itself.
>
>
> > Just this.
> >
> > >
> > >
> > > >
> > > > I don't see the reason why. At least the OSGi metadata should be
> > > generated
> > > > under camel Karaf project, instead of being part of the core
> components
> > > >
> > >
> > > I think the exact opposite since handling metadata in a 3rd always got
> > > proven not working very well for end user.
> > > SMix did a bunch of forks for that reason - which was enabling users
> but
> > > also a big constrait since users were not able to use the actual
> binaries
> > > for ex.
> > > Having metada on the fly is a neat solution but does not work very
> long,
> > > even when you have a bunch of people to maintain is - graalvm metadata
> > > repository is poorly usable for that reason today so for the camel
> > > ecosystem it sounds impossible to do with a good quality and being able
> > to
> > > say "next release" at each release for end users is just not an option
> -
> > > but what it would mean concretely to not handle it in camel.
> > >
> > >
> > > >
> > > > I see there is a veto about moving to apache Karaf. It was already a
> > mess
> > > > before to maintain the features and release camel-karaf with Camel 3,
> > in
> > > > the end there were one contributor (myself) taking care of them, with
> > > some
> > > > sporadic help. I really don't have the capacity in the future.
> > > >
> > >
> > > Guess it joins my previous point and actually justifies it should be in
> > > camel project or not at the end since it looks like the status of the
> > > camel-osgi ecosystem as of today - inter projects.
> > >
> > >
> > > >
> > > > If the situation is this, as Camel PMC we'll need to discuss this and
> > > > eventually discontinue, deprecating or make the camel-karaf releases
> > > > optional.
> > > >
> > >
> > > +1 if there is no real ownership, better to go to attic than have a not
> > > living project IMHO
> > >
> > >
> > > >
> > > > Thanks.
> > > >
> > > >
> > > >
> > > > Il mer 18 gen 2023, 19:27 Matt Pavlovich  ha
> > > scritto:
> > > >
> > > > > I have a similar question on this point--
> > > > >
> > > > > > On Jan 18, 2023, at 12:02 PM, Łukasz Dywicki <
> l...@code-house.org>
> > > > > wrote:
> > > > > >
> > > > > > 6) I do not see any sign of what is going to happen with OSGi
> > > metadata
> > > > > which is present for Apache Camel 3.x components. Is Camel 4.x
> going
> > to
> > > > > retain OSGi metadata?
> > > > >
> > > > > How is maintaining OGSI metadata in Camel a concern?
> > > > >
> > > > > Thanks,
> > > > > Matt Pavlovich
> > > >
> > >
> >
>

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

[Andrea Cosentino]

Il mer 18 gen 2023, 20:06 Romain Manni-Bucau  ha
scritto:

> Le mer. 18 janv. 2023 à 19:43, Andrea Cosentino  a
> écrit :
>
> > Hello,
> >
> > The point is just one in relation to OSGi metadata. The components will
> be
> > consumed, also, by runtimes that don't need OSGi metadata, so why all the
> > components should be with OSGi metadata and packaged as bundles?
> >
>
> I'm maybe a bit dumb but why all the work and meta for quarkus and spring
> boot if the reasoning is right?
> I perfectly understand spring or quarkus have their own programming
> model/runtime so need specific code and meta but then how is OSGi
> different?
>
> A simple example is that you should be able to drop most jandex indices if
> your statement is true.
>

My point is related more to have the components as bundles with OSGi
metadata. To me they should be just JAR.
  Mainly the reason I'm saying this about supporting camel-karaf because
the work wi be on the shoulders of 1 developer and this is not right for me
and for the community.

Just this.

>
>
> >
> > I don't see the reason why. At least the OSGi metadata should be
> generated
> > under camel Karaf project, instead of being part of the core components
> >
>
> I think the exact opposite since handling metadata in a 3rd always got
> proven not working very well for end user.
> SMix did a bunch of forks for that reason - which was enabling users but
> also a big constrait since users were not able to use the actual binaries
> for ex.
> Having metada on the fly is a neat solution but does not work very long,
> even when you have a bunch of people to maintain is - graalvm metadata
> repository is poorly usable for that reason today so for the camel
> ecosystem it sounds impossible to do with a good quality and being able to
> say "next release" at each release for end users is just not an option -
> but what it would mean concretely to not handle it in camel.
>
>
> >
> > I see there is a veto about moving to apache Karaf. It was already a mess
> > before to maintain the features and release camel-karaf with Camel 3, in
> > the end there were one contributor (myself) taking care of them, with
> some
> > sporadic help. I really don't have the capacity in the future.
> >
>
> Guess it joins my previous point and actually justifies it should be in
> camel project or not at the end since it looks like the status of the
> camel-osgi ecosystem as of today - inter projects.
>
>
> >
> > If the situation is this, as Camel PMC we'll need to discuss this and
> > eventually discontinue, deprecating or make the camel-karaf releases
> > optional.
> >
>
> +1 if there is no real ownership, better to go to attic than have a not
> living project IMHO
>
>
> >
> > Thanks.
> >
> >
> >
> > Il mer 18 gen 2023, 19:27 Matt Pavlovich  ha
> scritto:
> >
> > > I have a similar question on this point--
> > >
> > > > On Jan 18, 2023, at 12:02 PM, Łukasz Dywicki 
> > > wrote:
> > > >
> > > > 6) I do not see any sign of what is going to happen with OSGi
> metadata
> > > which is present for Apache Camel 3.x components. Is Camel 4.x going to
> > > retain OSGi metadata?
> > >
> > > How is maintaining OGSI metadata in Camel a concern?
> > >
> > > Thanks,
> > > Matt Pavlovich
> >
>

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

[Andrea Cosentino]

Hello,

The point is just one in relation to OSGi metadata. The components will be
consumed, also, by runtimes that don't need OSGi metadata, so why all the
components should be with OSGi metadata and packaged as bundles?

I don't see the reason why. At least the OSGi metadata should be generated
under camel Karaf project, instead of being part of the core components

I see there is a veto about moving to apache Karaf. It was already a mess
before to maintain the features and release camel-karaf with Camel 3, in
the end there were one contributor (myself) taking care of them, with some
sporadic help. I really don't have the capacity in the future.

If the situation is this, as Camel PMC we'll need to discuss this and
eventually discontinue, deprecating or make the camel-karaf releases
optional.

Thanks.



Il mer 18 gen 2023, 19:27 Matt Pavlovich  ha scritto:

> I have a similar question on this point--
>
> > On Jan 18, 2023, at 12:02 PM, Łukasz Dywicki 
> wrote:
> >
> > 6) I do not see any sign of what is going to happen with OSGi metadata
> which is present for Apache Camel 3.x components. Is Camel 4.x going to
> retain OSGi metadata?
>
> How is maintaining OGSI metadata in Camel a concern?
>
> Thanks,
> Matt Pavlovich

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

[Andrea Cosentino]

+1 (binding)

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Wednesday, January 18, 2023 at 11:03:27 AM GMT+1, Jean-Baptiste Onofré 
 wrote: 





Hi guys,

The Apache Camel community proposed to move Camel Karaf to the Apache
Karaf project (as a new subproject).

As a reminder, Camel Karaf provides:
- support Camel Contexts/Routes as OSGi services (camel-core-osgi)
- Camel components specific to OSGi and Karaf (camel-blueprint, camel-scr, ...)
- wrapping of Camel components as Karaf features (providing a features
repository XML)

I think there are a bunch of users using camel-karaf, so, from a
community perspective, it would be great to maintain it.
Furthermore, I already have some ideas to improve karaf-camel, like
avoiding to wrap each Camel component as an OSGi bundle, but instead
creating a kind of Uber jar to simplify deployment and have more
reliable behavior.

Concretely, accepting camel-karaf as Karaf subproject would mean:
- maintain the existing code, and improving it, preparing kind of
roadmap for camel-karaf
- deal with Camel versions and components (and all difficulties that
it could cause in an OSGi context :) )
- maintain camel-karaf specific documentation
- vote for the releases (the PMC members would be the Karaf ones, so
binding vote from Karaf PMC members)

I submit accepting camel-karaf (so karaf-camel :)) as new Karaf
subproject to your vote:

Please vote to approve this release:
[ ] +1 Approve camel-karaf as new Karaf subproject
[ ] -1 Don't approve camel-karaf as new Karaf subproject (please
provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB

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

[Andrea Cosentino]

As as side note to what JB just wrote:

as Apache Camel community we'll still maintain the 3.x side of the
projects, for continuity, Karaf-camel will be the house for the Camel 4.x
OSGi support.

Thanks.

Il giorno mer 18 gen 2023 alle ore 11:03 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:

> Hi guys,
>
> The Apache Camel community proposed to move Camel Karaf to the Apache
> Karaf project (as a new subproject).
>
> As a reminder, Camel Karaf provides:
> - support Camel Contexts/Routes as OSGi services (camel-core-osgi)
> - Camel components specific to OSGi and Karaf (camel-blueprint, camel-scr,
> ...)
> - wrapping of Camel components as Karaf features (providing a features
> repository XML)
>
> I think there are a bunch of users using camel-karaf, so, from a
> community perspective, it would be great to maintain it.
> Furthermore, I already have some ideas to improve karaf-camel, like
> avoiding to wrap each Camel component as an OSGi bundle, but instead
> creating a kind of Uber jar to simplify deployment and have more
> reliable behavior.
>
> Concretely, accepting camel-karaf as Karaf subproject would mean:
> - maintain the existing code, and improving it, preparing kind of
> roadmap for camel-karaf
> - deal with Camel versions and components (and all difficulties that
> it could cause in an OSGi context :) )
> - maintain camel-karaf specific documentation
> - vote for the releases (the PMC members would be the Karaf ones, so
> binding vote from Karaf PMC members)
>
> I submit accepting camel-karaf (so karaf-camel :)) as new Karaf
> subproject to your vote:
>
> Please vote to approve this release:
> [ ] +1 Approve camel-karaf as new Karaf subproject
> [ ] -1 Don't approve camel-karaf as new Karaf subproject (please
> provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
>

Re: [VOTE] Accept Apache Karaf Minho in Apache Karaf

[Andrea Cosentino]

+1 (non-binding)

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, October 20, 2022 at 09:36:26 AM GMT+2, Jean-Baptiste Onofré 
 wrote: 





+1 (binding)

Regards
JB

On Thu, Oct 13, 2022 at 8:46 AM Jean-Baptiste Onofré  wrote:
>
> Hi guys,
>
> As discussed on the mailing list, I would like to start a formal vote
> to accept Apache Karaf Minho in Apache Karaf.
>
> The proposal is:
> - create karaf-minho repository on github
> - use github issues/actions for Minho
> - rework the website to have all projects at the same level, Karaf
> runtime becoming Karaf OSGi. Each project will have its own
> subwebsite, like https://jbonofre.github.io/karaf5/.
>
> In the meantime, I will change all resources to use
> org.apache.karaf.minho namespace on my github before donation.
>
> Please vote to approve this donation/change:
>
> [ ] +1 Approve Minho donation and proposed plan
> [ ] -1 Don't approve the donation/changes (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Regards
> JB

Re: Karaf/Camel camel-elasticsearch-rest component and Log4jShell

[Andrea Cosentino]

Elasticsearch high level client and all the related stuff changed their
license after 7.10.2

As far as I know is not compatible with ASF License.

This is the reason is not updated.

Il giorno lun 3 gen 2022 alle ore 16:27 Francois Papon <
francois.pa...@openobject.fr> ha scritto:

> Hi,
>
> The Camel elasticsearch-rest-component depend on the version 7.10.2 of
> elasticsearch-client that has a dependency on log4j-core:2.13.3 and
> log4j-api:2.13.3
>
> When installating the Karaf feature the log4j bundles are installed:
>
>
> https://github.com/apache/camel-karaf/blob/e976acc7c1d6405b283ffe3e69d336aab854bd5b/pom.xml#L232
>
> There is a comment about upgrading but with a warning about other
> features compatibility.
>
> Does anyone has some information about this?
>
> Do we need to upgrade?
>
> The Elasticsearch team upgraded to log4j:2.17.0 on 7.16.2.
>
> May be Servicemix bundle should be update too.
>
> Regards,
>
> Francois
>
>
>
>

Re: Top Contributors

[Andrea Cosentino]

Hello Bernd,

Thanks a lot, much appreciated :-)



--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Tuesday, August 31, 2021, 05:52:33 PM GMT+2, Bernd Eckenfels 
 wrote: 





Congratulations to JB and Andrea for beeing recognized as top committers and 
senders in the latest annual ASF report

https://s.apache.org/FY2021AnnualReport

And of course also a huge thank you to all other contributors from my side. I 
came across the report and thought it’s a good reason to say thank you.

Gruss
Bernd
--
http://bernd.eckenfels.net

Re: [VOTE] Apache Karaf runtime 4.2.9 (take #2)

[Andrea Cosentino]

+1 (non-binding)

Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, June 5, 2020, 02:48:18 PM GMT+2, Jean-Baptiste Onofre 
 wrote: 





Hi everyone,

I submit Apache Karaf runtime 4.2.9 release to your vote (take #2 where we 
fixed the ASM update).

This is a maintenance release on the 4.2.x series bringing fixes, updates and 
improvements.
It especially fixes the issues related to the shell (paste didn’t work 
properly, some commands caused exception, …).

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12346465
 
<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12346465>

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1143/ 
<https://repository.apache.org/content/repositories/orgapachekaraf-1143/>

Staging Dist:
https://dist.apache.org/repos/dist/dev/karaf/4.2.9/ 
<https://dist.apache.org/repos/dist/dev/karaf/4.2.9/>

Git Tag:
karaf-4.2.9

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB

Re: [VOTE] Apache Karaf Decanter 2.4.0 release

[Andrea Cosentino]

+1 (non-binding)

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, April 24, 2020, 08:44:59 AM GMT+2, Jean-Baptiste Onofre 
 wrote: 





Hi everyone,

As discussed previously on the mailing list, I submit Apache Karaf Decanter 
2.4.0 to your vote.

It’s a major release on the Decanter 2.x series, containing a bug fix on the 
Prometheus appender feature, and new features, especially:

- New processing layer with aggregator (see blog 
http://blog.nanthrax.net/?p=1016 <http://blog.nanthrax.net/?p=1016>)
- New collectors (prometheus, Elasticsearch, configadmin, redis, oshi) (see 
blog http://blog.nanthrax.net/?p=1019 <http://blog.nanthrax.net/?p=1019>)

Take a look on the Release Notes for details.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12346613
 
<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12346613>

Git Tag:
decanter-2.4.0

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1141/ 
<https://repository.apache.org/content/repositories/orgapachekaraf-1141/>

Staging Dist:
https://dist.apache.org/repos/dist/dev/karaf/decanter/2.4.0/ 
<https://dist.apache.org/repos/dist/dev/karaf/decanter/2.4.0/>

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Regards
JB

R: Re: Redirecting PR notifications

[Andrea Cosentino]

You can also set an .asf.yml in the repository. We are doing it in Camel.

Inviato da Yahoo Mail su Android 
 
  Il lun, 27 apr, 2020 alle 18:50, Jean-Baptiste Onofre ha 
scritto:   Hi,

Yes, I didn’t see that as I had a filter on my client.

Let me fix that and send to comm...@karaf.apache.org 
.

Regards
JB

> Le 27 avr. 2020 à 18:23, Guillaume Nodet  a écrit :
> 
> Is there a way to configure gitbox so that PR notifications are sent to
> comm...@karaf.apache.org or eventually iss...@karaf.apache.org ?
> This would reduce a bit the traffic on dev@karaf.apache.org and help
> keeping up with dev related discussions.
> 
> -- 
> 
> Guillaume Nodet
  

Re: [VOTE] Remove Apache Karaf EIK & Wicket WebConsole repositories

[Andrea Cosentino]

+1 (non-binding)

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Monday, April 6, 2020, 01:38:36 PM GMT+2, Jean-Baptiste Onofre 
 wrote: 





Hi everyone,

While ago we voted to deprecate Karaf EIK & Wicket WebConsole. The two 
components are flagged as "deprecated" in Jira.

I would like to call for a vote to completely remove the EIK & WicketWebConsole 
git repositories, and also the references in Jira (tickets and components).

Please vote to remove the EIK & WebConsole resources:

[ ] + 1 Approve deletion
[ ] -1 Don’t approve the deletion (please provide specific comments)

This vote will be open for 48 hours.

Thanks,
Regards
JB

Re: Board report for March 30th

[Andrea Cosentino]

+1, Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, February 27, 2020, 09:57:29 AM GMT+1, Jean-Baptiste Onofre 
 wrote: 





Hi guys,

I prepared the board report for this month:

https://cwiki.apache.org/confluence/display/KARAF/Board+Reports 
<https://cwiki.apache.org/confluence/display/KARAF/Board+Reports>

Please, review and let me know if I forgot something.
I would like to submit the report asap.

Thanks !

Regards
JB

Re: [VOTE] Apache Karaf runtime 4.2.8 release

[Andrea Cosentino]

+1 (non binding)

Cheers.

Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Sunday, January 12, 2020, 12:34:39 PM GMT+1, Jean-Baptiste Onofré 
 wrote: 





Hi all,

I submit Apache Karaf runtime 4.2.8 to your vote. This is a
maintenance release on the 4.2.x series, bringing updates, improvements
and fixes.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12346100

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1137

Staging Dist:
https://dist.apache.org/repos/dist/dev/karaf/4.2.8/

Git Tag:
karaf-4.2.8

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

R: Re: Board report for this quarter

[Andrea Cosentino]

+1 thanks JB

Inviato da Yahoo Mail su Android 
 
  Il ven, 13 dic, 2019 alle 13:42, Grzegorz Grzybek ha 
scritto:   +1

regards
Grzegorz Grzybek

pt., 13 gru 2019 o 13:27 Jean-Baptiste Onofré  napisał(a):

> Hi guys,
>
> here's the board report I prepared for this month:
>
> ## Description:
> Apache Karaf provides a modern and polymorphic applications runtime,
> multi-purpose (microservices, cloud, IoT, OSGi, etc).
>
> ## Issues:
> There are no issues requiring board attention at this time
>
> ## Membership Data:
> Apache Karaf was founded 2010-06-16 (9 years ago)
> There are currently 31 committers and 17 PMC members in this project.
> The Committer-to-PMC ratio is roughly 8:5.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Francois Papon on 2018-11-29.
> - No new committers. Last addition was Francois Papon on 2018-05-19.
>
> ## Project Activity:
> We did a complete refactoring on Karaf Cave and did two releases:
> * Cave 4.2.1 was released on 2019-12-02.
> * Cave 4.2.0 was released on 2019-10-31.
> We also did a Karaf runtime maintenance release:
> * 4.2.7 was released on 2019-09-29.
> We also vote the donation of Winegrower as new Apache Karaf subprojec.
> A first Winegrower release will happen soon.
>
> ## Community Health:
> * dev@karaf.apache.org had a 82% increase in traffic in the past quarter
>  (223 emails compared to 122)
> * u...@karaf.apache.org had a 35% increase in traffic in the past quarter
>  (405 emails compared to 298)
> * 126 issues opened in JIRA, past quarter (53% increase)
> * 98 issues closed in JIRA, past quarter (66% increase)
> * 199 commits in the past quarter (61% increase)
> * 19 code contributors in the past quarter (72% increase)
> * 118 PRs opened on GitHub, past quarter (81% increase)
> * 115 PRs closed on GitHub, past quarter (101% increase)
> We also started and helped other communities during the past quarter:
> * discussion with Apache PLC4X about OSGi/Karaf adoption
> * help Apache Unomi to upgrade to the latest Karaf releases branch
>
> I'm also upgrading cwiki.
>
> Please, let me know if I missed something or you want some changes.
>
> Thanks !
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>  

Re: [VOTE] Apache Karaf (runtime) 4.2.7 release

[Andrea Cosentino]

+1 (non-binding)

Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Monday, September 23, 2019, 6:35:20 PM GMT+2, Jean-Baptiste Onofré 
 wrote: 





Hi all,

I submit Apache Karaf (runtime) 4.2.7 to your vote. This is a
maintenance release on the 4.2.x series, bringing updates, improvements
and fixes (client.bat on Windows, config fileinstall reuse, race
condition on config in some activator, ...).

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12345539

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1133/

Git Tag:
karaf-4.2.7

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf (runtime) 4.2.6 release

[Andrea Cosentino]

+1 (non-binding)

Thanks JB

Cheers.

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, June 7, 2019, 1:13:24 PM GMT+2, Jean-Baptiste Onofré 
 wrote: 





Hi all,

I submit Apache Karaf (runtime) 4.2.6 to your vote. This is a
maintenance release on the 4.2.x series, bringing some improvements and
bug fixes (scr with equinox, dependencies updates, and much more !).

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12345365

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1132/

Git Tag:
karaf-4.2.6

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Board report for June 2019

[Andrea Cosentino]

Great, +1.

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, June 6, 2019, 10:57:11 AM GMT+2, Jean-Baptiste Onofré 
 wrote: 





Hi guys,

I prepared the board report for this month:

https://cwiki.apache.org/confluence/display/KARAF/Board+Reports

Please, take a look and let me know if I forgot something.

I would like to send the report over the week end.

Thanks !
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf (runtime) 4.2.5 release

[Andrea Cosentino]

+1 (non-binding)

Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, April 19, 2019, 10:40:17 AM GMT+2, Jean-Baptiste Onofré 
 wrote: 





+1 (binding)

Regards
JB

On 17/04/2019 20:29, Jean-Baptiste Onofré wrote:
> Hi all,
> 
> I submit Apache Karaf (runtime) 4.2.5 to your vote. This is a
> maintenance release on the 4.2.x series, bringing some improvements and
> bug fixes (scr commands, new docker goal in maven plugin, new
> distribution examples, ...).
> 
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12345153
> 
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1131/
> 
> Git Tag:
> karaf-4.2.5
> 
> Please vote to approve this release:
> 
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
> 
> This vote will be open for at least 72 hours.
> 
> Thanks,
> Regards
> JB
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

R: Re: [VOTE] Move jclouds-karaf and jclouds-cli projects under Karaf project governance

[Andrea Cosentino]

+1. It makes sense 

Inviato da Yahoo Mail su Android 
 
  Il mer, 17 apr, 2019 alle 20:16, Francois Papon 
ha scritto:   +1 (binding)

regards,

François Papon
fpa...@apache.org

Le 17/04/2019 à 19:14, Jean-Baptiste Onofré a écrit :
> Hi,
>
> Some days ago we discussed on the Apache jClouds dev mailing list about
> moving the jclouds-karaf and jclouds-cli project under the Karaf project
> governance, as it's hard for the jClouds community to maintain them.
>
> So, I'm proposing:
>
> 1. We keep the git repository where they are currently:
>     https://gitbox.apache.org/repos/asf?p=jclouds-karaf.git
>     https://gitbox.apache.org/repos/asf?p=jclouds-cli.git
> We also keep the Maven coordinates as they are.
> It would be completely transparent for our users.
>
> 2. The governance changes to Karaf PMC. I will ask to INFRA to change
> the team (group) managing the repo and Jenkins jobs.
> 3. I will update Jenkins to notify Karaf mailing list.
>
> I already have couple of PRs ready for upgrade jclouds-karaf for Karaf
> 4.2.x/4.3.x and some other cleanups.
>
> Please vote to approve this change:
>
> [ ] +1 Approve the change
> [ ] -1 Don't approve the change (please provide specific comments)
>
> Thanks,
> Regards
> JB
  

Re: [VOTE] Apache Karaf (runtime) 4.2.4 release

[Andrea Cosentino]

+1 (non-binding)

Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Monday, March 18, 2019, 2:45:27 PM GMT+1, Jean-Baptiste Onofré 
 wrote: 





+1 (binding)

Regards
JB

On 14/03/2019 13:43, Jean-Baptiste Onofré wrote:
> Hi all,
> 
> I submit Apache Karaf (runtime) 4.2.4 to your vote. This is a
> maintenance release on the 4.2.x series, bringing some improvements and
> bug fixes (child instances, blacklist, new configadmin, ASM, ...
> versions, and much more).
> 
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12344856
> 
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1129/
> 
> Git Tag:
> karaf-4.2.4
> 
> Please vote to approve this release:
> 
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
> 
> This vote will be open for at least 72 hours.
> 
> Thanks,
> Regards
> JB
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf (runtime) 4.2.4 release

[Andrea Cosentino]

+1 (non-binding)

Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, March 14, 2019, 1:43:32 PM GMT+1, Jean-Baptiste Onofré 
 wrote: 





Hi all,

I submit Apache Karaf (runtime) 4.2.4 to your vote. This is a
maintenance release on the 4.2.x series, bringing some improvements and
bug fixes (child instances, blacklist, new configadmin, ASM, ...
versions, and much more).

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12344856

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1129/

Git Tag:
karaf-4.2.4

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf (runtime) 4.2.3 release (take 2)

[Andrea Cosentino]

+1 (non-binding)

Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, February 8, 2019, 8:17:06 AM GMT+1, Grzegorz Grzybek 
 wrote: 





+1 (binding)

javax.annotation is at version 1.3 in important places (hibernate's bundle
can be overriden in etc/org.apache.karaf.features.xml if needed):

*javax.annotation/javax.annotation-api*

  - *mvn:javax.annotation/javax.annotation-api/1.2*
      - hibernate-validator-javax-money/6.0.14.Final
      
(mvn:org.hibernate.validator/hibernate-validator-osgi-karaf-features/6.0.14.Final/xml/features)
  - *mvn:javax.annotation/javax.annotation-api/1.3*
      - jetty/9.4.12.v20180830
      (mvn:org.apache.karaf.features/standard/4.2.3/xml/features)
      - pax-cdi-core/1.1.1
      (mvn:org.ops4j.pax.cdi/pax-cdi-features/1.1.1/xml/features)
      - pax-jetty/9.4.12.v20180830
      (mvn:org.ops4j.pax.web/pax-web-features/7.2.8/xml/features)
      - undertow/1.4.23.Final
      (mvn:org.ops4j.pax.web/pax-web-features/7.2.8/xml/features)

The report is here:
http://people.apache.org/~ggrzybek/apache-karaf-4.2.3-bundle-report.xml

regards
Grzegorz Grzybek

pt., 8 lut 2019 o 05:31 Jean-Baptiste Onofré  napisał(a):

> Hi all,
>
> I submit Apache Karaf (runtime) 4.2.3 to your vote. This is a
> maintenance release on the 4.2.x series, bringing some improvements and
> bug fixes.
> NB: Once this release vote passed, I will create the karaf-4.2.x branch
> and master will become 4.3.x. Obviously karaf-4.2.x will be an active
> branch and I already plan to prepare 4.2.4 release.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12344587
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1126/
>
> Git Tag:
> karaf-4.2.3
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf (runtime) 4.2.3 release

[Andrea Cosentino]

+1 (non-binding)
Thanks JB!
--Andrea Cosentino --Apache Camel PMC 
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd 

On Tuesday, February 5, 2019, 10:57:55 AM GMT+1, Jean-Baptiste Onofré 
 wrote:  
 
 Hi all,

I submit Apache Karaf (runtime) 4.2.3 to your vote. This is a
maintenance release on the 4.2.x series, bringing some improvements and
bug fixes.
NB: Once this release vote passed, I will create the karaf-4.2.x branch
and master will become 4.3.x. Obviously karaf-4.2.x will be an active
branch and I already plan to prepare 4.2.4 release.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12344587

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1125/

Git Tag:
karaf-4.2.3

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
  

Re: [PROPOSAL] Adding a new Java 11 master build on Jenkins

[Andrea Cosentino]

+1 :-)

Thanks JB!

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, January 10, 2019, 8:59:21 AM GMT+1, Jean-Baptiste Onofré 
 wrote: 





Hi,

I would like to add a new job on Jenkins of Karaf master branch, using
JDK 11 for the build.
This job won't publish/deploy SNAPSHOT, just a full build (the SNAPSHOTs
will be still deployed by the JDK 8 based current job).

Thoughts ?

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Version alignment report for Karaf 4.2.3-SNAPSHOT - 1/2

[Andrea Cosentino]

I think a Jenkins profile is really a good idea.

Great!

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Tuesday, January 8, 2019, 1:34:35 PM GMT+1, Jean-Baptiste Onofré 
 wrote: 





Nice Greg.

What do you think about enabling this report via Jenkins (using a profile) ?

Regards
JB

On 08/01/2019 13:28, Grzegorz Grzybek wrote:
> Hello
> 
> For any custom Karaf distro we can enable generation of "consistency
> report" - check sample here:
> http://people.apache.org/~ggrzybek/bundle-report-full-karaf.xml (requires
> browser that can do XSLT transformation using )
> 
> it can be configured using:
> 
> 
>    org.apache.karaf.tooling
>    karaf-maven-plugin
>    
> 
> ${project.build.directory}/assembly
> 
> 
> karaf-maven-plugin:assembly then generates:
>  - bundle-report.xslt - stylesheet to transform XMLs
>  - bundle-report-full.xml - full report, including blacklisted
> repos/features/bundles
>  - bundle-report.xml - a report without blacklisted items
> 
> The idea behind this report is to show _duplicates_ - bundles that appear
> with the same groupId and artifactId (maven) but with different version.
> The report also shows the features the bundles are declared in and feature
> repositories the features come from.
> 
> Entire closure of bundles → features → repositories is taken into account.
> 
> It's most important when creating custom Karaf distribution - we can check
> if some features declare conflicting bundles - we (usually) don't want to
> have two versions of servlet-api JAR installed (though it's not a problem
> with guava - it's even a must).
> 
> When a _duplicate_ is found or even duplicate repositories are referenced
> (directly or transitively) usually there's a need to _blacklist_ something.
> 
> With https://issues.apache.org/jira/browse/KARAF-5376 I've introduced a way
> (documentation is still being written...) to blacklist
> bundles/features/repositories or override bundles/features/repositories.
> 
> Blacklisting/overriding is done using etc/org.apache.karaf.features.xml
> file. Short summary of the mechanism is here:
> https://issues.apache.org/jira/browse/KARAF-5376?focusedCommentId=16431939=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16431939
> 
> In next email, I'll show what should/could be aligned in master branch for
> Karaf 4.2.3-SNAPSHOT.
> 
> regards
> Grzegorz Grzybek

> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf (runtime) 4.2.2 release

[Andrea Cosentino]

+1 (non-binding)

Thanks JB!

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Sunday, December 16, 2018, 11:18:51 AM GMT+1, Jean-Baptiste Onofré 
 wrote: 





Hi all,

Finally, after different new fixes and third party releases, I'm glad to
submit Karaf (runtime) 4.2.2 release to your vote. This is a major
maintenance release for 4.2.x series, bringing a lot of fixes &
improvements.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343458=12311140

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1123/

Git Tag:
karaf-4.2.2

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Bad commit https://github.com/apache/karaf/commit/62e832c7009b5b8beafd219ff7b6b66051205682

[Andrea Cosentino]

We may add a note also in the on the camel documentation in the github repo 
about this.

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Monday, December 3, 2018, 3:49:17 PM GMT+1, Jean-Baptiste Onofré 
 wrote: 





OK, I found the issue, it's related to property placeholder:

https://issues.apache.org/jira/browse/CAMEL-12570

So, it affects users when using property placeholder in the camel
blueprint route.

To work, users have to use at least Camel 2.21.2.

If an user still uses Camel 2.20.1, it won't work.

That's why I think it's better to:

1. stay with blueprint-core 1.9.x on Karaf 4.2.x
2. do a a new blueprint-core 1.9.1 release including the interceptor fix
we need for jpa

Thoughts ?

Regards
JB

On 03/12/2018 15:43, Jean-Baptiste Onofré wrote:
> I just tested camel-blueprint 2.20.1 with blueprint-core 1.10.0 and it
> seems to work: I deployed a simple camel route written using blueprint
> and it starts and works fine.
> 
> Does someone remember the issue we had with the blueprint-core upgrade
> with camel-blueprint ? Maybe it was with previous Camel version.
> 
> Regards
> JB
> 
> On 03/12/2018 15:26, Jean-Baptiste Onofré wrote:
>> Hi guys,
>>
>> A pull request has been merged on master (so for Karaf 4.2.2), but I
>> think it's not correct:
>>
>> https://github.com/apache/karaf/commit/62e832c7009b5b8beafd219ff7b6b66051205682
>>
>> This is an upgrade to blueprint-core 1.10.0. We already have a Jira
>> about that:
>>
>> https://issues.apache.org/jira/browse/KARAF-5942
>>
>> We can't update to blueprint 1.10.0 on Karaf 4.2.x without breaking the
>> Camel Blueprint support, which I think it's really bad.
>>
>> So, I think it would be better to revert this update and target
>> blueprint 1.10.0 to Karaf 4.3.x.
>>
>> Thoughts ?
>>
>> Regards
>> JB
>>
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Bad commit https://github.com/apache/karaf/commit/62e832c7009b5b8beafd219ff7b6b66051205682

[Andrea Cosentino]

+1.
--Andrea Cosentino --Apache Camel PMC 
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd 

On Monday, December 3, 2018, 3:27:00 PM GMT+1, Jean-Baptiste Onofré 
 wrote:  
 
 Hi guys,

A pull request has been merged on master (so for Karaf 4.2.2), but I
think it's not correct:

https://github.com/apache/karaf/commit/62e832c7009b5b8beafd219ff7b6b66051205682

This is an upgrade to blueprint-core 1.10.0. We already have a Jira
about that:

https://issues.apache.org/jira/browse/KARAF-5942

We can't update to blueprint 1.10.0 on Karaf 4.2.x without breaking the
Camel Blueprint support, which I think it's really bad.

So, I think it would be better to revert this update and target
blueprint 1.10.0 to Karaf 4.3.x.

Thoughts ?

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
  

R: [VOTE] Apache Karaf Cellar 4.0.5 release

[Andrea Cosentino]

+1(non-binding)
Thanks JB

Inviato da Yahoo Mail su Android 
 
  Il mar, 9 ott, 2018 alle 17:31, Jean-Baptiste Onofré ha 
scritto:   Hi all,

I submit Karaf Cellar 4.0.5 release to your vote. This release is a
maintenance release of the Cellar 4.0.x serie.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12340649

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1117/

Git Tag:
cellar-4.0.5

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
  

R: [VOTE] Apache Karaf Cellar 4.1.2 release

[Andrea Cosentino]

+1(non-binding)
Thanks JB

Inviato da Yahoo Mail su Android 
 
  Il mer, 10 ott, 2018 alle 8:05, Jean-Baptiste Onofré ha 
scritto:   Hi all,

I submit Karaf Cellar 4.1.2 release to your vote. This release is a
maintenance release of the Cellar 4.1.x serie.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12341724

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1118/

Git Tag:
cellar-4.1.2

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
  

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

[Andrea Cosentino]

+1.

Thanks JB






On Monday, September 24, 2018, 10:01:48 AM GMT+2, Jean-Baptiste Onofré 
 wrote: 





Hi guys,

based on what Guillaume started already, I moved forward during the week
end on OSGi R7 support in Karaf.

I think I will have something fully ready this week (during ApacheCon ;)).

Once my PR is ready, I propose the following plan:

- create the karaf-4.2.x branch with the current master
- bump version on master to 4.3.0-SNAPSHOT and merge the R7 PR
- "flag" 4.1.x branch as non active

Thoughts ?

By the way, I will be at ApacheCon Montréal from tomorrow up to Thursday
afternoon. If you want to meet, talk about Karaf and related, please let
me know !

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf Cave 4.1.1 release

[Andrea Cosentino]

+1 (non-binding)

Thanks for the release.

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Wednesday, September 5, 2018, 6:56:17 AM GMT+2, Jean-Baptiste Onofré 
 wrote: 





Hi,

I submit Apache Karaf Cave 4.1.1 release to your vote.

This is a maintenance release on Cave 4.1.x series (working on Karaf
4.0.x, 4.1.x and 4.2.x), before starting the upgrade to the next 4.2.x
series.
This release contains fixes on the Maven repository management, the
Feature gateway, the REST services (for both repository and deployer).

For complete details, please take a look on the release notes:

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12342356

Git tag:
cave-4.1.1

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1115/

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf "Container" 4.2.1 release

[Andrea Cosentino]

+1 (non-binding)

Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Saturday, August 18, 2018, 3:34:37 PM GMT+2, Jean-Baptiste Onofré 
 wrote: 





Hi,

I submit Apache Karaf 4.2.1 release to your vote.

This release is a major update on the 4.2.x series. It includes bunch of
dependencies updates, fixes and new features, especially:

- Better Java 9/10/11 support
- Assembly tooling to create Docker image, by the way, official Karaf
images will be available soon using these scripts
- Docker feature allowing you to manipulate Docker directly from Karaf
- Improved itest KarafTestSuport to create your own itests easily
- Updated dev guide with examples included in the Karaf standard
distribution (and using in the itests)

For complete details, please take a look on the release notes:

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12342945

Git tag:
karaf-4.2.1

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1114/

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

R: [VOTE] Apache Karaf (Container) 4.1.6 release

[Andrea Cosentino]

+1 (non-binding)
Thanks JB 
 
  Il ven, 3 ago, 2018 alle 19:20, Jean-Baptiste Onofré ha 
scritto:   Hi all,

I submit Karaf (Container) 4.1.6 release to your vote. This is a
maintenance release on 4.1.x series.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12342748

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1112/

Git Tag:
karaf-4.1.6

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
  

Re: Preparing Karaf 4.2.1 and some ideas

[Andrea Cosentino]

+1, great work!

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Sunday, June 17, 2018, 5:17:23 PM GMT+2, Jean-Baptiste Onofré 
 wrote: 





Hi guys,

As I started to prepare Karaf 4.2.1, I rebased and cleaned up the
examples. The corresponding PR is there:

https://github.com/apache/karaf/pull/484

As already mention on the mailing list, I gonna add new examples asked
by users. It seems also that lot of users has difficulties to create
their own Karaf distro. I will add new examples around that (there is
already one), and I think we can improve the karaf-maven-plugin to
simplify the way of creating distribution, and give the right example
(the generate MOJO is more a source of problem and we should encourage
users to write their features XML IMHO).

On the other hand, I started a branch where I refactored the README and
other documentation file to use the md format. The advantages of md
(compare to raw text or ascii doc) is that:
1. It can be rendered directly on github
2. The doxia maven plugin supports it by default (no need to use
asciidoc specific plugin)
3. It's a well known format

We are moving forward on this and other Jira (starting the triage right
now) and hopefully, Karaf 4.2.1 will be submitted to vote soon-"ish"
(middle of this week).

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

[Andrea Cosentino]

+1 (non-binding)
Thanks JB
--Andrea Cosentino --Apache Camel PMC 
MemberApache Karaf CommitterApache Servicemix PMC MemberEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd 

On Tuesday, April 3, 2018, 10:25:19 AM GMT+2, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote:  
 
 Hi all,

I submit Karaf (Container) 4.2.0 release to your vote.

This is the first GA on the 4.2.x series, following M1 and M2.

NB: I preferred to postpone the merge of the new examples as it needs a little
polish. The PR is already available and it will be included in 4.2.1 (that we
can expect beginning of May depending of 4.2.0 feedbacks):
https://github.com/apache/karaf/pull/484

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12342076

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1110/

Git Tag:
karaf-4.2.0

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
  

Re: compilation failing with karaf 4.2.0.M2

[Andrea Cosentino]

yes, you have to update it.

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, March 8, 2018, 2:45:05 PM GMT+1, shivibansal 
<shivanibansal1...@gmail.com> wrote: 





On my system, I have maven installed as 3.0.5.

but in the codebase pom files, I have changed properties to 
4.2.0.M2

4.2.0.M2

Shall i update the maven version on my system?


Regards
Shivani



--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-Dev-f930721.html

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

[Andrea Cosentino]

+1 (non-binding)

Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Monday, February 26, 2018, 10:43:41 AM GMT+1, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote: 





Hi all,

I submit Karaf (Container) 3.0.9 release to your vote. It's a maintenance
release, fixing several issues and bringing minor dependency updates.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12338081

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1109

Git Tag:
karaf-3.0.9

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Apache Karaf 4.2.0 GA

[Andrea Cosentino]

+1 

Thanks JB!

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Monday, February 19, 2018, 5:58:36 AM GMT+1, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote: 





Hi guys,

After 4.2.0.M1 & 4.2.0.M2, I think it's time to do the first 4.2.0 GA.

I have three actions on the way:

1. Upgrade to Pax Web 7 with Jetty 9.4 support. I started Pax Web/Jetty part on
a local branch. I hope to have something this week around that. It takes a
little bit of time because the Jetty API slightly changed (as usual). This point
is a blocker and 4.2.0 needs it. If you think it's worth to have a 4.2.0.M3 with
this update, please let me know.
2. Merge karaf-docker feature branch. It's something that we discussed days ago.
I updated and cleanup the code for donation. Not blocker but good to have.
3. Merge examples branch. In order to allow users to easily start with Karaf,
François and I are working on a set of examples
(https://github.com/jbonofre/karaf/tree/DEV_GUIDE/examples). The idea is to
include those examples in the Karaf distribution, linked them in the developer
guide. At the end, I would like to add itests using these examples as well,
allowing us to detect regression. Again not a blocker, but good to have. Please,
let me know what you are thinking about the examples. Some examples are in
development (take a look in the examples pom.xml for the list of examples).

Roughly, I would like to cut 4.2.0 in 2 weeks or so.

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

R: [VOTE] Apache Karaf Decanter 2.0.0 release, take 2

[Andrea Cosentino]

+1 (non-binding)
Thanks JB

Inviato da Yahoo Mail su Android 
 
  Il ven, 2 feb, 2018 alle 15:20, Jean-Baptiste Onofré ha 
scritto:   Hi all,

I submit Karaf Decanter 2.0.0 release to your vote.

This is the first release in the new Decanter 2.x series. It's designed to work
with Karaf >= 4.

It's an important release providing updated and new backends, a first round of
shell commands (to manage the alerting feature) and much more.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12341053

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1107/

Git Tag:
decanter-2.0.0

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
  

Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

[Andrea Cosentino]

Wasn't Pax-web 7 the version with Jetty 9.4.x support?

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, February 1, 2018, 7:53:49 AM GMT+1, Grzegorz Grzybek 
<gr.grzy...@gmail.com> wrote: 





Hello

On PAX-WEB side (and wrt PAX-CDI), I did some important, but norrow-scoped
changes related to pax-cdi integration. Generally pax-web-jetty now allows
to run JSF/CDI WARs without problems (at least MyFaces + Weld). There was
minor change needed in pax-web itself and a bit bigger change in pax-cdi.

I know pax-cdi is not that popular, but still - having 1.0.0.RCx for ~5
years now isn't nice ;)

As for pax-web 6.1.x upgrade to Jetty 9.4 - I'm OK, as (after I think I've
collected the right information here
<https://docs.google.com/spreadsheets/d/1TB_q5r9i8DOIHmBQa1_RjsrcjWCwCwsLPj3Pc6FoTJ8/edit#gid=1455909167>
- see both sheets) Jetty 9.4.x is still Servlets 3.1/JavaEE 7.

best regards
Grzegorz Grzybek

2018-01-31 20:59 GMT+01:00 Jean-Baptiste Onofré <j...@nanthrax.net>:

> Hi,
>
> a quick update on the release schedule.
>
> As you probably saw, I canceled the Decanter 2.0.0 vote today. I will fix
> the two pending issues: I should be able to submit a new 2.0.0 release to
> vote tomorrow.
>
> For Cellar releases, I need more time as some changes are wider than
> expected.
>
> Regarding "container", before 4.2.0 release (still planned in couple of
> weeks), I would like to prepare a 4.1.5 release pretty soon (probably for
> the weekend). We did good fixes and improvements valuable for users, so it
> makes sense to cut a release.
>
> Regards
> JB
>
>
> On 24/01/2018 15:38, Jean-Baptiste Onofré wrote:
>
>> Hi guys,
>>
>> Just a quick update about the coming releases.
>>
>> 1. Apache Karaf Decanter 2.0.0
>> I'm working right now on the Decanter 2.0.0 release. It's a major new
>> releases
>> (from the new Decanter 2.x series). We are on the right track for this
>> release,
>> I should be able to submit to vote during the weekend.
>>
>> 2. Karaf Cellar 4.0.4/4.1.2
>> Some PRs have been merged and I'm reviewing a larger PR. I also have
>> several
>> fixes and little improvements on the way. I plan to submit releases to
>> vote in
>> roughly 2 weeks.
>>
>> 3. Karaf "Container" 4.2.0
>> After 4.2.0.M1 and 4.2.0.M2, I think we are pretty close to 4.2.0
>> release. We
>> still have 18 issues to qualify and eventually fix for this release. One
>> of
>> important one is that we have to upgrade to Pax Web 6.1.2 that should
>> upgrade to
>> Jetty 9.4.6. It's important to be aligned with latest Camel releases.
>> So, I started the Jira triage and also started the Pax Web Jetty ugprade.
>> I don't have strong dates in mind for now but hopefully, we should be
>> able to
>> cut 4.2.0 in roughly 2 weeks.
>>
>> Regards
>> JB
>>
>>

Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

[Andrea Cosentino]

Thanks JB

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Wednesday, January 24, 2018, 3:38:22 PM GMT+1, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote: 





Hi guys,

Just a quick update about the coming releases.

1. Apache Karaf Decanter 2.0.0
I'm working right now on the Decanter 2.0.0 release. It's a major new releases
(from the new Decanter 2.x series). We are on the right track for this release,
I should be able to submit to vote during the weekend.

2. Karaf Cellar 4.0.4/4.1.2
Some PRs have been merged and I'm reviewing a larger PR. I also have several
fixes and little improvements on the way. I plan to submit releases to vote in
roughly 2 weeks.

3. Karaf "Container" 4.2.0
After 4.2.0.M1 and 4.2.0.M2, I think we are pretty close to 4.2.0 release. We
still have 18 issues to qualify and eventually fix for this release. One of
important one is that we have to upgrade to Pax Web 6.1.2 that should upgrade to
Jetty 9.4.6. It's important to be aligned with latest Camel releases.
So, I started the Jira triage and also started the Pax Web Jetty ugprade.
I don't have strong dates in mind for now but hopefully, we should be able to
cut 4.2.0 in roughly 2 weeks.

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [PROPOSAL] Docker feature in Karaf container

[Andrea Cosentino]

+1 :-)

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Thursday, January 18, 2018, 10:38:03 AM GMT+1, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote: 





Hi,

Some days ago, we discussed about Decanter 2.0.0 and using "external" instances 
of used engines,  like Elasticsearch or Kibana.

Basically, the main reason is that some engines are not easy to embed in Karaf. 
It's the case of Kibana as it uses node.js.

However, one of the big advantage of embedded instance of Elasticsearch or 
Kibana is that it's very easy to install and use: it's just a feature:install 
command to perform.

So, I would like to provide both advantages: easy to install and use with 
external instances ;)

A first approach would be to create a "exec" bundle starting the instance. But 
we gonna face the "classic" issues depending of the environment.

Maybe some of you remember the karaf-docker PoC I did month ago:

https://github.com/jbonofre/karaf-docker

This is a simple feature that allows you to manipulate docker images: 
bootstrapping, starting/running, ...

I think it would help a lot in Decanter or Cellar: we can just provide Karaf 
Docker commands to bootstrap Elasticsearch, Kibana, OrientDB, ...
As a best effort, we will try to provide embedded instance as possible, but it 
won't be the preferred approach.

As karaf-docker is small project and just basically use docker, I think it 
doesn't require to be a Karaf subproject.
As we have the karaf scheduler (using Quartz internally), I would like to 
propose to add docker in Karaf container in a dedicated module.

It means that users will be able to do feature:install docker to have the 
docker 
commands.
I would like also to add a command and configuration to have "ready to go 
images". Something that will allow users to do:

docker:run elasticsearch

then, elasticsearch will use a ready to go dockerfile.

It would be possible to do:

docker:run mvn:org.apache.karaf.decanter.docker/elasticsearch/6.1.0/docker

Where we can host ready to use "official" dockerfile.

Thoughts ?

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [PROPOSAL] Apache Karaf Decanter 2.0.0

[Andrea Cosentino]

+1.

Thanks JB.

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Monday, January 8, 2018, 2:25:34 PM GMT+1, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote: 





Hi,

I'm working on the preparation of the next Decanter release.

I would like to bump Decanter version to 2.0.0 for the following reasons:

1. Upgrade to OSGi Spec 6.0.0, especially for Compendium & DS. It means that 
Decanter 2.0.0 will require Karaf >= 3.0.0.
2. Up to now, Decanter provided embedded feature for Elasticsearch, Kibana, 
OrientDB. Those features will still be present in Decanter and they won't be 
the 
recommended approach. We encourage users to use external instances for 
production. For instance, Kibana 6 is not easy to ship in Karaf (due to 
node.js), and I think it's more reliable to use a "native" Kibana instance.
3. We will introduce new webconsole and shell commands for Decanter. It will be 
base on Karaf 4 style.

Thoughts ?

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

[Andrea Cosentino]

+1 (non-binding).

Thanks JB!

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Saturday, December 16, 2017, 7:23:58 AM GMT+1, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote: 





Hi all,

I submit Karaf (Container) 4.1.4 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12341702

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1102/

Git Tag:
karaf-4.1.4

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

[Andrea Cosentino]

+1 (non-binding).

Thanks JB.

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Friday, October 27, 2017, 6:08:16 AM GMT+2, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote: 





Hi all,

I submit Karaf (Container) 4.1.3 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12341130

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1100/

Git Tag:
karaf-4.1.3

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 48 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [DISCUSS] Trim down karaf distributions for 4.2

[Andrea Cosentino]

+1, it makes sense.
Cheers,
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd




 
 
 On Wednesday, October 11, 2017, 3:01:07 PM GMT+2, Guillaume Nodet 
<gno...@apache.org> wrote: 





The point that makes me raise this problem is that the karaf default
distribution uses the Apache versions of xerces and xalan.  Fwiw, the
latest xerces release is from 2011 and the latest xalan from 2014, so
they're not the most active.  In particular, xalan latest release does not
implement jaxp 1.4.

One additional point is that those libraries stuff is broken on Java 9, so
one option would be to remove it alltogether which bring us much closer to
Java 9 support ;-)  Seriously, I'm not sure I want to spend too much time
allowing pluggability for specs/implementations while the only real
implementation provider is the JDK itself.  That's really a lot of work for
no real benefit.

In addition, the default distribution still install some "legacy" features
such as aries-blueprint, shell-compat, etc...

So here's a list of propositions for 4.2:
  * remove all libraries for specs / impls from apache-karaf distro
  * remove support for endorsed / ext libraries in the  element
and wherever used
  * remove aries-blueprint and shell-compat from default distro
  * remove a few features from the karaf-minimal distro. I'm not sure which
one exactly, but I think we should get the zip under 10 Mb.  Maybe only
keeping jaas, shell, feature, ssh, bundle, config, deployer and log, also
removing equinox / logback bundles...

Thoughts ?

-- 

Guillaume Nodet

Re: [VOTE] Apache Karaf Cellar 4.1.1 release

[Andrea Cosentino]

+1 (non-binding)
Thanks JB
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd




 
 
 On Saturday, October 7, 2017, 11:50:25 AM GMT+2, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote: 





Hi all,

I submit Karaf Cellar 4.1.1 release to your vote. This is a maintenance release 
on 4.1.x series.
This release brings an important bug fixes for cluster:features* commands and 
dependency updates.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12340615

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1099/

Git Tag:
cellar-4.1.1

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

[Andrea Cosentino]

+1 (non-binding).

Thanks JB.

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, August 4, 2017, 8:51:20 PM GMT+2, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote:


Hi all,

I submit Karaf (Container) 4.1.2 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12340261

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1097/

Git Tag:
karaf-4.1.2

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 48 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf Decanter 1.4.0 release

[Andrea Cosentino]

+1 (non-binding).
Thanks JB.
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, July 17, 2017, 3:02:34 PM GMT+2, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote:


Hi all,

I submit Karaf Decanter 1.4.0 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12338800

Git tag:
decanter-1.4.0

Staging repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1096/

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf Decanter 1.4.0 release

[Andrea Cosentino]

+1 (non-binding).
Thanks JB
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, July 4, 2017, 8:40:38 AM GMT+2, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote:


Hi all,

I submit Karaf Decanter 1.4.0 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12338800

Git tag:
decanter-1.4.0

Staging repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1094/

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf Cellar 4.0.4 release

[Andrea Cosentino]

+1 (non-binding)

Thanks JB 
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd


On Thursday, May 11, 2017 11:08 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:



Hi all,


I submit Karaf Cellar 4.0.4 release to your vote. This release is a maintenance 

release of the Cellar 4.0.x serie.


Release Notes:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12338929


Staging Repository:

https://repository.apache.org/content/repositories/orgapachekaraf-1093/


Git Tag:

cellar-4.0.4


Please vote to approve this release:


[ ] +1 Approve the release

[ ] -1 Don't approve the release (please provide specific comments)


This vote will be open for at least 72 hours.


Thanks,

Regards

JB

-- 

Jean-Baptiste Onofré

jbono...@apache.org

http://blog.nanthrax.net

Talend - http://www.talend.com

Re: [VOTE] Apache Karaf Cellar 4.1.0 release

[Andrea Cosentino]

+1 (non-binding).

Thanks JB
 
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd


On Thursday, May 11, 2017 8:12 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:



Hi all,


I submit Karaf Cellar 4.1.0 release to your vote. This release is the first one 

in the Cellar 4.1.x serie, fully compatible with Karaf 4.1.x (and 4.2.x).


Release Notes:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12340376


Staging Repository:

https://repository.apache.org/content/repositories/orgapachekaraf-1092/


Git Tag:

cellar-4.1.0


Please vote to approve this release:


[ ] +1 Approve the release

[ ] -1 Don't approve the release (please provide specific comments)


This vote will be open for at least 72 hours.


Thanks,

Regards

JB

-- 

Jean-Baptiste Onofré

jbono...@apache.org

http://blog.nanthrax.net

Talend - http://www.talend.com

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

[Andrea Cosentino]

+1 (non-binding)
Thanks JB! --Andrea Cosentino --Apache Camel 
PMC MemberApache Karaf CommitterApache Servicemix PMC MemberEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd 

On Wednesday, March 29, 2017 8:46 AM, Grzegorz Grzybek 
<gr.grzy...@gmail.com> wrote:
 

 +1 (non-binding)

regards
Grzegorz Grzybek

2017-03-29 8:43 GMT+02:00 Toni Menzel <toni.men...@rebaze.com>:

> +1 (non-binding)
>
> We are using 4.1.1-SNAPSHOT for a while now without any blocking issue. So
> 4.1.1 would be great to have. ;)
> Thanks, all!
> Toni
>
>
>
> *www.rebaze.de <http://www.rebaze.de/> | www.rebaze.com
> <http://www.rebaze.com/> | @rebazeio <https://twitter.com/rebazeio>*
>
> On Wed, Mar 29, 2017 at 8:03 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
>
> > Hi Stephan,
> >
> > yes, it's a known issue, but we need a new jline release to be able to
> > customize the color scheme (and users will be able to do so as well). It
> > should be included in 4.1.2.
> >
> > Regards
> > JB
> >
> >
> > On 03/29/2017 07:51 AM, Siano, Stephan wrote:
> >
> >> Hi,
> >>
> >> I don't think that this is a showstopper, but the release has still very
> >> strange console color effects on windows:
> >>
> >> How to reproduce:
> >>
> >> 1. download the zip file from https://repository.apache.org/
> >> content/repositories/orgapachekaraf-1090/org/apache/karaf/
> >> apache-karaf/4.1.1/ and unzip it somewhere on a Windows 10 system.
> >> 2. double click on bin/karaf.bat. The server will start and you will get
> >> a console
> >> 3. If you type anything into the console it will be dark red on black
> >> ground (which is hardly readable). Once a command is complete, it will
> turn
> >> dark blue on black ground (which is even more unreadable). Parameters
> >> entered to the commands are light grey on black ground, but error
> messages
> >> are in the same almost unreadable red as the incomplete commands. I
> tried
> >> to change the terminal background to white and the text to black but
> this
> >> only makes things worse because the blue and black letters still have a
> >> black background (so you get black bars on your white background with
> >> letters in it which are much less readable than before).
> >>
> >> Is it possible that these color effects were only tested with terminals
> >> where the default color is black on white background? Is there a way to
> >> disable these effects (I can live without any syntax highlighting if I
> can
> >> read the texts instead)?
> >>
> >> Best regards
> >> Stephan
> >>
> >> -Original Message-
> >> From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
> >> Sent: Dienstag, 28. März 2017 22:12
> >> To: Karaf Dev <dev@karaf.apache.org>
> >> Subject: [VOTE] Apache Karaf (Container) 4.1.1 release
> >>
> >> Hi all,
> >>
> >> I submit Karaf (Container) 4.1.1 release to your vote.
> >>
> >> Release Notes:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> >> ctId=12311140=12339244
> >>
> >> Staging Repository:
> >> https://repository.apache.org/content/repositories/orgapachekaraf-1090/
> >>
> >> Git Tag:
> >> karaf-4.1.1
> >>
> >> Please vote to approve this release:
> >>
> >> [ ] +1 Approve the release
> >> [ ] -1 Don't approve the release (please provide specific comments)
> >>
> >> This vote will be open for at least 48 hours.
> >>
> >> Thanks,
> >> Regards
> >> JB
> >>
> >>
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>

   

Re: Board report March '17

[Andrea Cosentino]

Looks good!

Thanks JB!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, March 9, 2017 6:17 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

I've prepared the board report for this month:

https://cwiki.apache.org/confluence/display/KARAF/Board+Reports

Please, take a look and let me know if you have any comments or points 
to add.

I would like to send the board report later today.

Thanks
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf (Container) 4.1.0 release, RC#2

[Andrea Cosentino]

+1.

Thanks JB
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, February 1, 2017 8:32 PM, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote:
Hi all,

I submit Karaf (Container) 4.1.0 release (second attempt) to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12332799

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1089/

Git Tag:
karaf-4.1.0

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 48 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Towards Karaf (Container) 4.1.0

[Andrea Cosentino]

+1.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, January 30, 2017 1:39 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi,

I confirm the "jline" commands are now working fine.

So, I will release 4.1.0.

As part of the 4.1.0, I would like to include examples (I have some more 
in preparation that I gonna merge) in the standard distribution:

https://github.com/jbonofre/karaf/tree/DEV_GUIDE/examples

We will improve and extend the examples (and dev guide) for 4.1.1.

WDYT ?

Regards
JB


On 01/30/2017 11:05 AM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> Guillaume fixed the shell backward compatibility this morning.
>
> I'm testing the fix now and if it's good, I will directly do a 4.1.0
> release.
>
> Thanks !
> Regards
> JB
>
> On 01/29/2017 01:38 PM, Jean-Baptiste Onofré wrote:
>> A quick new update related to the first Karaf 4.1.x release.
>>
>> 1. Jenkins build
>> I fixed the Jenkins jobs for both master and karaf-4.0.x:
>>
>> https://builds.apache.org/view/K/view/Karaf/
>>
>> I also removed the job for karaf-3.0.x.
>>
>> The build are now fully OK, including itests.
>> It's important to keep this build clean. I encourage you to check the
>> result of the build after your commits. If you have any doubt before
>> committing, we still have the PR validation job. So, you can create a
>> pull request that will be validated by Jenkins. Then, you can merge your
>> PR branch.
>>
>> 2. Shell command issue
>> Several projects providing shell commands (like Camel, ActiveMQ, ...)
>> directly use jline dependency. It's pretty bad (they should use the
>> Karaf "wrapper), and, as Karaf 4.1.x now uses JLine 3.x, those commands
>> don't work in Karaf 4.1.x.
>> Here, we have two solutions:
>> 2.1. We create the jline "2.x" compliant packages in Karaf (in a bundle
>> as part of the shell-compat feature for instance). It's only a
>> workaround but should fix the issue.
>> 2.2. jline 3.x can provide a "compat" bundle with the jline 2.x packages
>> name, wrapping the jline 3.x ones. It's probably the most elegant
>> solution, but it's require a new jline 3.x release.
>>
>> 3. Version & Schedule
>> Basically, I planned to release 4.1.0-M1 version today, as shell command
>> "break" is pretty bad. I'm postponing the decision to tomorrow evening.
>> I plan to discuss with Guillaume tomorrow about the jline 3 and shell
>> commands issue. If we can find a good solution, and release jline 3.1.3
>> tomorrow, then, I will release Karaf 4.1.0 tomorrow evening.
>> If it's more complex and requires more time, then, I will release
>> 4.1.0-M1 tomorrow evening, the 4.1.0 (GA) will be released 3 weeks
>> later, giving time for us to fix the jline/command issue.
>>
>> Thanks !
>> Regards
>> JB
>>
>> On 01/29/2017 11:31 AM, Jean-Baptiste Onofré wrote:
>>> Hi all,
>>>
>>> the problem is clearly an incompatible version of jline (resulting of
>>> the update we did in Karaf 4.1.x). It breaks other projects which are
>>> using directly jline (for completer for instance).
>>>
>>> So, the other projects should be refactored (camel, activemq, ...) to
>>> not relay on jline but Karaf (for the completer for instance).
>>>
>>> Anyway, it means that Karaf 4.1.0 is not yet ready to support any other
>>> projects.
>>>
>>> So, I'm going to 4.1.0-M1 first and we will invite maximum of people to
>>> test on this milestone in order to clearly identify the breaking changes
>>> and provide max backward compatibility when possible.
>>>
>>> I already changed the version in Jira and I will cut 4.1.0-M1 later
>>> today.
>>>
>>> Regards
>>> JB
>>>
>>> On 01/28/2017 03:32 PM, Jean-Baptiste Onofré wrote:
>>>> Hi guys,
>>>>
>>>> as you might know, I'm preparing the Karaf 4.1.0 release.
>>>>
>>>> We are mostly ok, but during my tests, I found that Camel (at least
>>>> 2.18.1) commands are not available in the shell.
>>>>
>>>> I suspect because they use the "old" style.
>>>>
>>>> I also see lot of small annoying behaviors in the shell console (on
>>>> completion especially).
>>>>
>>>> So, even we are mostly ready, I'm not sure it's fully ready for
>>>> production.
>>

R: Re: karaf git commit: Revert to 3.2.17 as some 3.2.18 spring bundles are missing in central

[Andrea Cosentino]

They are 
 
  Il mer, 25 gen, 2017 alle 12:54, Jean-Baptiste Onofré ha 
scritto:   Gonna check but they should be on central.⁣​

On Jan 25, 2017, 12:42, at 12:42, cschnei...@apache.org wrote:
>Repository: karaf
>Updated Branches:
>  refs/heads/master cae112943 -> e4b2b45d2
>
>
>Revert to 3.2.17 as some 3.2.18 spring bundles are missing in central
>
>
>Project: http://git-wip-us.apache.org/repos/asf/karaf/repo
>Commit: http://git-wip-us.apache.org/repos/asf/karaf/commit/e4b2b45d
>Tree: http://git-wip-us.apache.org/repos/asf/karaf/tree/e4b2b45d
>Diff: http://git-wip-us.apache.org/repos/asf/karaf/diff/e4b2b45d
>
>Branch: refs/heads/master
>Commit: e4b2b45d225b1d88076919633604aeafab4c1323
>Parents: cae1129
>Author: Christian Schneider 
>Authored: Wed Jan 25 12:42:32 2017 +0100
>Committer: Christian Schneider 
>Committed: Wed Jan 25 12:42:32 2017 +0100
>
>--
> pom.xml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>--
>
>
>http://git-wip-us.apache.org/repos/asf/karaf/blob/e4b2b45d/pom.xml
>--
>diff --git a/pom.xml b/pom.xml
>index 429dc7a..971e391 100644
>--- a/pom.xml
>+++ b/pom.xml
>@@ -273,7 +273,7 @@
> 
>        1.2.1
>        3.1.4.RELEASE
>-        3.2.18.RELEASE_1
>+        3.2.17.RELEASE_1
>        4.0.7.RELEASE_3
>        4.1.9.RELEASE_1
>        4.2.9.RELEASE_1
  

R: [PROPOSAL] Add convenient and "starter" examples in Karaf Container distribution

[Andrea Cosentino]

+1.
Thanks JB 
 
  Il dom, 15 gen, 2017 alle 19:15, Jean-Baptiste Onofré ha 
scritto:   Hi guys,

In the preparation for the Karaf 4.1.0 release, I'm working on the final 
touches on the developer guide.

As part of this, I created simple example projects:
- Service with pure OSGi (registration/reference)
- Configuration management with ConfigAdmin service
- Configuration with ManagedService
- Configuration with ManagedServiceFactory
- Service with Blueprint (registration/reference)
- Service with DS/SCR (registration/reference)
- Create a custom Command
- Create a custom MBean
- Create a custom URL NamespaceHandler
- Logging custom appender
- Create a custom deployer
- Create a custom JAAS LoginModule
- Security realm usage
- Encryption service usage
- Create a servlet
- Create a WAB and use service
- Use Karaf JNDI
- Use and manipulate JDBC service
- Use and manipulate JMS service
- Use of JPA & JTA
- Use of CDI
- Use of CXF for WebServices (very quick and simple, README is 
referencing CXF website/samples)
- Use of Camel in Karaf (very quick and simple, README is referencing 
Camel website/samples)
- Profiles

I tried basically to list the most common questions/requests we got from 
users when they start with Karaf.

These samples and new developer guide are already ready, I will create a 
pull request tonight or Tuesday (I'm traveling tomorrow).

I did:
- a samples module containing those samples, including a README for each 
sample
- moved the content of demo in samples (demo is removed)
- updated the developer guide based on README in those samples
- add new archetypes ("starter") to create the code of the samples too

The idea is to provide quick ways (starters) for end-users to start with 
Karaf, providing practical samples. It's a first start/transition 
waiting for Karaf Boot. However, as Karaf Boot

I plan to add the same things in Decanter (create custom collector, 
appenders, alerters, ...) and Cellar (use of distribution map, DOSGi, ...).

Thoughts ?

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
  

Re: Board Report for January '17

[Andrea Cosentino]

I don't have Karma to edit the docs so I wrote in the mailing list.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, January 5, 2017 3:51 PM, Andrea Cosentino 
<ancosen1...@yahoo.com.INVALID> wrote:
In the Activity section you can also add


- We are beginning the work for a full JDK9 support, we expect to achieve the 
result in release 4.2.0

Maybe in the health report you can talk about the security fixes we did in the 
last month. 
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, January 5, 2017 3:37 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:



Hi guys,

gently reminder as I would like to send the board report tomorrow.

Thanks,
Regards
JB


On 01/04/2017 08:05 AM, Jean-Baptiste Onofré wrote:
> Hi guys,
>
> The board provided comments on the last board report. Basically, the
> board asked for some details:
>
> "
> Comments:
>
>   idf: While the project seems healthy from the raw numbers provided,
>this report needs a few more sentences on community health to
>be really helpful.
>
>   mh: +1 to Isabel's comment. Some sort of narrative would be helpful.
>   Who is participating in development -- are there many or few? Is
>   the community turbulent or steady?
> "
>
> I asked to report this month to address these comments and provide a
> more complete report.
>
> I started a board report draft here:
>
> https://cwiki.apache.org/confluence/display/KARAF/Board+Reports
>
> adding more narrative content.
>
> Please, take a look and complete with couple of sentences in the "TODO"
> section.
>
> I would like to send the board report by the end of this week.
>
> Thanks !
> Regards
> JB

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Karaf 4.1 and JDK9

[Andrea Cosentino]

+1.

It looks like we'll have a lot of work to do to have a full JDK9 support.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, January 4, 2017 1:34 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi Achim,

For Karaf 4.1, the purpose is not to fully support JDK9 but to start the 
required improvements.

I plan to release Karaf 4.1.0 by the end of this week as it is, with 
full JDK8 support, and JDK9 support preview (not fully tested).

I would consider the full JDK9 support for Karaf 4.2. I'm pretty sure 
that other projects (Pax Web as you said, but also Aries Proxy) are not 
fully ready, so, it's not really possible to announce a full JDK9 support.

My plan is to create the karaf-4.1.x branch tomorrow, and then, prepare 
the full JDK9 support on master.

Thoughts ?

Regards
JB


On 01/04/2017 01:25 PM, Achim Nierbeck wrote:
> Hi,
>
> got a question regarding Karaf 4.1 and JDK9 compatibility.
> I've seen we had numerous issues regarding JDK9 for Karaf 4.1.
> Is it our goal to have Karaf 4.1 runnable with JDK9?
> If so, the ops4j community just came across some major drawbacks.
>
> First it just seemed like we just need to bump the version for ASM in
> Pax-Web [1][2][3] and everything is smooth, but it's not.
>
> It turned out we also need another upgrade for ASM 6 in Aries [4], but
> again this isn't the only thing.
>
> It turns out, Jetty 9.3.x isn't compatible with JDK9, so an upgrade to
> Jetty 9.4 might be needed.
> Again this turns out to be more complex then first anticipated.
> As it turns out, neither Jetty 9.3 nor 9.4 are ready to go for ASM 6, but
> still rely on version 5 [5].
> Not to speak of the need to bump Pax-Web to version 6.1 for using Jetty
> 9.4.
>
> So how do we handle JDK9 for Karaf 4.1?
> Is it our main goal to support JDK9 from head start?
> If the answer is yes, we need to do a lot more then what we've done so far.
> Just to mention one thing that needs to be done instantly, have a build
> which uses JDK9 to run our tests. That should already cover most of the
> issues we came across.
> Also I would like to hold back the release for 4.1 for a while to make sure
> we have all project we or our users depend on straightened for JDK9.
>
>
> regards, Achim
>
> [1] - https://issues.apache.org/jira/browse/KARAF-4912
> [2] - https://ops4j1.jira.com/browse/PAXWEB-1047
> [3] - https://issues.apache.org/jira/browse/KARAF-4913
> [4] - https://issues.apache.org/jira/browse/ARIES-1646
> [5] -
> https://ops4j1.jira.com/browse/PAXWEB-1047?focusedCommentId=39702=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-39702
>
>

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

[Andrea Cosentino]

+1 (non-binding)

Thanks JB
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, December 14, 2016 9:49 AM, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote:
Hi all,

I submit Karaf (Container) 4.0.8 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12338273

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1085/

Git Tag:
karaf-4.0.8

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [DISCUSS] & in feature (KARAF-4829)

[Andrea Cosentino]

I guess this is the only way.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, December 8, 2016 3:43 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
It means that we have to check on the final name (not the URL). And on the 
final name we have to check the target subfolder (cfg goes in etc but we can 
put something in bar folder using configfile for instance) and the extension of 
the final name (.cfg).

Regards
JB⁣​


On Dec 8, 2016, 15:35, at 15:35, Guillaume Nodet <gno...@apache.org> wrote:
>Instead of trying to guess the format of the config file, we could
>simpy
>use the extension I think.
>The  element has both the file name and the url.  So if the
>file name ends with ".cfg", we assume we can write the content to
>configadmin directly.  I'm not sure I see a real problem here.
>
>2016-12-08 15:28 GMT+01:00 Guillaume Nodet <gno...@apache.org>:
>
>>
>>
>> 2016-12-08 15:27 GMT+01:00 Jean-Baptiste Onofré <j...@nanthrax.net>:
>>
>>> Yes, Achim already replied and I fully agree.
>>>
>>> So, I wonder if it makes sense to do ConfigAdmin configuration
>creation
>>> for  as it would require to detect file format.
>>>
>>> Can we document that way:
>>> 1. for cfg file, we recommend to use  in feature XML
>>> 2. for any other file format, we recommend to use  in
>>> feature XML
>>> ?
>>>
>>
>> That sounds to me the exact reason why we create those two elements
>in the
>> first place. ;-)
>>
>>
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 12/08/2016 03:24 PM, Guillaume Nodet wrote:
>>>
>>>> The  element supports  any kind of configuration file,
>not
>>>> only
>>>> properties file.  For example we use it for the xml configuration
>of
>>>> jetty
>>>> in pax-web.
>>>>
>>>> 2016-12-08 15:08 GMT+01:00 Jean-Baptiste Onofré <j...@nanthrax.net>:
>>>>
>>>> Hi guys,
>>>>>
>>>>> Some weeks ago we discussed on the mailing list about the fact
>that a
>>>>> feature using  just creates the cfg file in the etc
>folder,
>>>>> and the corresponding configuration is created later by
>ConfigAdmin
>>>>> (thanks
>>>>> to FileInstall).
>>>>> This can produce unfortunate behavior as the bundles in the
>feature can
>>>>> be
>>>>> started before the creation of the configuration in ConfigAdmin.
>>>>> Christian proposes to create the configuration in ConfigAdmin as
>soon as
>>>>> the FeatureService deals with  tag.
>>>>>
>>>>> On the other hand, in Karaf 4.0.5, we improved the  tag:
>the
>>>>> FeatureService now creates the corresponding cfg file in etc based
>on
>>>>> the
>>>>>  tag content.
>>>>>
>>>>> So, with KARAF-4829, we will have the same behavior using
> and
>>>>> :
>>>>> *  will create the configuration in ConfigAdmin and the
>cfg
>>>>> file
>>>>> *  will create the cfg file and the configuration in
>>>>> ConfigAdmin
>>>>>
>>>>> The difference is where the configuration comes from:
>>>>> - an existing file (mvn URL) in the case of 
>>>>> - inner properties in the case of 
>>>>>
>>>>> I wonder:
>>>>> 1. does it make sense to have both  and  in
>the
>>>>> future (Karaf 4.1.x) ?
>>>>> 2. should we do the change on  in Karaf 4.0.x ?
>>>>>
>>>>> Thoughts ?
>>>>>
>>>>> Regards
>>>>> JB
>>>>> --
>>>>> Jean-Baptiste Onofré
>>>>> jbono...@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>>
>>
>> --
>> 
>> Guillaume Nodet
>> 
>> Red Hat, Open Source Integration
>>
>> Email: gno...@redhat.com
>> Web: http://fusesource.com
>> Blog: http://gnodet.blogspot.com/
>>
>>
>
>
>-- 
>
>Guillaume Nodet
>
>Red Hat, Open Source Integration
>
>Email: gno...@redhat.com
>Web: http://fusesource.com
>Blog: http://gnodet.blogspot.com/

Re: Board Report for December 2016

[Andrea Cosentino]

+1 for me.

Thanks JB
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Saturday, December 3, 2016 8:19 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi guys,

I prepared the board report for December 2016:

https://cwiki.apache.org/confluence/display/KARAF/Board+Reports

Can you please take a look and update ?

I would like to send asap.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Next releases

[Andrea Cosentino]

+1. Thanks for your hard work.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, November 21, 2016 2:17 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi guys,

now that ApacheCon is done, and regarding some dependencies new releases 
(especially Pax URL 2.5.1), I think we can move forward on releases.

I propose the following schedule:

Karaf Container 4.0.8 by the end of this week. The important issue to 
fix is the support of ARM and Solaris (jansi).
Karaf Container 3.0.9 beginning of next week (waited by ServiceMix).

Karaf Decanter 1.3.0 should come end of this week or next one.

I think it makes sense to plan Karaf Container 4.1.0.RC1 by the end of 
this year (so in the coming month).

Regarding blog post, it is ready but as I'm changing blog system (from 
wordpress to bloggers) it will be published next week (migrating other 
content).

Thoughts ?

Regards
JB


On 10/10/2016 07:43 AM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> Just a rough schedule for the next release:
>
> - in the coming two weeks (probably end of this week or next one):
> -- Cellar 4.0.3 (including support of bundles and features update,
> hazelcast upgrade and other bug fixes)
> -- Decanter 1.3.0 (elasticsearch upgrade, fix on kafka appender, new
> features)
> - in two weeks:
> -- Container 4.0.8: the ARM/Solaris issue should be fixed now (that was
> an important regression in 4.0.6 & 4.0.7). Other fixes and upgrades are
> coming too.
>
> Blog:
> - Karaf & Cellar with Mesos and Marathon: last week, I prepared a blog
> post showing how to use Karaf and Cellar on Mesos and Marathon. I will
> push on my github the dockerfile and marathon json. I will propose the
> docker image as official (based on alpine/jre).
> I planned to do a talk based on that during ApacheCon but my talk
> proposal has been declined.
> I plan to publish this post during the week end.
>
> Regards
> JB

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf Decanter 1.3.0 release

[Andrea Cosentino]

+1 (non-binding).

Thanks JB
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, November 2, 2016 8:12 AM, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote:
Hi all,

I submit Karaf Decanter 1.3.0 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12338064

Git tag:
decanter-1.3.0

Staging repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1077/

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf Cellar 4.0.3 release

[Andrea Cosentino]

+1 (non-binding).

Thanks JB!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, October 20, 2016 8:51 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

I submit Apache Karaf Cellar 4.0.3 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12338324

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1076/

Git Tag:
cellar-4.0.3

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: The future of gemini-blueprint

[Andrea Cosentino]

+1 (non-binding) to remove it.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, October 17, 2016 11:42 AM, Christian Schneider 
<ch...@die-schneider.net> wrote:
+1 to remove it.

Christian


On 17.10.2016 11:33, Grzegorz Grzybek wrote:
> Hello
>
> I've created https://issues.apache.org/jira/browse/KARAF-4774 to consider
> deprecation/removal of gemini-blueprint support.
>
> I had this idea after reviewing Maven usage in Karaf4. Currently there's
> following configuration of remote repositories:
>
> org.ops4j.pax.url.mvn.repositories= \
>>  http://repo1.maven.org/maven2@id=central, \
>>
>> http://repository.springsource.com/maven/bundles/release@id=spring.ebr.release,
>> \
>>
>> http://repository.springsource.com/maven/bundles/external@id=spring.ebr.external,
>> \
>>  http://zodiac.springsource.com/maven/bundles/release@id=gemini, \
>>
>> http://repository.apache.org/content/groups/snapshots-group@id=apache@snapshots@noreleases,
>> \
>>
>> https://oss.sonatype.org/content/repositories/snapshots@id=sonatype.snapshots.deploy@snapshots@noreleases,
>> \
>>
>> https://oss.sonatype.org/content/repositories/ops4j-snapshots@id=ops4j.sonatype.snapshots.deploy@snapshots@noreleases,
>> \
>>
>> http://repository.springsource.com/maven/bundles/external@id=spring-ebr-repository@snapshots@noreleases
>>
>   4 repositories are SpringSource ones and FAQ on their site says:
>
> *What is the current status of the repository?*
>> The repository is frozen but will remain accessible *until at least 1
>> September 2014*. See http://www.eclipse.org/ebr/ for information
>> regarding the Eclipse Bundle Recipes project to which users of the
>> SpringSource Enterprise Bundle Repository should transition.
>>
> These 4 (3 for non-snapshots) repositories are queried during all
> Maven/Aether resolutions.
>
> Maybe it's time to remove gemini-blueprint? What do you think?
>
> best regards
> Grzegorz Grzybek
>


-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Re: [HEADS UP] Karaf (Container) 4.0.7 for the end of this week

[Andrea Cosentino]

Thanks JB
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, September 15, 2016 7:28 AM, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote:
Hi all,

as discussed during Karaf (Container) 4.0.6 vote, I plan to cut the 
4.0.7 release end of this week.

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf Cellar 4.0.2 release (2nd take)

[Andrea Cosentino]

+1 (non-binding)

Thanks JB
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, September 9, 2016 3:04 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

I submit Karaf Cellar 4.0.2 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12337886

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1074/

Git Tag:
cellar-4.0.2

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

[Andrea Cosentino]

+1 (non-binding).

Thanks JB!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, August 24, 2016 10:17 AM, Guillaume Nodet <gno...@apache.org> 
wrote:
+1


2016-08-24 6:47 GMT+02:00 Jean-Baptiste Onofré <j...@nanthrax.net>:

> Hi all,
>
> I submit Karaf (Container) 4.0.6 release to your vote.
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12311140=12335477
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1071/
>
> Git Tag:
> karaf-4.0.6
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>



-- 

Guillaume Nodet

Red Hat, Open Source Integration

Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

R: [VOTE] Apache Karaf (Container) 3.0.8 release

[Andrea Cosentino]

+1 (non-binding)
Thanks JB 
 
  Il lun, 8 ago, 2016 alle 9:59, Jean-Baptiste Onofré ha 
scritto:   Hi all,

I submit Karaf Container 3.0.8 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12335948

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1069/

Git Tag:
karaf-3.0.8

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
  

Re: [VOTE] Apache Karaf Decanter 1.2.0 release

[Andrea Cosentino]

+1 (non-binding).

Thanks JB!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, August 2, 2016 2:02 PM, Christian Schneider 
<ch...@die-schneider.net> wrote:
+1 (non binding)

Christian


On 01.08.2016 18:32, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Karaf Decanter 1.2.0 release to your vote.
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12335659
>  
>
>
> Git tag:
> decanter-1.2.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1068/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
>
> Regards
> JB


-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect

http://www.talend.com

Re: [VOTE] Apache Karaf Cellar 4.0.1 release

[Andrea Cosentino]

+1 (non-binding).

Thanks JB :-)
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, July 11, 2016 10:28 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

I submit Apache Karaf Cellar 4.0.1 to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12334169

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1067/

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [UPDATE] Releases schedule

[Andrea Cosentino]

Thanks JB! :-)
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Sunday, July 3, 2016 8:52 PM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
Hi all,

just a quick update about the releases schedule.

End of this week and during the week end, I should be able to submit 
Cellar 4.0.1 and Decanter 1.1.1 to vote.

Karaf Container 4.0.6 and 3.0.8 are planned for end of the following week.

On the other hand, I worked on couple of PoC around Docker and 
karaf-boot. I will give you more details soon.

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

R: Re: [VOTE] Apache Karaf 3.0.7 release (take 3)

[Andrea Cosentino]

In this case +1 for me. I was thinking the release was delayed.
Thanks JB :-)
Andrea

 
 
  Il ven, 17 giu, 2016 alle 22:20, Krzysztof 
Sobkowiak ha scritto:   Look here 
http://irclogs.dankulp.com/logs/irclogger_log/apache-karaf?date=2016-06-16,Thu

On 17.06.2016 22:16, Krzysztof Sobkowiak wrote:
> I've chatted with JB and he told he will include it in 3.0.8.
>
> On 17.06.2016 22:02, Jamie G. wrote:
>> > Is take 3 under vote or was it delayed for Karaf 4539?
>> >

-- 
Krzysztof Sobkowiak (@ksobkowiak)

JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
  

Re: Board report June 2016

[Andrea Cosentino]

Looks good to me :-)

Thanks JB :-)
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, June 13, 2016 7:52 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

I prepared the board report for June 2016:

https://cwiki.apache.org/confluence/display/KARAF/Board+Reports

Please take a look and let me know if I forgot something.

I would like to submit asap.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf 3.0.7 release

[Andrea Cosentino]

I was able to make it work because I had that artifact in my local repository..
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, June 8, 2016 10:25 AM, Andreas Kuhtz <andreas.ku...@gmail.com> 
wrote:
Hi JB,

I cannot find org.apache.aries.blueprint:org.apache.aries.blueprint.cm:jar:1.0.9
in a public repo, but it's required due to
https://issues.apache.org/jira/browse/KARAF-4556.
According to
https://github.com/apache/aries/commits/trunk/blueprint/blueprint-cm the
release was cancelled.

Regards,
Andreas

Andrea Cosentino <ancosen1...@yahoo.com.invalid> schrieb am Mi., 8. Juni
2016 um 08:16 Uhr:


> +1 (non-binding).
>
> Thanks JB!
>  --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
> On Tuesday, June 7, 2016 6:34 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
> Hi all,
>
> I submit Apache Karaf (Container) 3.0.7 to your vote.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12334639
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1063/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf 3.0.7 release

[Andrea Cosentino]

+1 (non-binding).

Thanks JB!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, June 7, 2016 6:34 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

I submit Apache Karaf (Container) 3.0.7 to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12334639

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1063/

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Start/Stop bundles commands on symbolic name

[Andrea Cosentino]

There was a spam attack on Apache JIRA platform.

At the moment people in the 'jira-users' group are no longer allowed to 
'Create' tickets and are no
longer allowed to 'Comment' on any tickets.

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd




On Wednesday, May 18, 2016 8:07 AM, Cristiano Costantini 
<cristiano.costant...@gmail.com> wrote:
Hello all,
am I missing that something has changed in the issue opening process,
or do I've lost capability to open issues on ASF Jira?

Anyone else has problem opening issues?

Thanks,
Cristiano



Il giorno mar 17 mag 2016 alle ore 17:08 Cristiano Costantini <
cristiano.costant...@gmail.com> ha scritto:


> Yeah,
> ok for the Jira Issue
>
> P.S. If you like to give some suggestions/indications on how to do it, I
> can try to make it by myself and propose a pull request.
>
>
>
>
>
> Il giorno mar 17 mag 2016 alle ore 17:06 Jean-Baptiste Onofré <
> j...@nanthrax.net> ha scritto:
>
>> Hi Cristiano,
>>
>> ok, I see your point on the completer now ;)
>>
>> So, yes, I can implement a completer similar to the one I did in Cellar.
>>
>> Do you mind to create a Jira about that ?
>>
>> Regards
>> JB
>>
>> On 05/17/2016 03:36 PM, Cristiano Costantini wrote:
>> > Hi JB,
>> >
>> > yeah you are right, you can use symbolic name also in bundle:* commands.
>> > What is cool in cluster:bundle-* commands is the autocompletion for
>> > symbolic name...  this is missing on the bundle:* commands. Isn't it?
>> >
>> > Regards,
>> > Cristiano
>> >
>> > P.S: sorry I didn't reply before!
>> >
>> >
>> >
>> >
>> > Il giorno gio 5 mag 2016 alle ore 17:25 Jean-Baptiste Onofré <
>> > j...@nanthrax.net> ha scritto:
>> >
>> >> Hi Cristiano,
>> >>
>> >> it should be already the case (BundleSelector in Karaf).
>> >>
>> >> Regards
>> >> JB
>> >>
>> >> On 05/05/2016 05:18 PM, Cristiano Costantini wrote:
>> >>> Hello all,
>> >>>
>> >>> in cellar it is possible to start or stop bundles using their symbolic
>> >> name:
>> >>>
>> >>>  karaf@root> cluster:bundle-stop default my-bundle-symbolic-name
>> >>>
>> >>> and also provide autocompletion for the symbolic name,
>> >>> while in normal karaf start and stop work only on bundle ID.
>> >>>
>> >>>  karaf@root> list -s | grep my-bundle
>> >>>  123 | Active   |  80 | 1.0.0.SNAPSHOT  | my-bundle-symbolic-name
>> >>>  karaf@root> bundle:stop 123
>> >>>
>> >>> is it possible to extend the basic commands to use the symbolic name
>> as
>> >> in
>> >>> cellar?
>> >>> would it be hard?
>> >>>
>> >>> Bye,
>> >>> Cristiano
>> >>>
>> >>
>> >> --
>> >> Jean-Baptiste Onofré
>> >> jbono...@apache.org
>> >> http://blog.nanthrax.net
>> >> Talend - http://www.talend.com
>> >>
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

Re: [PROPOSAL] Karaf Boot roadmap

[Andrea Cosentino]

+1 to all the points :-)

Thanks!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, May 11, 2016 5:04 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

Karaf Boot code is now on the Apache Git:

https://git.apache.org/karaf-boot.git/

with the github mirror:

https://github.com/apache/karaf-boot

I created the component in Jira.

I will update the website with karaf-boot description.

I propose the following roadmap for karaf-boot, heading to the first 1.0 
release:

1. Bootstrapping

As a reminder, karaf-boot has two goals:
- simplify the way to create module and application for developers
- simplify the bootstrapping as a "standalone" application (leveraging 
the container feature)

Currently, we mostly address the first point. Our starters provide 
annotations allowing to easily create application. The 
karaf-boot-maven-plugin "calls" the annotation processor in the 
starters, and other plugins behind the hood to easily generate artifacts.

Now, we have to address the second point: bootstrapping. I started a PoC 
on that.
I created new starters for bootstrapping:
- karaf-boot-starter-feature creates a feature using the dependencies 
and project artifact
- karaf-boot-starter-distribution creates both zip and tar.gz Karaf 
custom distribution embedding the current project artifact and dependencies
- karaf-boot-starter-distribution-rjar is similar to distribution, but 
it's a runnable jar (using a custom Main)
- karaf-boot-starter-docker creates a docker image embedding the custom 
distribution

Now, the karaf-boot-maven-plugin is checking the dependencies to find 
one of these bootstrap starter, and react accordingly.
However, most of the logic is in the plugin, leveraging 
karaf-maven-plugin (assembly and archive goals for instance).
If this approach works (and is easy), I don't think it's the most 
elegant way.
I think we should create a @bootstrap annotation on a Runnable class in 
the bootstrap starters. The annotated class is responsible of the 
bootstrap artifact creation. An abstract bootstrap starter provide an 
annotation processor that look for @bootstrap annotation and run the 
class in a thread. The karaf-boot-maven-plugin just delegates the 
bootstrapping to the starter.

WDYT ?

2. New starters
---
We have to extend the coverage of the starter to address more use cases. 
I'm thinking about starters for test (both utest and itest leveraging 
pax-exam), for jaas, for management/MBean, for eventadmin, for decanter, 
for camel, etc.

3. New samples
--
Related to 2, each new starter should have a corresponding sample. The 
samples are really important as it's where the users start.

We should also provide kind of full application use case, multi-module. 
I started this showing how to use different starters in different 
modules (like a Logo construction set).

4. Documentation and Karaf Dev Guide

The "new" Karaf Dev guide will be based mostly on karaf-boot. A second 
section ("advanced") can still address non karaf-boot cases.

Thoughts ?

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf Decanter 1.1.0 release

[Andrea Cosentino]

+1 (non-binding).

Thanks JB!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, April 21, 2016 10:07 AM, Christian Schneider 
<ch...@die-schneider.net> wrote:
+1 (non binding)

Thanks JB

Christian

On 19.04.2016 17:51, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Decanter 1.1.0 release to your vote.
>
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12334862
>  
>
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1062/
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB


-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect

http://www.talend.com

Re: [VOTE] Apache Karaf 4.0.5 release (take 3)

[Andrea Cosentino]

+1 (non-binding).

Thanks JB!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, April 18, 2016 9:56 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

I submit Karaf Container 4.0.5 release to your vote.

Release Note:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12334629

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1061/

Git tag:
karaf-4.0.5

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Andrea Cosentino]

I guess option 2 is the best solution.

Thanks!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, April 6, 2016 8:39 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi Cristiano,

I don't think it's related, as the issue in about blueprint-ext 
namespace (not even define). The problem is located in Aries Blueprint.

I gonna deal with Guillaume.

We can:
0. leave Karaf 4.0.5 as it is, but I think it's not acceptable: 
blueprint is used by lot of users, and we can't allow a release without 
a working blueprint layer.
1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't 
benefit about some improvements implemented in blueprint
2. revert or fix the change in Aries: it means we would need a new Aries 
Blueprint core release, so 3 days vote, meaning that we won't be able to 
release Karaf before roughly 6 days.

My preference is on 2 even if it delays Karaf 4.0.5 release.

Thoughts ?

I will add an Integration Test on blueprint to avoid such problem in the 
future.

Regards
JB

On 04/06/2016 08:14 AM, Cristiano Costantini wrote:
> Hi JB and Krzysztof,
>
> I don't know if this can be have any impact on the problem you have
> reported, but about 1 month ago I got into an issue with camel XSD schemas
> for Camel namespaces, and the issue is that the URL of the latest XSD,
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
> is not from latest version 2.16.2, but it is from version 2.15.0
>
> While upgrading to ServiceMix 7, I had to change manually the XML to
> xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel
> .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make it work
> (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
> available)
>
> But in fact the only problem I had was that Eclipse validation and
> autocompletion of the XML files was not working properly.
>
> if this is not relevant, please ignore this message ;-)
>
> Cristiano
>
>
>
>
> Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
> j...@nanthrax.net> ha scritto:
>
>> I tried with Camel 2.16.2, camel-blueprint, and simple route in
>> blueprint: it works fine.
>>
>> I tried with your XML, and actually I have the same problem.
>>
>> It sounds like a Aries Blueprint bug. Let me try if I downgrade to
>> blueprint 1.5.x and check the change in aries blueprint (I know
>> Guillaume did some enhancements & changes).
>>
>> Honestly, I would consider as a blocker for the release, so, I will
>> probably revert my vote to -1. I just want to make more tests.
>>
>> Regards
>> JB
>>
>> On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
>>> Hi
>>>
>>> I tried to upgrade ServiceMix to the new version and have several
>> problems with blueprint.
>>>
>>> 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
>> FeaturesServiceImpl  | 9 - org.apache.karaf.features.core -
>> 4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
>>> 2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |
>> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
>> 1.6.0 | Unable to start blueprint container for bundle
>> cxf-wsn-receive/7.0.0.SNAPSHOT
>>> org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
>> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
>>  element information item must be identical to the targetNamespace
>> attribute, 'http://camel.apache.org/schema/blueprint', of the imported
>> document.
>>>   at
>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>> Source)[:]
>>>   at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
>> Source)[:]
>>>   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>> Source)[:]
>>>   at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>> Source)[:]
>>>   at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>> Source)[:]
>>>   at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>> Source)[:]
>>>   at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>> Source)[:]
>>>   at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
>> Source)[:]
>>>
>>> or
>>>
>>>

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Andrea Cosentino]

+1 (non-binding).

Thanks JB!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, April 5, 2016 7:45 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
+1 (binding)

Regards
JB


On 04/04/2016 10:38 PM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Karaf Container 4.0.5 release to your vote.
>
> Release Note:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12334629
>
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1060/
>
> Git tag:
> karaf-4.0.5
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf 4.0.5 release

[Andrea Cosentino]

+1 (non-binding).

Thanks JB!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, April 1, 2016 3:23 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

I submit Karaf Container 4.0.5 release to your vote.

Release Note:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12334629

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1059/

Git tag:
karaf-4.0.5

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf Decanter 1.1.0 release

[Andrea Cosentino]

+1 (non-binding)

Thanks.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, March 28, 2016 3:18 PM, Christian Schneider 
<ch...@die-schneider.net> wrote:
+1 (non binding)

Christian


2016-03-28 10:52 GMT+02:00 Morgan <morgan.haut...@gmail.com>:

> +1 (non-binding)
>
>
> On 2016-03-28 10:09, Jean-Baptiste Onofré wrote:
>
>> Hi all,
>>
>> I submit the Decanter 1.1.0 release to your vote.
>>
>> Release Notes:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12334862
>>
>> Staging Repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1058/
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Do not approve the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.
>>
>> Regards
>> JB
>>
>
>


-- 
-- 
Christian Schneider
http://www.liquid-reality.de
<https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46=http%3a%2f%2fwww.liquid-reality.de>

Open Source Architect
http://www.talend.com
<https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46=http%3a%2f%2fwww.talend.com
>

Re: [PROPOSAL] Create karaf-boot project

[Andrea Cosentino]

Hi JB,

in my opinion is better a new subproject :-)

Thanks!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, March 21, 2016 12:52 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi team,

Regarding the discussion we had couple of months ago, karaf-boot PoC 
started on my github.

In order to give more visibility, and allow anyone to work on it, I 
propose to donate this as a Karaf sub-project or a Karaf Container module.

Right now, I will push some enhancements/new features that I did last 
week, and I will update the README (markdown) to describe the purposes 
and objectives of karaf-boot.

For the donation, I see two ways:

- a new subproject as Decanter, or Cellar, meaning karaf-boot will have 
its own git repo.
- a module in Karaf Container (so a folder named boot or karaf-boot in 
the Karaf container git repo).

Thoughts ?

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Release schedule

[Andrea Cosentino]

+1.

Thanks!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, March 4, 2016 8:12 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

All good things have an end: I'm back from vacation ;)

I propose to work on the preparation of the following releases:
- Karaf Decanter 1.1.0: it's a major new series, with a lot of new 
features. I have some work in progress that I will push.
- Karaf Container 4.0.5
- Karaf Cellar 3.0.4 and 4.0.1

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [DISCUSS] Release Decanter 1.1.0

[Andrea Cosentino]

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é <j...@nanthrax.net> 
wrote:
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 like bundle.id or event.topics block fail 
the storage of the document in elasticsearch.

In order to support both Elasticsearch 1.x and Elasticsearch 2.x, I 
would like to replace '.' by '_' in all field name (in the decanter 
marshaller).

If it doesn't affect the default Kibana dashboards (they use the field 
values, not the name), it could have an impact for users who extended 
decanter.

That's why I would propose the following:
1. I create the decanter-1.0.x branch based on the decanter-1.0.1 tag
2. I update decanter master to 1.1.0-SNAPSHOT version
3. then I will release Decanter 1.1.0 including support of elasticsearch 
1.x and 2.x (with both native and REST API), and the other appenders 
(kafka, mqtt, etc).

Thoughts ?

Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf 3.0.6 release

[Andrea Cosentino]

+1 (non-binding).


 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, February 10, 2016 7:45 AM, Jean-Baptiste Onofré 
<j...@nanthrax.net> wrote:
+1 (binding)

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
>
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1057/
>
> Git tag:
> karaf-3.0.6
>
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

R: Roadmap and releases schedule

[Andrea Cosentino]

Great plan! Sounds good!
Andrea

Inviato da Yahoo Mail su Android 
 
  Il mer, 3 feb, 2016 alle 7:32, Jean-Baptiste Onofré ha 
scritto:   Hi all,

I would like to provide a quick update about the releases schedule (it's 
not up to date on the current website, but it is on the new one).

1. New website: as I said yesterday, it's mostly done, I'm adding the 
last content. I should be able to promote the new website tonight or 
tomorrow.
2. Decanter 1.0.2: I would like to release Decanter 1.0.2 during the 
week end or beginning of next week. It will include refactorings 
(marshaller service), bug fixes (timestamp, JDBC appender, etc), new 
features (new appenders for kafka, mongodb, etc).
3. Cellar 4.0.1 planned middle of next week, including mostly bug fixes 
and couple of new features (cluster:status, etc).
4. Karaf 3.0.6: I fixed issues on the 3.x branch. Hopefully, I should be 
able to propose 3.0.6 to vote for the end of this week.
5. Master is now 4.1.0-SNAPSHOT. I think we could include karaf-boot 
there and start "major" dependency updates. It's also where I'm doing 
the complete dev guide refactoring, replacing the existing demos with 
bunch of samples.

Thoughts ?
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
  

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

[Andrea Cosentino]

+1.

Looks great on oneplus one.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, January 21, 2016 3:30 PM, Jamie G. <jamie.goody...@gmail.com> 
wrote:
+1 - looks great :)


On Thu, Jan 21, 2016 at 10:56 AM, Serge Huber <shu...@jahia.com> wrote:
> Sorry that first sentence should have been : "Looks quite good on my iPhone 6 
> Plus but strangely not all links are clickable.”
>
>> On 21 janv. 2016, at 15:25, Serge Huber <shu...@jahia.com> wrote:
>>
>> Looks quite good on my iPhone 6 Plus but strangely not all links are not 
>> clickable.
>>
>> For example if I click on Documentation in the top menu and then want to 
>> click on Karaf Container 4.x [online] link it doesn’t do anything. Testing 
>> this in Safari’s responsive design mode has the same behavior. Not sure 
>> what’s going on there.
>>
>> Strangely all the links in the top menu always work, but any link in the 
>> content doesn’t !
>>
>> cheers,
>>  Serge…
>>
>>> On 21 janv. 2016, at 14:53, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
>>>
>>> Hi all,
>>>
>>> Morgan helped me to fix the mobile rendering issue.
>>>
>>> I updated the website proposal on the same URL:
>>>
>>> http://maven.nanthrax.net/goodies/karaf/site/
>>>
>>> (NB: don't forget to refresh your browser cache with CTRL-SHIFT-R)
>>>
>>> I gonna add couple of missing links, but you can consider this mockup as 
>>> the one to vote on.
>>>
>>> @Milen: as you voted -1 due to the mobile rendering, can you take a new 
>>> look and see if it's OK for you now ?
>>>
>>> For the others, don't hesitate to vote (if it's not already done).
>>>
>>> Thanks !
>>> Regards
>>> JB
>>>
>>> On 01/19/2016 10:24 AM, Jean-Baptiste Onofré wrote:
>>>> Hi all,
>>>>
>>>> I extending this vote to 72 more hours in order for me to fix the
>>>> rendering on mobile, and add the release schedule information.
>>>>
>>>> Thanks,
>>>> Regards
>>>> JB
>>>>
>>>> On 01/13/2016 06:58 PM, Jean-Baptiste Onofré wrote:
>>>>> Hi all,
>>>>>
>>>>> As already discussed on the mailing list, I would like to promote the
>>>>> new website.
>>>>>
>>>>> As reminder, the new website proposal is there:
>>>>>
>>>>> http://maven.nanthrax.net/goodies/karaf/site/
>>>>>
>>>>> Please vote to approve the new website:
>>>>>
>>>>> [ ] +1 Approve the new website promotion
>>>>> [ ] -1 Don't approve the new website (please provide specific comments)
>>>>>
>>>>> This vote will be open for at least 72 hours.
>>>>>
>>>>> Thanks,
>>>>> Regards
>>>>> JB
>>>>
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>
>

Re: [VOTE] Apache Karaf 2.4.4 release

[Andrea Cosentino]

+1 (non-binding).


Thanks JB.
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, January 22, 2016 2:16 AM, Freeman Fang <freeman.f...@gmail.com> 
wrote:
+1 (binding)
－
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat




> On Jan 22, 2016, at 12:25 AM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
> 
> Hi all,
> 
> I submit Karaf 2.4.4 release to your vote.
> 
> This is the last release on the karaf-2.x branch to include all last fixes. 
> The karaf-2.x branch now moves to "Non Active" mode: it means that it's not 
> in the main focus of the Karaf team (only individual effort).
> 
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12332989
> 
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1056/
> 
> Git Tag:
> karaf-2.4.4
> 
> Please vote to approve this release:
> 
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
> 
> This vote will be open for at least 72 hours.
> 
> Thanks,
> Regards
> JB
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: [VOTE] Apache Karaf 2.3.12 release

[Andrea Cosentino]

+1.

Thanks JB.

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, January 19, 2016 6:16 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

I submit Karaf 2.3.12 release to your vote.

This is the last release on the karaf-2.3.x branch to include all last 
fixes. The karaf-2.3.x branch now moves to "Non Active" mode: it means 
that it's not in the main focus of the Karaf team (only individual effort).

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12329877

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1055

Git Tag:
karaf-2.3.12

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

[Andrea Cosentino]

+1 (non-binding).
Best,Andrea

Inviato da Yahoo Mail su Android 
 
  Il mer, 13 gen, 2016 alle 19:05, Jamie G. ha 
scritto:   +1 (binding)

Cheers,
Jamie

On Wed, Jan 13, 2016 at 2:32 PM, Serge Huber  wrote:
> +1 (non-binding)
>
> cheers,
>  Serge…
>
>> On 13 janv. 2016, at 18:58, Jean-Baptiste Onofré  wrote:
>>
>> Hi all,
>>
>> As already discussed on the mailing list, I would like to promote the new 
>> website.
>>
>> As reminder, the new website proposal is there:
>>
>> http://maven.nanthrax.net/goodies/karaf/site/
>>
>> Please vote to approve the new website:
>>
>> [ ] +1 Approve the new website promotion
>> [ ] -1 Don't approve the new website (please provide specific comments)
>>
>> This vote will be open for at least 72 hours.
>>
>> Thanks,
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>  

Re: [VOTE] Apache Karaf 4.0.4 release

[Andrea Cosentino]

You're right :-)

I was wrong.

Andrea





On Monday, January 11, 2016 9:33 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Your vote is not binding (you are not PMC).

Regards
JB


On 01/11/2016 08:45 AM, Andrea Cosentino wrote:
> Hi,
>
> +1 (binding)
>
> Thanks,
>

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Apache Karaf 4.0.4 release

[Andrea Cosentino]

Hi,

+1 (binding)

Thanks,

-- 
Andrea Cosentino 
-
Apache Camel PMC Member
Apache Karaf Committer

Email: ancosen1...@yahoo.com 
Twitter: @oscerd2 
Github: oscerd 



On Sunday, January 10, 2016 6:10 PM, Jean-Baptiste Onofré <j...@nanthrax.net> 
wrote:
Hi all,

I submit Karaf 4.0.4 release to your vote.

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12334047

Staging Repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1054/

Git Tag:
karaf-4.0.4

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB
-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com