Re: [VOTE] Release Apache Karaf 2.3.10

[Andreas Pieber]

+1 (binding)

Kind regards,
Andreas

On Thu Feb 05 2015 at 3:09:11 AM Freeman Fang 
wrote:

> ＋1 (binding)
> －
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
>
>
>
> On 2015-2-4, at 上午8:45, Jamie G. wrote:
>
> > Hi,
> >
> > We resolved 10 issues in this release:
> > http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
> webapp/index/community/download/karaf-2.3.10-release.page?view=markup
> >
> > Dependency changes can be reviewed here:
> > http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
> webapp/index/documentation/karaf-dependencies/karaf-deps-
> 2.3.x.page?revision=1613719&view=markup
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1022/
> >
> > Git tag:
> > karaf-2.3.10
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote will be open for 72 hours.
>
>

Re: Karaf 4.0 switch to Java8?

[Andreas Pieber]

I'm not so sure that I like the idea of removing the support for a JDK
Version between two minor release. If we keep 7 for 4.0 we should keep it
for the entire 4xer line. Especially since the industry does not move as
fast as we do...

Kind regards,
Andreas

On Mon Jan 26 2015 at 7:08:52 PM Jean-Baptiste Onofré 
wrote:

> Hi,
>
> I would prefer:
> - Java7 for compilation on Karaf 4.0.x
> - Java7 and Java8 runtime compliant for Karaf 4.0.x
> - Java8 "oriented" for compilation and runtime for Karaf 4.1.x
>
> So, I would wait the 4.0.x GA before moving completely on Java8.
>
> Regards
> JB
>
> On 01/26/2015 04:22 PM, Achim Nierbeck wrote:
> > Hi,
> >
> > How is everybody feeling about to switch to JDK8 for building the master
> > branch? (Karaf 4)
> > According to [1], Java 7 is pretty much at EOL.
> > I think this needs to be addressed right now since for Pax Web 4.1. which
> > is now used by Karaf 4
> > it is needed to use JDK8. Not because of using any new features of Java 8
> > but because of the memory issues while running the integration tests.
> > There seems to be a reproducible issue since switching to Jetty 9.2 and
> > running the integration tests with Java 7. Those are gone when Java 8 is
> > used.
> > Therefore Pax Web 4.1. uses JDK8 for building right now, though the
> > switches are set to be compatible with Java 7, for source and target.
> >
> > Another benefit might be to use JDK8 features already.
> >
> > For me I would like to see at least JDK8 with source and target set to 7
> >
> > regards, Achim
> >
> > [1] - http://www.oracle.com/technetwork/java/eol-135779.html
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Karaf 3.0.3

[Andreas Pieber]

+1 (binding)

Kind regards,
Andreas

On Wed Jan 28 2015 at 10:46:56 AM Christoph Gritschenberger <
christoph.gritschenber...@gmail.com> wrote:

> +1 (non-binding)
>
> kind regards,
> Christoph
>
> On 28/01/15 02:01, Jamie G. wrote:
> > Hi,
> >
> > We resolved 97 issues in this release:
> > http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
> webapp/index/community/download/karaf-3.0.3-release.page?view=markup
> >
> > Dependency changes can be reviewed here:
> > http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
> webapp/index/documentation/karaf-dependencies/karaf-deps-
> 3.0.x.page?view=markup
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1021/
> >
> > Git tag:
> > karaf-3.0.3
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote will be open for 72 hours.
> >
>
>

Re: [VOTE] Apache Karaf Cellar 3.0.1 release

[Andreas Pieber]

+1 (binding)

Kind regards,
Andreas

On Thu Jan 22 2015 at 6:35:22 PM Jamie G.  wrote:

> +1 (binding)
>
> Cheers,
> Jamie
>
> On Wed, Jan 21, 2015 at 5:09 PM, Jean-Baptiste Onofré 
> wrote:
> > +1 (binding)
> >
> > Regards
> > JB
> >
> >
> > On 01/19/2015 02:53 PM, Jean-Baptiste Onofré wrote:
> >>
> >> Hi all,
> >>
> >> I submit Apache Karaf Cellar 3.0.1 release to your vote.
> >>
> >> Release Notes:
> >>
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311140&version=12327148
> >>
> >>
> >> Staging Repository:
> >> https://repository.apache.org/content/repositories/orgapachekaraf-1019/
> >>
> >> Git tag:
> >> cellar-3.0.1
> >>
> >> 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.
> >>
> >> Thanks,
> >> Regards
> >> JB
> >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf Cellar 2.3.4 release

[Andreas Pieber]

+1 (binding)

Kind regards,
Andreas

On Thu Jan 22 2015 at 6:28:39 PM Jamie G.  wrote:

> +1 (binding)
>
> Cheers,
> Jamie
>
> On Wed, Jan 21, 2015 at 5:09 PM, Jean-Baptiste Onofré 
> wrote:
> > +1 (binding)
> >
> > Regards
> > JB
> >
> >
> > On 01/19/2015 06:27 PM, Jean-Baptiste Onofré wrote:
> >>
> >> Hi all,
> >>
> >> I submit Apache Karaf Cellar 2.3.4 release to your vote.
> >>
> >> Release Notes:
> >>
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311140&version=12328968
> >>
> >>
> >> Staging Repository:
> >> https://repository.apache.org/content/repositories/orgapachekaraf-1020/
> >>
> >> Git tag:
> >> cellar-2.3.4
> >>
> >> 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.
> >>
> >> Thanks,
> >> Regards
> >> JB
> >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Karaf 2.4.1

[Andreas Pieber]

+1 (binding)

kind regards, and a happy new year!
Andreas

On Wed Dec 31 2014 at 4:57:38 PM Achim Nierbeck 
wrote:

> +1 (binding)
>
> regards, and happy new year :-)
>
> Achim
>
> 2014-12-31 7:15 GMT+01:00 Jean-Baptiste Onofré :
> >
> > +1 (binding)
> >
> > Regards
> > JB
> >
> >
> > On 12/31/2014 03:10 AM, Jamie G. wrote:
> >
> >> Hi,
> >>
> >> We resolved 76 issues in this release:
> >> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
> >> webapp/index/community/download/karaf-2.4.1-release.page?view=markup
> >>
> >> Dependency changes can be reviewed here:
> >> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
> >> webapp/index/documentation/karaf-dependencies/karaf-deps-
> >> 2.4.x.page?view=markup
> >>
> >> Staging repository:
> >> https://repository.apache.org/content/repositories/orgapachekaraf-1018/
> >>
> >> Git tag:
> >> karaf-2.4.1
> >>
> >> Please vote to approve this release:
> >>
> >> [ ] +1 Approve the release
> >> [ ] -1 Veto the release (please provide specific comments)
> >>
> >> This vote will be open for at least 72 hours given the new year's
> holiday.
> >>
> >>
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
>
> --
>
> Apache Member
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> blog 
> Co-Author of Apache Karaf Cookbook 
>
> Software Architect / Project Manager / Scrum Master
>

Re: [RESULT][PROPOSAL] Karaf Decanter monitoring

[Andreas Pieber]

Hey JB,

Thank you very much for the update! I'm already thrilled about that one :-)

Kind regards,
Andreas

On Fri Nov 14 2014 at 7:17:04 PM Achim Nierbeck 
wrote:

> Hi JB,
>
> awesome. Thanks for the feedback :-)
>
> regards, Achim
>
> 2014-11-14 16:40 GMT+01:00 Jean-Baptiste Onofré :
>
> > Hi guys,
> >
> > just a quick update about Karaf Decanter.
> >
> > The INFRA created the git repository. I will cleanup the legal files, and
> > add the latest features. I will push to karaf-decanter later today.
> >
> > Regards
> > JB
> >
> >
> > On 10/19/2014 09:18 PM, Jean-Baptiste Onofré wrote:
> >
> >> Hi all,
> >>
> >> this vote passed with only +1.
> >>
> >> I will push my latest changes on the github, request the git repo to
> >> INFRA (to push there and remove the github one), and create a component
> >> in Jira.
> >>
> >> Thanks all for your vote.
> >>
> >> Regards
> >> JB
> >>
> >> On 10/14/2014 05:12 PM, Jean-Baptiste Onofré wrote:
> >>
> >>> Hi all,
> >>>
> >>> First of all, sorry for this long e-mail ;)
> >>>
> >>> Some weeks ago, I blogged about the usage of ELK
> >>> (Logstash/Elasticsearch/Kibana) with Karaf, Camel, ActiveMQ, etc to
> >>> provide a monitoring dashboard (know what's happen in Karaf and be able
> >>> to store it for a long period):
> >>>
> >>> http://blog.nanthrax.net/2014/03/apache-karaf-cellar-camel-
> >>> activemq-monitoring-with-elk-elasticsearch-logstash-and-kibana/
> >>>
> >>>
> >>>
> >>> If this solution works fine, there are some drawbacks:
> >>> - it requires additional middlewares on the machines. Additionally to
> >>> Karaf itself, we have to install logstash, elasticsearch nodes, and
> >>> kibana console
> >>> - it's not usable "out of the box": you need at least to configure
> >>> logstash (with the different input/output plugins), kibana (to create
> >>> the dashboard that you need)
> >>> - it doesn't cover all the monitoring needs, especially in term of SLA:
> >>> we want to be able to raise some alerts depending of some events (for
> >>> instance, when a regex is match in the log messages, when a feature is
> >>> uninstalled, when a JMX metric is greater than a given value, etc)
> >>>
> >>> Actually, Karaf (and related projects) already provides most (all) data
> >>> required for the monitoring. However, it would be very helpful to have
> a
> >>> "glue", ready to use and more user friendly, including a storage of the
> >>> metrics/monitoring data.
> >>>
> >>> Regarding this, I started a prototype of a monitoring solution for
> Karaf
> >>> and the applications running in Karaf.
> >>> The purpose is to be very extendible, flexible, easy to install and
> use.
> >>>
> >>> In term of architecture, we can find the following component:
> >>>
> >>> 1/ Collectors & SLA Policies
> >>> The collectors are services responsible of harvesting monitoring data.
> >>> We have two kinds of collectors:
> >>> - the polling collectors are invoked by a scheduler periodically.
> >>> - the event driven collectors react to some events.
> >>> Two collectors are already available:
> >>> - the JMX collector is a polling collector which harvest all MBeans
> >>> attributes
> >>> - the Log collector is a event driven collector, implementing a
> >>> PaxAppender which react when a log message occurs
> >>> We can planned the following collectors:
> >>> - a Camel Tracer collector would be an event driven collector, acting
> as
> >>> a Camel Interceptor. It would allow to trace any Exchange in Camel.
> >>>
> >>> It's very dynamic (thanks to OSGi services), so it's possible to add a
> >>> new custom collector (user/custom implementation).
> >>>
> >>> The Collectors are also responsible of checking the SLA. As the SLA
> >>> policies are tight to the collected data, it makes sense that the
> >>> collector validates the SLA and call/delegate the alert to SLA
> services.
> >>>
> >>> 2/ Scheduler
> >>> The scheduler service is responsible to call the Polling Collectors,
> >>> gather the harvested data, and delegate to the dispatcher.
> >>> We already have a simple scheduler (just a thread), but we can plan a
> >>> quartz scheduler (for advanced cron/trigger configuration), and another
> >>> one leveraging the Karaf scheduler.
> >>>
> >>> 3/ Dispatcher
> >>> The dispatcher is called by the scheduler or the event driven
> collectors
> >>> to dispatch the collected data to the appenders.
> >>>
> >>> 4/ Appenders
> >>> The appender services are responsible to send/store the collected data
> >>> to target systems.
> >>> For now, we have two appenders:
> >>> - a log appender which just log the collected data
> >>> - a elasticsearch appender which send the collected data to a
> >>> elasticsearch instance. For now, it uses "external" elasticsearch, but
> >>> I'm working on an elasticsearch feature allowing to embed elasticsearch
> >>> in Karaf (it's mostly done).
> >>> We can plan the following other appenders:
> >>> - redis to send the collected data in Redis messaging system
> >>> - jdbc to store the collected data in

Re: [VOTE] Release Apache Karaf 2.3.9

[Andreas Pieber]

Basically +1; builds and runs fine.

Just a curious question, but shouldn't be the notice file located
in apache-karaf-2.3.9 the same as the one in apache-karaf-2.3.9/src?

Kind regards,
Andreas

On Thu, Nov 6, 2014 at 6:02 AM, Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Regards
> JB
>
>
> On 11/06/2014 02:19 AM, Jamie G. wrote:
>
>> Hi,
>>
>> We resolved 7 issues in this release:
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
>> webapp/index/community/download/karaf-2.3.9-release.page?view=markup
>>
>> Dependency changes can be reviewed here:
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
>> webapp/index/documentation/karaf-dependencies/karaf-deps-
>> 2.3.x.page?revision=1613719&view=markup
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1014/
>>
>> Git tag:
>> karaf-2.3.9
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

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

[Andreas Pieber]

+1

Kind regards,
Andreas

On Wed, Oct 15, 2014 at 7:19 PM, Jean-Baptiste Onofré 
wrote:

> Hi all,
>
> following the discussion about Karaf Decanter, I would like to submit a
> formal vote.
>
> The purpose is to be able to create the resources (especially the git
> repo) to move forward and easily allow contributions.
>
> Please vote to approve the create/donation of Decanter:
>
> [ ] +1 Approve Karaf Decanter subproject
> [ ] -1 Do not approve Karaf Decanter subproject (please provide specific
> comments)
>
> This vote will be open for 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Karaf 4.0.0.M1 technology preview.

[Andreas Pieber]

+1

On Mon, Oct 13, 2014 at 12:40 AM, Guillaume Nodet  wrote:

> +1
>
> 2014-10-11 23:10 GMT+02:00 Jamie G. :
>
> > Hi,
> >
> > We have 327 issues resolved on our way towards Apache Karaf 4.0.0 GA
> > release. This is a technology preview, as such there will be features
> > and other functionality not yet implemented. Please refrain from using
> > this particular RC in production.
> >
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-4.0.0.M1-release.page
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1013/
> >
> > Release git tags:
> > 4.0.0.M1
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote will be open for 72 hours.
> >
>

Re: [VOTE] Release Apache Karaf 3.0.2

[Andreas Pieber]

+1

Kind regards,
Andreas
On Oct 10, 2014 9:34 PM, "Jamie G."  wrote:

> Hi,
>
> We resolved 215 issues in this release:
>
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-3.0.2-release.page?view=markup
>
> Dependency changes can be reviewed here:
>
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-3.0.x.page?view=markup
>  (The website published table will be updated after vote)
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1012/
>
> Git tag:
> karaf-3.0.2
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>

Re: [VOTE] Release Apache Karaf 2.3.8

[Andreas Pieber]

+1 (binding)

On Wed, Sep 17, 2014 at 3:25 AM, Freeman Fang 
wrote:

> +1 (binding)
> －
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
>
>
>
> On 2014-9-16, at 下午3:56, Jamie G. wrote:
>
> > Hi,
> >
> > We resolved 9 issues in this release:
> >
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.8-release.page?view=markup
> >
> > Dependency changes can be reviewed here:
> >
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1010/
> >
> > Git tag:
> > karaf-2.3.8
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote will be open for 72 hours.
>
>

Re: [VOTE] Release Apache Karaf 2.3.7

[Andreas Pieber]

builds and tests as it should. Distribution looks good and does what it
should do.

+1 (binding).

Kind regards,
Andreas


On Wed, Sep 3, 2014 at 11:29 PM, Krzysztof Sobkowiak <
krzys.sobkow...@gmail.com> wrote:

> +1 (non-binding)
> Looks good for me
>
> Best regards
> Krzysztof
>
> On 03.09.2014 02:47, Jamie G. wrote:
> > Hi,
> >
> > We resolved 15 issues in this release:
> >
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.7-release.page?view=markup
> >
> > Dependency changes can be reviewed here:
> >
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1009/
> >
> > Git tag:
> > karaf-2.3.7
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote will be open for 72 hours.
>
>
> --
> Krzysztof Sobkowiak
>
> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
> @ ASF
> Capgemini  | Software Solutions Center
>  | Wroclaw
> e-mail: krzys.sobkow...@gmail.com  |
> Twitter: @KSobkowiak
> Calendar: http://goo.gl/yvsebC
>

Re: Board Report for September 2014

[Andreas Pieber]

Hey,

+1 too from my side.

Kind regards,
Andreas


On Wed, Aug 27, 2014 at 8:46 PM, Achim Nierbeck 
wrote:

> Hi JB,
>
> looks good to me.
> +1
>
> regards, Achim
>
>
>
> 2014-08-27 16:32 GMT+02:00 Jean-Baptiste Onofré :
>
> > Hi all,
> >
> > I prepared the Board Report for September 2014:
> >
> > https://cwiki.apache.org/confluence/display/KARAF/Board+Reports
> >
> > I will update it with the new releases that we should provide end of this
> > week or next week.
> >
> > Please review and update if I forgot something.
> >
> > Thanks,
> > Regards
> > JB
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
>
>
> --
>
> Apache Member
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> blog 
>
> Software Architect / Project Manager / Scrum Master
>

Re: [VOTE] Release Apache Karaf 2.3.6

[Andreas Pieber]

+1 (binding)

Kind regards,
Andreas


On Thu, Jul 31, 2014 at 11:53 AM, Christian Schneider <
ch...@die-schneider.net> wrote:

> +1 (non binding)
>
> Christian
>
> Am 29.07.2014 04:39, schrieb Jamie G.:
>
>  Hi,
>>
>> We resolved 70 issues in this release:
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
>> webapp/index/community/download/karaf-2.3.6-release.page?view=markup
>>
>> Dependency changes can be reviewed here:
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
>> webapp/index/documentation/karaf-dependencies/karaf-deps-
>> 2.3.x.page?revision=1613719&view=markup
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1008/
>>
>> Git tag:
>> karaf-2.3.6
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.
>>
>
>
> --
>  Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
>

Re: [DISCUSS] Release Karaf 2.4.0

[Andreas Pieber]

Nothing to add; +1

Kind regards,
Andreas


On Wed, Jul 9, 2014 at 5:24 PM, Guillaume Nodet  wrote:

> Now that Aries releases are done, I'd like to discuss a 2.4.0 release asap.
> I think it's in a good shape, but i'll do a bit more testing and I would
> welcome any additional volunteers.
>
> Anyway, does anyone as any urgent stuff to put in before we release ?
> I'd like to start the release friday or monday if nothing requires a delay.
>
> Thoughts ?
>
> Guillaume
>

Re: [VOTE] Apache Karaf Cave 3.0.0 release

[Andreas Pieber]

Builds, tests and looks fine => +1

Kind regards,
Andreas


On Mon, Jun 30, 2014 at 4:53 PM, Jean-Baptiste Onofré 
wrote:

> Hi all,
>
> I submit the Apache Karaf Cave 3.0.0 release to your vote.
>
> This is a major new release of Cave, the first purpose is to fully work on
> Karaf 3.0.x.
>
> We resolved 10 issues in this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311140&version=12327169
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1007/
>
> Git tag:
> cave-3.0.0
>
> 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.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Karaf 2.3.5

[Andreas Pieber]

+1 (binding)

Kind regards,
Andreas


On Fri, Apr 11, 2014 at 5:49 AM, Jean-Baptiste Onofré wrote:

> +1 (binding)
>
> Regards
> JB
>
>
> On 04/10/2014 06:45 PM, Jamie G. wrote:
>
>> Hi,
>>
>> We resolved 34 issues in this release:
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
>> webapp/index/community/download/karaf-2.3.5-release.page?view=log
>>
>> Dependency changes can be reviewed here:
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/
>> webapp/index/documentation/karaf-dependencies/karaf-deps-
>> 2.3.x.page?view=log
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1004/
>>
>> Git tag:
>> karaf-2.3.5
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Karaf 3.0.1

[Andreas Pieber]

* Build and tests run clean using jdk7.
* Artifacts looks fine.
* Notice files look fine.

+1

Kind regards,
Andreas


On Thu, Apr 10, 2014 at 11:57 PM, Jamie G.  wrote:

> Hi,
>
> We resolved 145 issues in this release:
>
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-3.0.1-release.page?view=markup
>
> Dependency changes can be reviewed here:
>
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-3.0.x.page?view=markup
>  (The website published table will be updated after vote)
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1005/
>
> Git tag:
> karaf-3.0.1
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>

Fwd: Karaf & Java8

[Andreas Pieber]

I really think that we should create a 3.1 branch soon again (directly
before Gulliaumes commits), since 4.0 is simply too far in the future and
new features on micro releases are not following the semvers specification.

Kind regards,
Andreas

-- Forwarded message --
From: Jean-Baptiste Onofré 
Date: Fri, Mar 28, 2014 at 11:01 AM
Subject: Re: Karaf & Java8
To: u...@karaf.apache.org


Hi JP,

yes, 3.0.1 will be release soon (I'm a bit late on this but I will work on
that during the week end).

3.1.0 doesn't exist anymore for now (master is 4.0.0-SNAPSHOT).

So, yes, Java8 will be support by 3.0.1 and 4.0.0 (and eventually 3.1.0 if
we decide to create the branch at some point).

Regards
JB


On 03/28/2014 10:35 AM, CLEMENT Jean-Philippe wrote:

> Excellent :)
>
> I guess 3.0.1 should be released soon (at least as a RC)?
>
> PS: is Java 8 part of 3.0.1 or 3.1.0?
>
> JP
>
> -Message d'origine-
> De : Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
> Envoyé : jeudi 27 mars 2014 19:23
> À : u...@karaf.apache.org
> Objet : Re: Karaf & Java8
>
> Hi Charlie,
>
> Yes, 3.0.1 and 4.0.0 will have Java8 support.
>
> Regards
> JB
>
> On 03/27/2014 07:17 PM, Charlie Mordant wrote:
>
>> Hi JB, JP,
>>
>> Will it be a 3.0.1 dedicated to Java8 support soon? It should be nice
>> for sharp devs ;).
>>
>> Regards,
>>
>>
>> 2014-03-27 19:13 GMT+01:00 Jean-Baptiste Onofré > >:
>>
>>  Hi JP,
>>
>>  it works straight forward for me using ASM 5.0.1. I will rebase my
>>  local branch and merge on master.
>>
>>  Regards
>>  JB
>>
>>
>>  On 03/27/2014 04:45 PM, CLEMENT Jean-Philippe wrote:
>>
>>  Hi JB,
>>
>>  Some modules which have been compiled with Java 8 fail to start.
>>  The problem is I have no clue if it's due to Karaf/Java8 or
>>  not... I'm stuck :S
>>
>>  Did you make any progress?
>>
>>  JP
>>
>>  [@@ THALES GROUP INTERNAL @@]
>>
>>
>>  -Message d'origine-
>>  De : Jean-Baptiste Onofré [mailto:j...@nanthrax.net
>>  ]
>>  Envoyé : lundi 24 mars 2014 12:11
>>  À : u...@karaf.apache.org 
>>  Objet : Re: Karaf & Java8
>>
>>  Hi JP
>>
>>  for Karaf itself no, the point is more on the Aries Proxy side.
>>
>>  I plan to push something about that later today (I'm in the US
>>  this week).
>>
>>  Regards
>>  JB
>>
>>  On 03/24/2014 12:08 PM, CLEMENT Jean-Philippe wrote:
>>
>>  Hi Jean-Baptiste,
>>
>>  FYI, ASM has been updated to 5.0.1: " This is a maintenance
>>  version which fixes a few important bugs found in the 5.0
>>  version ".
>>
>>  Do you think it will take long to catch up with ASM 5 /
>> Java8?
>>
>>  JP
>>
>>  [@@ OPEN @@]
>>  -Message d'origine-
>>  De : Jean-Baptiste Onofré [mailto:j...@nanthrax.net
>>  ] Envoyé : mercredi
>>  19 mars 2014 10:19 À : u...@karaf.apache.org
>>   Objet : Re: Karaf & Java8
>>
>>  Hi JP,
>>
>>  FYI, I updated the Jira this morning, I will work on ASM5
>>  update today.
>>
>>  Regards
>>  JB
>>
>>  On 03/19/2014 09:26 AM, CLEMENT Jean-Philippe wrote:
>>
>>  Hi JB,
>>
>>  How may I download the 3.1.0-SNAPSHOT?
>>
>>  Regards,
>>  JP
>>
>>  [@@ THALES GROUP INTERNAL @@]
>>
>>  -Message d'origine-
>>  De : Jean-Baptiste Onofré [mailto:j...@nanthrax.net
>>  ] Envoyé : lundi 17
>>  mars 2014 10:55 À : u...@karaf.apache.org
>>   Objet : Re: Karaf &
>> Java8
>>
>>  Hi JP,
>>
>>  Karaf master is 3.1.0-SNAPSHOT. I will take a look on
>>  the update on master (especially the impact on
>> blueprint).
>>
>>  Regards
>>  JB
>>
>>  On 03/17/2014 10:17 AM, CLEMENT Jean-Philippe wrote:
>>
>>  Dear Karaf-ers,
>>
>>  ASM 5 is released so it may be used in Karaf to get
>>  Java 8 support:
>>
>>  "This version is fully backward compatible with ASM
>>  5.0 BETA (itself binary compatible with the 4.x
>>  versions) and provides full support for the new Java
>>  8 class format features. However, new dynamic checks
>>  have been added in order to make sure that ASM
>>  version numbers (e.g.
>>  Opcodes.ASM4, Opcodes.ASM5, etc) are correc

Re: [HEADS UP] Huge commits on master

[Andreas Pieber]

I don't see a problem with simply turning up the version number on the
master and branching off before Guillaumes commit and keeping the version
there.

Kind regards,
Andreas


On Mon, Mar 24, 2014 at 10:03 PM, Jamie G.  wrote:

> Master currently is at 3.1.0-SNAPSHOT, we'd need to branch that checkin at
> 4.0.
>
> --Jamie
>
> On Mon, Mar 24, 2014 at 5:32 PM, Achim Nierbeck 
> wrote:
> > Wow, now that's been a commit :D
> >
> > As far as I can tell right now this would mean master is version 4.0, at
> > least that's what
> > we discussed before, would be the impact of those changes.
> >
> > I think we have another possibility, we might create a branch based on
> the
> > revision before this commit. This would give also give a lot more people
> a
> > way of experimenting with the "impact" of
> > the new core design.
> >
> > Regards, Achim
> >
> >
> >
> > 2014-03-24 17:52 GMT+01:00 Guillaume Nodet :
> >
> >> I pushed quite a few commits to master a few minutes ago.  FWIW, that
> was
> >> slightly not done on purpose, but I wanted to push the last fix to
> master
> >> and ... everything went with it ;-)
> >>
> >> Anyway, those commits are related to making Karaf more lightweight and
> >> switching out blueprint to pure OSGi.  The code has been mostly
> unchanged
> >> (i.e. mainly switching the blueprint xml to a BundleActivator class with
> >> eventually a few very minor changes to the service implementation
> classes).
> >>
> >> The end result is the following:
> >>   * features/framework is bare to the down minimum: pax-url-aether,
> >> pax-url-wrap (we could actually remote it), pax-logging, configadmin,
> >> fileinstall, region/core and features/core
> >>   * the default karaf distro is mostly unchanged, though everything is
> >> installed through features, including the console
> >>   * the minimal distribution does not install aries-blueprint,
> aries-proxy
> >> and the shell compatibility (the previous shell console to support 2.x
> or
> >> 3.0 commands), so it's much more lightweight, even though some services
> >> could be removed at will
> >>
> >> Actually, I just spotted that the aries jars are still included in the
> >> minimal distro, even if not installed, so I'll try to align the
> contained
> >> bundles to those installed.
> >>
> >> Again, that was not really intended, so if there's a push back, we can
> git
> >> revert or force update ...
> >>
> >> Guillaume
> >>
> >
> >
> >
> > --
> >
> > Apache Karaf  Committer & PMC
> > OPS4J Pax Web  Committer
> &
> > Project Lead
> > blog 
> >
> > Software Architect / Project Manager / Scrum Master
>

Re: Board report for March 2014

[Andreas Pieber]

+1

Kind regards,
Andreas
On 5 Mar 2014 15:39, "Jean-Baptiste Onofré"  wrote:

> Hi all,
>
> I prepared the board report for March 2014:
> https://cwiki.apache.org/confluence/display/KARAF/Board+Reports
>
> Please, review and keep me posted asap. I would like to submit it today.
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [PROPOSAL] karaf-maven-plugin changes

[Andreas Pieber]

I'm with Christoph on this one. I think people wont like us too much for
changing things during minor releases. Maybe we could print a deprecation
comment if the original commands are used instead of the new ones helping
the users switch.

Kind regards,
Andreas


On Wed, Mar 5, 2014 at 12:47 AM, Christoph Gritschenberger <
christoph.gritschenber...@gmail.com> wrote:

> I think it's a bad idea to _rename_ plugin-goals. That would break
> compatibility with 3.0-plugin-configurations.
>
> Maybe the new names should be provided as aliases and the old names
> removed in 4.0
>
> kind regards,
> christoph
>
>
> On 04/03/14 20:27, Jean-Baptiste Onofré wrote:
>
>> The refactoring is on master (3.1.x), I don't change on 3.0.x as it's a
>> maintenance branch now.
>>
>> Regards
>> JB
>>
>> On 03/04/2014 07:48 PM, Jamie G. wrote:
>>
>>> 1a. Refactoring/Renaming goals - on the 3.0.x or for 3.1.x? The
>>> shorter names are good, just want a clarification on target.
>>>
>>> 1b. New Goals - Sounds good.
>>>
>>> 2. New tests are always welcome :)
>>>
>>> On Tue, Mar 4, 2014 at 3:09 PM, Jean-Baptiste Onofré 
>>> wrote:
>>>
 Hi all,

 I would like to discuss with you about my current work on the
 karaf-maven-plugin:

 1/ on master, I refactored the karaf-maven-plugin to use the Maven
 annotations. It's simpler and cleaner, and compatible with all Maven
 version. I also added the Maven 3.1 and 3.2 support. I also fixed the
 same
 issue as on karaf-3.0.x (see below) and cleanup the code (using global
 I propose the following cleanup/refactoring/renaming on the goals:
 - karaf:commands-generate-help renamed to karaf:commands-documentation
 - karaf:create-instance-archive renamed to karaf:instance-archive
 - karaf:features-add-to-repository renamed to karaf:populate-repository
 - karaf:features-create-kar renamed to karaf:create-kar
 - karaf:features-export-meta-data renamed to karaf:export-metadata
 - karaf:features-generate-descriptor renames to karaf:create-features
 - karaf:features-validate-descriptor renamed to karaf:validate-features
 Introduction of new goals:
 - karaf:client to interact with a running instance
 - karaf:instance to interact with instances (start, stop, etc)
 - karaf:deploy to deploy bundles or features (and eventually populate
 the
 system repository using scp)
 - karaf:run to bootstrap and run a Karaf container
 I also merged the scr-karaf-maven-plugin in karaf-maven-plugin as a
 dedicated goal (karaf:scr).
 2/ on karaf-3.0.x branch, I introduced a set of new integration tests
 (using
 the maven-invoker-plugin). I fixed the different issues (construct
 global
 features set to resolve all features including transitive ones,
 support of
 file and http URLs, support of  in features repository XML,
 etc).

 Thoughts ?

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

>>>
>>
>
>

Re: [VOTE] Release Apache Karaf version 2.3.4

[Andreas Pieber]

+1 (binding)

Kind regards,
Andreas


On Sun, Feb 16, 2014 at 1:11 AM, Christian Schneider <
ch...@die-schneider.net> wrote:

> +1 (non binding)
>
> Did some simple tests on windows and linux. CXF and camel also seem to
> install fine.
> The zips and tar.gz seem to be complete and license also looks good.
>
> Christian
>
> Am 15.02.2014 03:09, schrieb Jamie G.:
>
>  Hi,
>>
>> We resolved 116 issues in this release (web page will be published post RC
>> promotion):
>> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/
>> webapp/index/community/download/karaf-2.3.4-release.page
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1000/
>>
>> Repository: karaf
>> Updated Tags:  refs/tags/karaf-2.3.4 [created] 653d885f4
>>
>> 2.3.x Dependencies table:
>> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/
>> webapp/index/documentation/karaf-dependencies/karaf-deps-
>> 2.3.x.page
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.
>>
>>
>
> --
>  Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
>

Re: [VOTE] Apache Karaf Cave 2.3.0 release

[Andreas Pieber]

+1 (binding)

Kind regards,
Andreas


On Thu, Jan 16, 2014 at 9:42 AM, Freeman Fang wrote:

> +1 (binding)
> －
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
>
>
>
> On 2014-1-12, at 上午1:32, Jean-Baptiste Onofré wrote:
>
> > Hi,
> >
> > I submit the first release of Apache Karaf Cave (2.3.0) to your vote.
> >
> > Release Notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12317874
> >
> > Staging Repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-021/
> >
> > Git tag:
> > cave-2.3.0
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Do not the release (please provide specific comments)
> >
> > This vote will be open for 72 hours.
> >
> > NB: I will publish the manual if the vote passes.
> >
> > Regards
> > JB
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>
>

Re: [VOTE] Release Apache Karaf version 3.0.0

[Andreas Pieber]

Compiling either the tag or the source archive works like a charm. Tested
with various use cases which also did what they should.

+1 (binding)

Kind regards,
Andreas


On Sun, Dec 22, 2013 at 4:32 AM, Jon Anstey  wrote:

> +1 non binding. Will be nice to see this one go out :-) Great job guys!
> On Dec 21, 2013 2:11 PM, "Jamie G."  wrote:
>
> > Hi,
> >
> > We resolved 1158 issues in this release:
> >
> >
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-3.0.0-release.page?view=markup
> >
> > Dependency changes can be reviewed here:
> >
> >
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-3.0.x.page?view=markup
> > (The website published table will be updated after vote)
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-013/
> >
> > Git tag:
> > karaf-3.0.0
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote will be open for 72 hours.
> >
>

Re: Git Push Summary

[Andreas Pieber]

Is it really happening? :-) I must dreaming!
On 20 Dec 2013 22:18,  wrote:

> Updated Tags:  refs/tags/karaf-3.0.0 [created] b72aadca5
>

Re: Error while building Karaf trunk

[Andreas Pieber]

do u use maven 3.1.x? If yes pls try to downgrade to 3.0.x

Kind regards,
Andreas


On Thu, Dec 19, 2013 at 6:39 AM, Jean-Baptiste Onofré wrote:

> Hi,
>
> try a complete mvn clean install, it should build the plugin first.
>
> Regards
> JB
>
>
> On 12/19/2013 03:33 AM, Harsh Kumar wrote:
>
>> Hi,
>> While building the trunk i get the following error,
>> [ERROR] Plugin org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT
>> or one of its dependencies could not be resolved: Could not find artifact
>> org.apache.karaf.tooling:karaf-maven-plugin:jar:3.0.0-SNAPSHOT -> [Help
>> 1]
>>
>> Would someone please help me resolve it.
>>
>> Regards,
>> Harsh
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: itests (trunk) on Mac osx (now with Java 7)

[Andreas Pieber]

Seams to be probem in RMI remoting. In [1] you find the exception. In [2]
you see a bug which might be connected to it. I only did a VERY short
googling. But this seams to be kind of the problem.

Kind regards,
Andreas

[1]
http://svn.apache.org/repos/asf/karaf/tags/karaf-2.3.0/tooling/exam/container/src/main/java/org/apache/karaf/tooling/exam/container/internal/RMIRegistry.java

[2] http://bugs.sun.com/view_bug.do?bug_id=7166687


On Thu, Dec 5, 2013 at 4:58 PM, David Bosschaert  wrote:

> Hi all,
>
> I have updated to Java 7 on my Mac and am getting the errors below
> with the itests [1]. They work fine for me on Linux. Also note that
> all the other maven modules in karaf trunk test/pass fine for me.
> Anyone an idea? I'm using the following Java:
>   $ java -version
>   java version "1.7.0_45"
>   Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
>   Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
>
> Thanks,
>
> David
>
> [1] All the itests fail as follows:
> java.util.ServiceConfigurationError:
> org.ops4j.pax.exam.TestContainerFactory: Provider
> org.ops4j.pax.exam.karaf.container.internal.KarafTestContainerFactory
> could not be instantiated: java.lang.IllegalStateException: Cannot
> select localhost. That usually not a good sign for networking..
> at java.util.ServiceLoader.fail(ServiceLoader.java:224)
> at java.util.ServiceLoader.access$100(ServiceLoader.java:181)
> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:377)
> at java.util.ServiceLoader$1.next(ServiceLoader.java:445)
> at
> org.ops4j.pax.exam.spi.PaxExamRuntime.sanityCheck(PaxExamRuntime.java:172)
> at
> org.ops4j.pax.exam.spi.PaxExamRuntime.getTestContainerFactory(PaxExamRuntime.java:69)
> at
> org.ops4j.pax.exam.spi.reactors.ReactorManager.createsTestContainerFactory(ReactorManager.java:335)
> at
> org.ops4j.pax.exam.spi.reactors.ReactorManager.createReactor(ReactorManager.java:308)
> at
> org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184)
> at
> org.ops4j.pax.exam.junit.impl.ProbeRunner.(ProbeRunner.java:80)
> at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82)
> at org.ops4j.pax.exam.junit.PaxExam.(PaxExam.java:73)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31)
> at
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
> at
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
> at
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
> at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Caused by: java.lang.IllegalStateException: Cannot select localhost.
> That usually not a good sign for networking..
> at
> org.ops4j.pax.exam.karaf.container.internal.RMIRegistry.(RMIRegistry.java:51)
> at
> org.ops4j.pax.exam.karaf.container.internal.KarafTestContainerFactory.(KarafTestContainerFactory.java:46)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:374)
> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:373)
> ... 31 more
>

Re: A Blueprint Free Karaf

[Andreas Pieber]

I would also be for 4.0. IMHO we dont have to wait all that long for a a
major as we do/did for 3.x

Kind regards,
Andreas


On Thu, Dec 5, 2013 at 10:14 AM, Achim Nierbeck wrote:

> Guillaume,
>
> that's why I would go for 4.0 :)
>
> regards, Achim
>
>
> 2013/12/5 Guillaume Nodet 
>
> > Forking a git repo is really the easiest way to experiment imho.   If
> > there's a consensus, we can port all the changes to the karaf repo and
> > maintain it in Karaf, else it will certainly be dropped.
> >
> > +1 too on both ideas (trim down minimal and switch to scr)
> >
> > The question I wonder about is which version to put that in.  I don't
> > really see that as a minor change, so I'm tempted to push that into 3.0,
> > but if we do, it will delay it even more.
> >
> >
> >
> > 2013/12/5 Andreas Pieber 
> >
> > > I'm with David on this one. I would even have no problems if the
> minimal
> > > distribution would really look like your fork. The only problem is that
> > > forking isn't just the best way to maintain a project :-)
> > >
> > > Kind regards,
> > > Andreas
> > >
> > >
> > > On Wed, Dec 4, 2013 at 10:00 PM, David Jencks  > > >wrote:
> > >
> > > > Great idea!  I think that scr/ds is better suited to framework
> service
> > > > wiring than blueprint.
> > > >
> > > > thanks
> > > > david jencks
> > > >
> > > > On Dec 4, 2013, at 12:48 PM, Hadrian Zbarcea 
> > wrote:
> > > >
> > > > > Sounds very interesting. Less is more. I absolutely need to try
> this
> > > :).
> > > > >
> > > > > Thanks,
> > > > > Hadrian
> > > > >
> > > > > On 12/04/2013 03:41 PM, Ioannis Canellos wrote:
> > > > >> For anyone curious on how Karaf without Blueprint would look like,
> > > > >> here is a karaf branch that is free of blueprint:
> > > > >> https://github.com/iocanel/karaf/tree/karaf-light (it's a fork of
> > the
> > > > >> karat-2.3.x branch).
> > > > >>
> > > > >> It is actually a refactored karaf 2.3.x that removes blueprint
> from
> > > > >> all modules (yet still provides blueprint as feaures). Karaf
> > specific
> > > > >> blueprint namespace handlers have moved to optional bundles so
> that
> > > > >> they can still be used if needed.
> > > > >> Blueprint has been replaced with Felix SCR (including the shell
> > > > >> commands). Moreover, misc refactorings on features and startup
> > bundles
> > > > >> have been performed in order to reduce the size and the amount of
> > > > >> bundles in the minimal distro.
> > > > >>
> > > > >> The result is a minimal distribution that starts 12 bundles [1]
> (out
> > > > >> of 37 which were part of karaf 2.3.3 minimal distro). 10 of those
> > > > >> bundle were blueprint bundles and the rest are extra noise.
> > > > >>
> > > > >> My motivation behind this refactoring was:
> > > > >> i) I like declarative services more than blueprint.
> > > > >> ii) I've been working on projects that are packaged inside the
> karaf
> > > > >> minimal distro which would benefit from a smaller size (e.g.
> > > > >> jclouds-cli).
> > > > >> iii) I wanted to make a karaf distro as flexible as possible.
> > > > >>
> > > > >> Please note that my main focus was the minimal distribution and
> also
> > > > >> this is not 100% polished.
> > > > >>
> > > > >> Enjoy!
> > > > >>
> > > > >>
> > > > >> [1]: The bundle list of the minimal distro:
> > > > >>
> > > > >>ID   State Level  Name
> > > > >> [   0] [Active ] [0] System Bundle (4.0.3)
> > > > >> [   1] [Active ] [5] OPS4J Pax Url - mvn: (1.3.6)
> > > > >> [   2] [Active ] [5] OPS4J Pax Url - wrap: (1.3.6)
> > > > >> [   3] [Active ] [8] OPS4J Pax Logging - API (1.7.1)
> > > > >> [   4] [Active ] [8] OPS4J Pax Logging - Service (1.7.1)
> > > > >> [   5] [Active ] [   10] Apache Felix Configuration Admin
> > Service
> > > > (1.6.0)
> > > > >> [   6] [Active ] [   11] Apache Felix File Install (3.2.6)
> > > > >> [   7] [Active ] [   13] Apache Felix Declarative Services
> > (1.6.2)
> > > > >> [   8] [Active ] [   25] Apache Karaf :: Shell :: Console
> > > > (2.3.4.SNAPSHOT)
> > > > >> [   9] [Active ] [   30] Apache Karaf :: Features :: Core
> > > > (2.3.4.SNAPSHOT)
> > > > >> [  10] [Active ] [   30] Apache Karaf :: Features :: Command
> > > > >> (2.3.4.SNAPSHOT)
> > > > >> [  11] [Active ] [   30] Apache Karaf :: Shell :: Log Commands
> > > > >> (2.3.4.SNAPSHOT)
> > > > >> [  12] [Active ] [   30] Apache Karaf :: Shell :: OSGi
> Commands
> > > > >> (2.3.4.SNAPSHOT)
> > > > >>
> > > >
> > > >
> > >
> >
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
> Commiter & Project Lead
> blog <http://notizblog.nierbeck.de/>
>

Re: A Blueprint Free Karaf

[Andreas Pieber]

Even for the a bit fuller one I think. Why should the karaf core need a
dependency on blueprint?

Kind regards, Andreas

PS: for a real adaption to karaf I would rather consider this for the 3.x
or 4.x line...
On 5 Dec 2013 06:40, "Achim Nierbeck"  wrote:

> yeah, I already did grab myself a copy of it ;)
>
> for the minimal distribution this makes a lot of sense :)
>
> regards, Achim
>
>
> 2013/12/5 Jean-Baptiste Onofré 
>
> > Hi Ioannis,
> >
> > it sounds interesting. I gonna take a look on that.
> >
> > Regards
> > JB
> >
> >
> > On 12/04/2013 09:41 PM, Ioannis Canellos wrote:
> >
> >> For anyone curious on how Karaf without Blueprint would look like,
> >> here is a karaf branch that is free of blueprint:
> >> https://github.com/iocanel/karaf/tree/karaf-light (it's a fork of the
> >> karat-2.3.x branch).
> >>
> >> It is actually a refactored karaf 2.3.x that removes blueprint from
> >> all modules (yet still provides blueprint as feaures). Karaf specific
> >> blueprint namespace handlers have moved to optional bundles so that
> >> they can still be used if needed.
> >> Blueprint has been replaced with Felix SCR (including the shell
> >> commands). Moreover, misc refactorings on features and startup bundles
> >> have been performed in order to reduce the size and the amount of
> >> bundles in the minimal distro.
> >>
> >> The result is a minimal distribution that starts 12 bundles [1] (out
> >> of 37 which were part of karaf 2.3.3 minimal distro). 10 of those
> >> bundle were blueprint bundles and the rest are extra noise.
> >>
> >> My motivation behind this refactoring was:
> >> i) I like declarative services more than blueprint.
> >> ii) I've been working on projects that are packaged inside the karaf
> >> minimal distro which would benefit from a smaller size (e.g.
> >> jclouds-cli).
> >> iii) I wanted to make a karaf distro as flexible as possible.
> >>
> >> Please note that my main focus was the minimal distribution and also
> >> this is not 100% polished.
> >>
> >> Enjoy!
> >>
> >>
> >> [1]: The bundle list of the minimal distro:
> >>
> >> ID   State Level  Name
> >> [   0] [Active ] [0] System Bundle (4.0.3)
> >> [   1] [Active ] [5] OPS4J Pax Url - mvn: (1.3.6)
> >> [   2] [Active ] [5] OPS4J Pax Url - wrap: (1.3.6)
> >> [   3] [Active ] [8] OPS4J Pax Logging - API (1.7.1)
> >> [   4] [Active ] [8] OPS4J Pax Logging - Service (1.7.1)
> >> [   5] [Active ] [   10] Apache Felix Configuration Admin Service
> >> (1.6.0)
> >> [   6] [Active ] [   11] Apache Felix File Install (3.2.6)
> >> [   7] [Active ] [   13] Apache Felix Declarative Services (1.6.2)
> >> [   8] [Active ] [   25] Apache Karaf :: Shell :: Console
> >> (2.3.4.SNAPSHOT)
> >> [   9] [Active ] [   30] Apache Karaf :: Features :: Core
> >> (2.3.4.SNAPSHOT)
> >> [  10] [Active ] [   30] Apache Karaf :: Features :: Command
> >> (2.3.4.SNAPSHOT)
> >> [  11] [Active ] [   30] Apache Karaf :: Shell :: Log Commands
> >> (2.3.4.SNAPSHOT)
> >> [  12] [Active ] [   30] Apache Karaf :: Shell :: OSGi Commands
> >> (2.3.4.SNAPSHOT)
> >>
> >>
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
>
>
> --
>
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> OPS4J Pax for Vaadin 
> Commiter & Project Lead
> blog 
>

Re: A Blueprint Free Karaf

[Andreas Pieber]

I'm with David on this one. I would even have no problems if the minimal
distribution would really look like your fork. The only problem is that
forking isn't just the best way to maintain a project :-)

Kind regards,
Andreas


On Wed, Dec 4, 2013 at 10:00 PM, David Jencks wrote:

> Great idea!  I think that scr/ds is better suited to framework service
> wiring than blueprint.
>
> thanks
> david jencks
>
> On Dec 4, 2013, at 12:48 PM, Hadrian Zbarcea  wrote:
>
> > Sounds very interesting. Less is more. I absolutely need to try this :).
> >
> > Thanks,
> > Hadrian
> >
> > On 12/04/2013 03:41 PM, Ioannis Canellos wrote:
> >> For anyone curious on how Karaf without Blueprint would look like,
> >> here is a karaf branch that is free of blueprint:
> >> https://github.com/iocanel/karaf/tree/karaf-light (it's a fork of the
> >> karat-2.3.x branch).
> >>
> >> It is actually a refactored karaf 2.3.x that removes blueprint from
> >> all modules (yet still provides blueprint as feaures). Karaf specific
> >> blueprint namespace handlers have moved to optional bundles so that
> >> they can still be used if needed.
> >> Blueprint has been replaced with Felix SCR (including the shell
> >> commands). Moreover, misc refactorings on features and startup bundles
> >> have been performed in order to reduce the size and the amount of
> >> bundles in the minimal distro.
> >>
> >> The result is a minimal distribution that starts 12 bundles [1] (out
> >> of 37 which were part of karaf 2.3.3 minimal distro). 10 of those
> >> bundle were blueprint bundles and the rest are extra noise.
> >>
> >> My motivation behind this refactoring was:
> >> i) I like declarative services more than blueprint.
> >> ii) I've been working on projects that are packaged inside the karaf
> >> minimal distro which would benefit from a smaller size (e.g.
> >> jclouds-cli).
> >> iii) I wanted to make a karaf distro as flexible as possible.
> >>
> >> Please note that my main focus was the minimal distribution and also
> >> this is not 100% polished.
> >>
> >> Enjoy!
> >>
> >>
> >> [1]: The bundle list of the minimal distro:
> >>
> >>ID   State Level  Name
> >> [   0] [Active ] [0] System Bundle (4.0.3)
> >> [   1] [Active ] [5] OPS4J Pax Url - mvn: (1.3.6)
> >> [   2] [Active ] [5] OPS4J Pax Url - wrap: (1.3.6)
> >> [   3] [Active ] [8] OPS4J Pax Logging - API (1.7.1)
> >> [   4] [Active ] [8] OPS4J Pax Logging - Service (1.7.1)
> >> [   5] [Active ] [   10] Apache Felix Configuration Admin Service
> (1.6.0)
> >> [   6] [Active ] [   11] Apache Felix File Install (3.2.6)
> >> [   7] [Active ] [   13] Apache Felix Declarative Services (1.6.2)
> >> [   8] [Active ] [   25] Apache Karaf :: Shell :: Console
> (2.3.4.SNAPSHOT)
> >> [   9] [Active ] [   30] Apache Karaf :: Features :: Core
> (2.3.4.SNAPSHOT)
> >> [  10] [Active ] [   30] Apache Karaf :: Features :: Command
> >> (2.3.4.SNAPSHOT)
> >> [  11] [Active ] [   30] Apache Karaf :: Shell :: Log Commands
> >> (2.3.4.SNAPSHOT)
> >> [  12] [Active ] [   30] Apache Karaf :: Shell :: OSGi Commands
> >> (2.3.4.SNAPSHOT)
> >>
>
>

Re: Board Report for December, 2013

[Andreas Pieber]

Looks good to me too; +1

Kind regards,
Andreas


On Fri, Nov 22, 2013 at 1:58 PM, Jean-Baptiste Onofré wrote:

> Hi all,
>
> I prepared the Board Report for December, 2013:
>
> https://cwiki.apache.org/confluence/display/KARAF/Board+Reports
>
> Please review it.
>
> I will update the report with the latest numbers end of November.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Versioning of command apis

[Andreas Pieber]

For the API externalisation: +1; BUT really externalized. Which means only
in a different project. Otherwise it could get quite interesting if e.g. we
need to release something differently in the 2.x branches.

For the second point I'm completely with JB (-1)

Kind regards,
Andreas


On Thu, Nov 14, 2013 at 2:12 PM, Jean-Baptiste Onofré wrote:

> +1 and -1
>
> +1 for have a clean API and externalized, with a cleaner versioning for
> Karaf 4.
>
> -1 to revert the move that we did in Karaf 3. We did this move 1 year
> before, it gives time to test and move for the other projects. I'm not OK
> to move now, at 1 week for Karaf 3.0.0. We released Karaf 3.0.0.RC1 like
> this. I'm fully OK to add a backward compatible module, to easily migrate,
> but not to revert.
>
> Regards
> JB
>
>
> On 11/14/2013 10:21 AM, Christian Schneider wrote:
>
>> As you all know we had and still some compatibility problems with
>> bundles that implement commands externally from karaf. CXF and Camel
>> work now but ActiveMQ still does not work with karaf 3.
>>
>> There are two kinds of problems that appear with the switch to karaf 3.
>>
>> 1. We moved the classes from org.apache.felix.gogo.commands and
>> org.apache.felix.gogo.commands.basic to org.apache.karaf.shell.commands
>> and org.apache.karaf.shell.commands.basic.
>> 2. The org.apache.karaf.shell.console package and subpackages are
>> exported as version 3.0.0 now which is by default incompatible with auto
>> generated import ranges.
>>
>> For problem 1 we created deprecated old classes at the old place which
>> allows people to migrate.
>> For problem 2 all external command bundles need to increase their import
>> range to include 3.x. The problem will reappear with version 4.
>>
>> I just discussed with Achim on irc what to do and we agreed that for
>> problem 2 a much better solution would be to introduce a versioning on
>> package level. This requires a lot more care and effort than what we now
>> do though.
>>
>> So my question is. Should we start versioning at least this api on
>> package level and what rules should be in place to make sure it works?
>>
>> When I look into the packages from shell.console I think that these are
>> not real api packages as of now. They contain some classes that rather
>> qualify as implementation like AbstractAction and
>> DefaultActionPreparator as they contain much code. At the moment these
>> packages can not be split easily from the minimal api we need to
>> provide. So I am not sure if we are already at a stage were we can do
>> good api versioning. So I wonder if we perhaps keep the api mostly
>> unchanged for karaf 3 and do a bigger redesign of the command apis for
>> karaf 4.
>>
>> If we decide to go this way it would be more consistent to revert the
>> move of the classes described in problem 1. This would then make sure
>> that users of karaf commands only need to do the change once. For
>> problem 2 we might simply define one fixed export version for command
>> apis in karaf 3.x like (2.3.0). This version would be compatible to old
>> external commands and we could use the same version for karaf 2.x
>> starting with 2.4. So we would stay very compatible for now and spare
>> the real changes for karaf 4. We could start these changes in a kind of
>> preview api in karaf 3.x and formalize it at some point which would then
>> become the karaf 4 command api.
>>
>> What do you think?
>>
>> Christian
>>
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Build failure on Karaf trunk...

[Andreas Pieber]

3.1.x does not work by now. Since the karaf plugin does not use the
abstraction layer this terribly fails with the new maven version --> 3.0.x
should work

Kind regards,
Andreas


On Fri, Oct 25, 2013 at 5:37 PM, David Bosschaert <
david.bosscha...@gmail.com> wrote:

> I was actually using the default mvn install on my system which is 3.0.3.
> I just tried with 3.1.1 which gives me a slightly similar error (below).
>
> What Maven version should work?
>
> Cheers,
>
> David
>
> The error with maven 3.1.1:
> [ERROR] Failed to execute goal
>
> org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT:features-generate-descriptor
> (compile) on project framework: Execution compile of goal
>
> org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT:features-generate-descriptor
> failed: Unable to load the mojo 'features-generate-descriptor' (or one
> of its required components) from the plugin
> 'org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT':
> com.google.inject.ProvisionException: Guice provision errors:
> [ERROR]
> [ERROR] 1) No implementation for org.sonatype.aether.RepositorySystem was
> bound.
> [ERROR] while locating
> org.apache.karaf.tooling.features.GenerateDescriptorMojo
> [ERROR] at
> ClassRealm[plugin>org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT,
> parent: sun.misc.Launcher$AppClassLoader@7987aeca]
> [ERROR] while locating org.apache.maven.plugin.Mojo annotated with
>
> @com.google.inject.name.Named(value=org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT:features-generate-descriptor)
> [ERROR]
> [ERROR] 1 error
> [ERROR] role: org.apache.maven.plugin.Mojo
> [ERROR] roleHint:
>
> org.apache.karaf.tooling:karaf-maven-plugin:3.0.0-SNAPSHOT:features-generate-descriptor
>
> On 25 October 2013 16:27, nseb  wrote:
> > You use maven 3.1.0 ?
> >
> >
> >
> > --
> > View this message in context:
> http://karaf.922171.n3.nabble.com/Build-failure-on-Karaf-trunk-tp4030054p4030055.html
> > Sent from the Karaf - Dev mailing list archive at Nabble.com.
>

Re: [VOTE] Apache Karaf Cellar 2.3.2 release

[Andreas Pieber]

+1 (binding)

kind regards,
Andreas


On Mon, Oct 14, 2013 at 9:05 PM, Achim Nierbeck wrote:

> +1 (binding)
>
> regards, Achim
>
>
> 2013/10/13 Christian Schneider 
>
> > +1 (non binding)
> >
> > Christian
> >
> > Am 11.10.2013 19:39, schrieb Jean-Baptiste Onofré:
> >
> >  Hi all,
> >>
> >> I submit Apache Karaf Cellar 2.3.2 release to your vote.
> >>
> >> This is a major update on the cellar-2.3.x branch, fully compatible with
> >> Karaf 2.3.x, including major bug fixes.
> >>
> >> Release Notes:
> >> http://svn.apache.org/repos/**asf/karaf/cellar/tags/cellar-**
> >> 2.3.2/RELEASE-NOTES<
> http://svn.apache.org/repos/asf/karaf/cellar/tags/cellar-2.3.2/RELEASE-NOTES
> >
> >>
> >> Staging repository:
> >> https://repository.apache.org/**content/repositories/**
> >> orgapachekaraf-164/<
> https://repository.apache.org/content/repositories/orgapachekaraf-164/>
> >>
> >> 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.
> >>
> >> Thanks
> >> Regards
> >> JB
> >>
> >
> >
> > --
> >  Christian Schneider
> > http://www.liquid-reality.de
> >
> > Open Source Architect
> > Talend Application Integration Division http://www.talend.com
> >
> >
>
>
> --
>
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> OPS4J Pax for Vaadin 
> Commiter & Project Lead
> blog 
>

Re: Null Pointer in comand dynamic-import

[Andreas Pieber]

not by definition, but an issue with the version where to apply your patch
and the error message would be fine independently.

Kind regards,
Andreas


On Wed, Oct 2, 2013 at 10:39 PM, nseb  wrote:

> I must create an issue ?
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Null-Pointer-in-comand-dynamic-import-tp4029798p4029817.html
> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>

Re: Board Report for September 2013

[Andreas Pieber]

+1

Kind regards, Andreas
On Sep 1, 2013 10:01 PM, "Achim Nierbeck"  wrote:

> hi ,
>
> +1, looks good to me.
>
> regards, Achim
>
>
> 2013/9/1 Jean-Baptiste Onofré 
>
> > Hi all,
> >
> > I prepared the Board Report for September 2013:
> > https://cwiki.apache.org/**confluence/display/KARAF/**Board+Reports<
> https://cwiki.apache.org/confluence/display/KARAF/Board+Reports>
> >
> > Please, review it as I would like to submit asap.
> >
> > Thanks !
> >
> > Regards
> > JB
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
>
>
> --
>
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> OPS4J Pax for Vaadin 
> Commiter & Project Lead
> blog 
>

Problems with new maven version

[Andreas Pieber]

Hey guys,

I've kind of a problem with KARAF-2395 [1]. While I've a patch making
everything compatible to maven 3.1.x it's incompatible then to maven 3.0.x.
Thanks to the way we're using aether the only real option I see is to
either set the minimum maven version to 3.1 or provide two commands; one
for 3.0 and one for 3.1. Both solutions don't feel ideal for me. Any
ideas/proposals how to progress?

Kind regards,
Andreas

[1]https://issues.apache.org/jira/browse/KARAF-2395

Re: [VOTE] Switch from svn to git

[Andreas Pieber]

+1 :-)

Kind regards,
Andreas


On Fri, Aug 9, 2013 at 8:23 AM, Łukasz Dywicki  wrote:

> Can we finish this vote and move forward to git? :)
>
> Cheers,
> Łukasz Dywicki
> --
> l...@code-house.org
> Twitter: ldywicki
> Blog: http://dywicki.pl
> Code-House - http://code-house.org
>
> Wiadomość napisana przez Christian Müller  w
> dniu 17 lip 2013, o godz. 00:00:
>
> > Apache Camel is using Git since a few weeks now without any issue. We
> also
> > did three releases in this time without any problems. Feel free to ask if
> > you need any assistance/help. I like to help...
> >
> > Best,
> > Christian
> > -
> >
> > Software Integration Specialist
> >
> > Apache Camel committer: https://camel.apache.org/team
> > V.P. Apache Camel: https://www.apache.org/foundation/
> > Apache Member: https://www.apache.org/foundation/members.html
> >
> > https://www.linkedin.com/pub/christian-mueller/11/551/642
> >
> >
> > On Tue, Jun 25, 2013 at 11:12 AM, Jean-Baptiste Onofré  >wrote:
> >
> >> Hi all,
> >>
> >> to follow the discussion that we had some weeks ago, I start here a
> formal
> >> vote to migrate our scm from svn to git.
> >>
> >> Please vote to approve this switch:
> >>
> >> [ ] +1 Approve the switch (from svn to git)
> >> [ ] -1 Do not approve the switch (please provide specific comments)
> >>
> >> This vote will be open for 72 hours.
> >>
> >> Thanks,
> >> Regards
> >> JB
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
>
>

Re: [VOTE] Release Apache Karaf 2.3.2

[Andreas Pieber]

Did it worked on 2.3.1?

Kind regards,
Andreas


On Wed, Jul 10, 2013 at 4:00 PM, semethyjr  wrote:

> I tried adding war and webconsole features to featuresBoot.  I get the
> following exception thrown in karaf.log on start up.  Running on RHEL 6.4.
>
> org.apache.karaf.features.cfg
>
> featuresBoot=config,ssh,management,kar,war,webconsole
>
> karaf.log
> 2013-07-09 15:56:01,205 | ERROR | rint Extender: 1 | WebApplication
> | iteboard.internal.WebApplication  229 | 77 -
> org.ops4j.pax.web.pax-web-extender-whiteboard - 1.1.14 | Registration
> skipped for
>
> [ListenerWebElement{mapping=DefaultListenerMapping{httpContextId=null,listener=org.apache.karaf.deployer.features.FeatureDeploymentListener@13bdbb15
> }}]
> due to error during registration
> java.lang.IllegalArgumentException: Listener
> [org.apache.karaf.deployer.features.FeatureDeploymentListener@13bdbb15]
> already registered.
> at
>
> org.ops4j.pax.web.service.spi.model.ServiceModel.addEventListenerModel(ServiceModel.java:90)[74:org.ops4j.pax.web.pax-web-spi:1.1.14]
> at
>
> org.ops4j.pax.web.service.internal.HttpServiceStarted.registerEventListener(HttpServiceStarted.java:358)[75:org.ops4j.pax.web.pax-web-runtime:1.1.14]
> at
>
> org.ops4j.pax.web.service.internal.HttpServiceProxy.registerEventListener(HttpServiceProxy.java:133)[75:org.ops4j.pax.web.pax-web-runtime:1.1.14]
> at
>
> org.ops4j.pax.web.extender.whiteboard.internal.element.ListenerWebElement.register(ListenerWebElement.java:63)[77:org.ops4j.pax.web.pax-web-extender-whiteboard:1.1.14]
> at
>
> org.ops4j.pax.web.extender.whiteboard.internal.WebApplication.registerWebElement(WebApplication.java:224)[77:org.ops4j.pax.web.pax-web-extender-whiteboard:1.1.14]
> at
>
> org.ops4j.pax.web.extender.whiteboard.internal.WebApplication.addWebElement(WebApplication.java:102)[77:org.ops4j.pax.web.pax-web-extender-whiteboard:1.1.14]
> at
>
> org.ops4j.pax.web.extender.whiteboard.internal.tracker.AbstractTracker.addingService(AbstractTracker.java:139)[77:org.ops4j.pax.web.pax-web-extender-whiteboard:1.1.14]
> at
>
> org.ops4j.pax.web.extender.whiteboard.internal.tracker.ListenerTracker.addingService(ListenerTracker.java:36)[77:org.ops4j.pax.web.pax-web-extender-whiteboard:1.1.14]
> at
>
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932)[karaf.jar:2.3.2-SNAPSHOT]
> at
>
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:1)[karaf.jar:2.3.2-SNAPSHOT]
> at
>
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)[karaf.jar:2.3.2-SNAPSHOT]
> at
>
> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)[karaf.jar:2.3.2-SNAPSHOT]
> at
>
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:894)[karaf.jar:2.3.2-SNAPSHOT]
> at
>
> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)[org.apache.felix.framework-4.0.3.jar:]
> at
>
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)[org.apache.felix.framework-4.0.3.jar:]
> at
>
> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)[org.apache.felix.framework-4.0.3.jar:]
> at
>
> org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4260)[org.apache.felix.framework-4.0.3.jar:]
> at
>
> org.apache.felix.framework.Felix.registerService(Felix.java:3275)[org.apache.felix.framework-4.0.3.jar:]
> at
>
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)[org.apache.felix.framework-4.0.3.jar:]
> at
>
> org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:439)[7:org.apache.aries.blueprint.core:1.1.0]
> at
>
> org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:190)[7:org.apache.aries.blueprint.core:1.1.0]
> at
>
> org.apache.aries.blueprint.container.BlueprintContainerImpl.notifySatisfaction(BlueprintContainerImpl.java:640)[7:org.apache.aries.blueprint.core:1.1.0]
> at
>
> org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe.setSatisfied(AbstractServiceReferenceRecipe.java:408)[7:org.apache.aries.blueprint.core:1.1.0]
> at
>
> org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe.serviceAdded(AbstractServiceReferenceRecipe.java:345)[7:org.apache.aries.blueprint.core:1.1.0]
> at
>
> org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe.access$000(AbstractServiceReferenceRecipe.java:72)[7:org.apache.aries.blueprint.core:1.1.0]
> at
>
> org.apache.aries.blueprint.container.AbstractServiceReferenceRecipe$3.run(AbstractServiceReferenceRecipe.java:318)[7:org.apache.aries.blueprint.core:1.1.0]
> at
>
> java.util.concurrent.Executors$Runnabl

Re: [VOTE] Release Apache Karaf 2.3.2

[Andreas Pieber]

finally the build works :-) +1

Kind regards,
Andreas


On Sun, Jul 7, 2013 at 3:47 PM, Jamie G.  wrote:

> Hi,
>
> We resolved 67 issues in this release (web page will be published post RC
> promotion):
>
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-
> 2.3.2-release.page
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-108
>
> Release tags:
> https://svn.apache.org/repos/asf/karaf/tags/karaf-2.3.2/
>
> 2.3.x Dependencies table:
>
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-
> 2.3.x.page
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>

Re: [VOTE] Release Apache Karaf 2.3.2 (second try)

[Andreas Pieber]

Sry for the delay... org.apache.karaf.shell.commands.WcTest is the only one
with test failures.

Kind regards,
Andreas


On Fri, Jul 5, 2013 at 1:12 PM, Jamie G.  wrote:

> Any more issues found Andreas?
>
> To make it official, this RC of Karaf 2.3.2 has been cancelled. I've
> dropped the staged RC and removed the tags.
>
>
> On Fri, Jul 5, 2013 at 2:54 AM, Andreas Pieber  wrote:
>
> > I'll try to run without build failing on test failures. Lets see if I can
> > discover any more failures.
> >
> > Kind regards,
> > Andreas
> >
> >
> > On Fri, Jul 5, 2013 at 6:03 AM, Jamie G. 
> wrote:
> >
> > > This is very strange, I set these tests to ignore in the source... I
> > agree
> > > that failed builds of the release candidate requires  minus one. While
> > this
> > > rc kit is still up are there any other test failures any one is
> observing
> > > on other platforms?
> > >
> > > On Friday, July 5, 2013, Andreas Pieber wrote:
> > >
> > > > This is kind of a PITA :-( While building the tag works without any
> > > > problems the source download still doesn't work. And this is the
> > artifact
> > > > we've to vote on I'm afraid. On Linux the following tests fail:
> > > >
> > > > Failed tests:
> > > > testOneFileWordCounts(org.apache.karaf.shell.commands.WcTest): A
> single
> > > > file report should not contain a total count row expected:< 3[4
> > 487
> > > >3307]   WcActionTestLarge.t...> but was:<   3[5 487
> > 3308]
> > > > WcActionTestLarge.t...>
> > > >   testLargeStringWordCounts(org.apache.karaf.shell.commands.WcTest):
> > The
> > > > expected lineCount should be equal expected:<34> but was:<35>
> > > >   testThreeFilesWordCounts(org.apache.karaf.shell.commands.WcTest): A
> > > > single file report should not contain a total expected:<  1[1 12
> > > >  34  WcActionTestSmall.txt(..)
> > > >
> > > >
> > > > -1 :-(
> > > >
> > > > Kind regards,
> > > > Andreas
> > > >
> > > >
> > > > On Thu, Jul 4, 2013 at 9:22 PM, Jamie G.  > > >
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > We resolved 66 issues in this release (web page will be published
> > post
> > > RC
> > > > > promotion):
> > > > >
> > > > >
> > > >
> > >
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-
> > > > > 2.3.2-release.page
> > > > >
> > > > > Staging repository:
> > > > >
> > https://repository.apache.org/content/repositories/orgapachekaraf-103/
> > > > >
> > > > > Release tags:
> > > > > https://svn.apache.org/repos/asf/karaf/tags/karaf-2.3.2/
> > > > >
> > > > > 2.3.x Dependencies table:
> > > > >
> > > > >
> > > >
> > >
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-
> > > > > 2.3.x.page
> > > > >
> > > > > Please vote to approve this release:
> > > > >
> > > > > [ ] +1 Approve the release
> > > > > [ ] -1 Veto the release (please provide specific comments)
> > > > >
> > > > > This vote will be open for 72 hours.
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Karaf 2.3.2 (second try)

[Andreas Pieber]

I'll try to run without build failing on test failures. Lets see if I can
discover any more failures.

Kind regards,
Andreas


On Fri, Jul 5, 2013 at 6:03 AM, Jamie G.  wrote:

> This is very strange, I set these tests to ignore in the source... I agree
> that failed builds of the release candidate requires  minus one. While this
> rc kit is still up are there any other test failures any one is observing
> on other platforms?
>
> On Friday, July 5, 2013, Andreas Pieber wrote:
>
> > This is kind of a PITA :-( While building the tag works without any
> > problems the source download still doesn't work. And this is the artifact
> > we've to vote on I'm afraid. On Linux the following tests fail:
> >
> > Failed tests:
> > testOneFileWordCounts(org.apache.karaf.shell.commands.WcTest): A single
> > file report should not contain a total count row expected:< 3[4   487
> >3307]   WcActionTestLarge.t...> but was:<   3[5 487 3308]
> > WcActionTestLarge.t...>
> >   testLargeStringWordCounts(org.apache.karaf.shell.commands.WcTest): The
> > expected lineCount should be equal expected:<34> but was:<35>
> >   testThreeFilesWordCounts(org.apache.karaf.shell.commands.WcTest): A
> > single file report should not contain a total expected:<  1[1 12
> >  34  WcActionTestSmall.txt(..)
> >
> >
> > -1 :-(
> >
> > Kind regards,
> > Andreas
> >
> >
> > On Thu, Jul 4, 2013 at 9:22 PM, Jamie G.  >
> > wrote:
> >
> > > Hi,
> > >
> > > We resolved 66 issues in this release (web page will be published post
> RC
> > > promotion):
> > >
> > >
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-
> > > 2.3.2-release.page
> > >
> > > Staging repository:
> > > https://repository.apache.org/content/repositories/orgapachekaraf-103/
> > >
> > > Release tags:
> > > https://svn.apache.org/repos/asf/karaf/tags/karaf-2.3.2/
> > >
> > > 2.3.x Dependencies table:
> > >
> > >
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-
> > > 2.3.x.page
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > This vote will be open for 72 hours.
> > >
> >
>

Re: [VOTE] Release Apache Karaf 2.3.2 (second try)

[Andreas Pieber]

This is kind of a PITA :-( While building the tag works without any
problems the source download still doesn't work. And this is the artifact
we've to vote on I'm afraid. On Linux the following tests fail:

Failed tests:
testOneFileWordCounts(org.apache.karaf.shell.commands.WcTest): A single
file report should not contain a total count row expected:< 3[4   487
   3307]   WcActionTestLarge.t...> but was:<   3[5 487 3308]
WcActionTestLarge.t...>
  testLargeStringWordCounts(org.apache.karaf.shell.commands.WcTest): The
expected lineCount should be equal expected:<34> but was:<35>
  testThreeFilesWordCounts(org.apache.karaf.shell.commands.WcTest): A
single file report should not contain a total expected:<  1[1 12
 34  WcActionTestSmall.txt(..)


-1 :-(

Kind regards,
Andreas


On Thu, Jul 4, 2013 at 9:22 PM, Jamie G.  wrote:

> Hi,
>
> We resolved 66 issues in this release (web page will be published post RC
> promotion):
>
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-
> 2.3.2-release.page
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-103/
>
> Release tags:
> https://svn.apache.org/repos/asf/karaf/tags/karaf-2.3.2/
>
> 2.3.x Dependencies table:
>
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-
> 2.3.x.page
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>

Re: [VOTE] Release Apache Karaf version 2.3.2

[Andreas Pieber]

I dont like the idea of ignoring tests; maybe we can copy those files which
get modified before the test?

Kind regards,
Andreas


On Thu, Jul 4, 2013 at 8:05 AM, Jean-Baptiste Onofré wrote:

> From the scm it works fine (checkout from karaf-2.3.x branch), but using
> the src tarball, the shell/commands build fails on the WcTest on my machine
> as well.
>
> It could be related to some change (during tagging, etc) on the test
> resources files.
>
> I propose to tag the WcTest as @Ignore (or remove the one that manipulate
> files).
>
> I revert my vote to -1 in order to fix that.
>
> Regards
> JB
>
>
> On 07/04/2013 06:17 AM, Dan Tran wrote:
>
>> I build from tag, passed on centos 5.7 jdk7, but failed on windows 7 wiht
>> jdk7
>>
>> Tests in error:
>>testStopWithTimeout(org.**apache.karaf.main.**MainStartTest): Unable
>> to
>> delete file: C:\Users\Dan.Tran\dev\karaf\**karaf-2.3.2\main\ta
>> rget\test-classes\test-karaf-**home\data\log\karaf.log
>>
>> Tests run: 84, Failures: 0, Errors: 1, Skipped: 6
>>
>> [INFO]
>> --**--**
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Karaf ..** SUCCESS
>> [1.672s]
>> [INFO] Apache Karaf :: Util .......... SUCCESS
>> [2.067s]
>> [INFO] Apache Karaf :: Main .. FAILURE
>> [27.834s]
>>
>>
>> On Wed, Jul 3, 2013 at 8:50 PM, Andreas Pieber 
>> wrote:
>>
>>  Am I the only one receiving the following result on downloading the
>>> -src.tar.gz file and running mvn clean install? I get the same error
>>> using
>>> java 6 and java 7:
>>>
>>> --**-
>>>   T E S T S
>>> --**-
>>> Running org.apache.karaf.shell.**commands.WcTest
>>> Tests run: 5, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.077 sec
>>> <<< FAILURE!
>>> Running org.apache.karaf.shell.**commands.GrepTest
>>> 1
>>> 2
>>> 3
>>> 4
>>> 5
>>> 6
>>> 7
>>> 8
>>> 9
>>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec
>>> Running org.apache.karaf.shell.**commands.SortTest
>>> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
>>>
>>> Results :
>>>
>>> Failed tests:
>>> testLargeStringWordCounts(org.**apache.karaf.shell.commands.**WcTest):
>>> The
>>> expected lineCount should be equal expected:<34> but was:<35>
>>>testOneFileWordCounts(org.**apache.karaf.shell.commands.**WcTest): A
>>> single
>>> file report should not contain a total count row expected:<  3[4 487
>>>3307]   WcActionTestLarge.t...> but was:<   3[5 487 3308]
>>> WcActionTestLarge.t...>
>>>testThreeFilesWordCounts(org.**apache.karaf.shell.commands.**WcTest):
>>> A
>>> single file report should not contain a total expected:< 1[1 12
>>>  34
>>>   WcActionTestSmall.txt(..)
>>>
>>> Tests run: 9, Failures: 3, Errors: 0, Skipped: 0
>>>
>>> [INFO]
>>> --**--**
>>> 
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Apache Karaf ..** SUCCESS
>>> [3.489s]
>>> [INFO] Apache Karaf :: Util .. SUCCESS
>>> [3.572s]
>>> [INFO] Apache Karaf :: Main .. SUCCESS
>>> [40.519s]
>>> [INFO] Apache Karaf :: JAAS .. SUCCESS
>>> [0.166s]
>>> [INFO] Apache Karaf :: JAAS :: Boot .. SUCCESS
>>> [0.712s]
>>> [INFO] Apache Karaf :: JAAS :: Config  SUCCESS
>>> [0.865s]
>>> [INFO] Apache Karaf :: JAAS :: Modules ... SUCCESS
>>> [1.529s]
>>> [INFO] Apache Karaf :: Shell . SUCCESS
>>> [0.116s]
>>> [INFO] Apache Karaf :: Shell :: Console .. SUCCESS
>>> [2.808s]
>>> [INFO] Apache Karaf :: Shell :: OBR Commands . SUCCESS
>>> [0.775s]
>>> [INFO] Apache Karaf :: Features .. SUCCESS
>>> [0.063s]
>>> [INFO] Apache Karaf :: Features :: Core ..

Re: [VOTE] Release Apache Karaf version 2.3.2

[Andreas Pieber]

yep I took the same artifact as used by Dan on the following system:

Linux macroprime 3.9.8-1-ARCH #1 SMP PREEMPT Thu Jun 27 21:37:31 CEST 2013
x86_64 GNU/Linux

Kind regards,
Andreas


On Thu, Jul 4, 2013 at 6:24 AM, Dan Tran  wrote:

> I encounter same linux build issue seen by Andeas using
>
> https://repository.apache.org/content/repositories/orgapachekaraf-102/org/apache/karaf/apache-karaf/2.3.2/apache-karaf-2.3.2-src.tar.gz
>
>
>
>
> On Wed, Jul 3, 2013 at 9:17 PM, Dan Tran  wrote:
>
> > I build from tag, passed on centos 5.7 jdk7, but failed on windows 7 wiht
> > jdk7
> >
> > Tests in error:
> >   testStopWithTimeout(org.apache.karaf.main.MainStartTest): Unable to
> > delete file: C:\Users\Dan.Tran\dev\karaf\karaf-2.3.2\main\ta
> > rget\test-classes\test-karaf-home\data\log\karaf.log
> >
> > Tests run: 84, Failures: 0, Errors: 1, Skipped: 6
> >
> > [INFO]
> > 
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] Apache Karaf .. SUCCESS
> [1.672s]
> > [INFO] Apache Karaf :: Util .. SUCCESS
> [2.067s]
> > [INFO] Apache Karaf :: Main .. FAILURE
> > [27.834s]
> >
> >
> > On Wed, Jul 3, 2013 at 8:50 PM, Andreas Pieber 
> wrote:
> >
> >> Am I the only one receiving the following result on downloading the
> >> -src.tar.gz file and running mvn clean install? I get the same error
> using
> >> java 6 and java 7:
> >>
> >> ---
> >>  T E S T S
> >> ---
> >> Running org.apache.karaf.shell.commands.WcTest
> >> Tests run: 5, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.077
> sec
> >> <<< FAILURE!
> >> Running org.apache.karaf.shell.commands.GrepTest
> >> 1
> >> 2
> >> 3
> >> 4
> >> 5
> >> 6
> >> 7
> >> 8
> >> 9
> >> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec
> >> Running org.apache.karaf.shell.commands.SortTest
> >> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007
> sec
> >>
> >> Results :
> >>
> >> Failed tests:
> >> testLargeStringWordCounts(org.apache.karaf.shell.commands.WcTest): The
> >> expected lineCount should be equal expected:<34> but was:<35>
> >>   testOneFileWordCounts(org.apache.karaf.shell.commands.WcTest): A
> single
> >> file report should not contain a total count row expected:<  3[4 487
> >>   3307]   WcActionTestLarge.t...> but was:<   3[5 487 3308]
> >> WcActionTestLarge.t...>
> >>   testThreeFilesWordCounts(org.apache.karaf.shell.commands.WcTest): A
> >> single file report should not contain a total expected:< 1[1 12
> >>  34
> >>  WcActionTestSmall.txt(..)
> >>
> >> Tests run: 9, Failures: 3, Errors: 0, Skipped: 0
> >>
> >> [INFO]
> >> 
> >> [INFO] Reactor Summary:
> >> [INFO]
> >> [INFO] Apache Karaf .. SUCCESS
> >> [3.489s]
> >> [INFO] Apache Karaf :: Util .. SUCCESS
> >> [3.572s]
> >> [INFO] Apache Karaf :: Main .. SUCCESS
> >> [40.519s]
> >> [INFO] Apache Karaf :: JAAS .. SUCCESS
> >> [0.166s]
> >> [INFO] Apache Karaf :: JAAS :: Boot .. SUCCESS
> >> [0.712s]
> >> [INFO] Apache Karaf :: JAAS :: Config  SUCCESS
> >> [0.865s]
> >> [INFO] Apache Karaf :: JAAS :: Modules ... SUCCESS
> >> [1.529s]
> >> [INFO] Apache Karaf :: Shell . SUCCESS
> >> [0.116s]
> >> [INFO] Apache Karaf :: Shell :: Console .. SUCCESS
> >> [2.808s]
> >> [INFO] Apache Karaf :: Shell :: OBR Commands . SUCCESS
> >> [0.775s]
> >> [INFO] Apache Karaf :: Features .. SUCCESS
> >> [0.063s]
> >> [INFO] Apache Karaf :: Features :: Core .. SUCCESS
> >> [7.067s]
> >> [INFO] Apache Karaf :: Features :: Command ... SUCCESS
> >> [0.604s]
> >> [INFO] Apache Karaf :: Management ...

Re: [VOTE] Release - Appassembler Maven Plugin version 1.4

[Andreas Pieber]

wrong mailing list? :-)

Kind regards,
Andreas


On Wed, Jul 3, 2013 at 10:55 PM, Dan Tran  wrote:

> Hello all,
>
>
> I'd like release version 1.4 of the appassembler-maven-plugin which
> contains
> new features and bug fixes
>
> The Application Assembler Plugin is a Maven plugin for generating scripts
> for starting java applications. All dependencies and the artifact of the
> project itself are placed in
> a generated Maven repository in a defined assemble directory. All artifacts
> (dependencies + the artifact from the project) are added to the classpath
> in the generated bin scripts.
>
> Staging Repositories:
> https://nexus.codehaus.org/content/repositories/orgcodehausmojo-095/
>
>
> Site
> http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/
>
> We solved 4 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11780&version=18633
>
> SCM Tag:
> http://svn.codehaus.org/mojo/**tags/appassembler-1.<
> http://svn.codehaus.org/mojo/tags/appassembler-1.3.1>
> 4
>
>  [ ] +1
>  [ ] +0
>  [ ] -1
>
> The vote is open for 72 hours and will succeed by lazy consensus.
>
> +1 from me
>
>
> Kind regards
>
>
> -D
>

Re: [VOTE] Release Apache Karaf version 2.3.2

[Andreas Pieber]

Am I the only one receiving the following result on downloading the
-src.tar.gz file and running mvn clean install? I get the same error using
java 6 and java 7:

---
 T E S T S
---
Running org.apache.karaf.shell.commands.WcTest
Tests run: 5, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.077 sec
<<< FAILURE!
Running org.apache.karaf.shell.commands.GrepTest
1
2
3
4
5
6
7
8
9
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec
Running org.apache.karaf.shell.commands.SortTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec

Results :

Failed tests:
testLargeStringWordCounts(org.apache.karaf.shell.commands.WcTest): The
expected lineCount should be equal expected:<34> but was:<35>
  testOneFileWordCounts(org.apache.karaf.shell.commands.WcTest): A single
file report should not contain a total count row expected:<  3[4 487
  3307]   WcActionTestLarge.t...> but was:<   3[5 487 3308]
WcActionTestLarge.t...>
  testThreeFilesWordCounts(org.apache.karaf.shell.commands.WcTest): A
single file report should not contain a total expected:< 1[1 12  34
 WcActionTestSmall.txt(..)

Tests run: 9, Failures: 3, Errors: 0, Skipped: 0

[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Apache Karaf .. SUCCESS [3.489s]
[INFO] Apache Karaf :: Util .. SUCCESS [3.572s]
[INFO] Apache Karaf :: Main .. SUCCESS [40.519s]
[INFO] Apache Karaf :: JAAS .. SUCCESS [0.166s]
[INFO] Apache Karaf :: JAAS :: Boot .. SUCCESS [0.712s]
[INFO] Apache Karaf :: JAAS :: Config  SUCCESS [0.865s]
[INFO] Apache Karaf :: JAAS :: Modules ... SUCCESS [1.529s]
[INFO] Apache Karaf :: Shell . SUCCESS [0.116s]
[INFO] Apache Karaf :: Shell :: Console .. SUCCESS [2.808s]
[INFO] Apache Karaf :: Shell :: OBR Commands . SUCCESS [0.775s]
[INFO] Apache Karaf :: Features .. SUCCESS [0.063s]
[INFO] Apache Karaf :: Features :: Core .. SUCCESS [7.067s]
[INFO] Apache Karaf :: Features :: Command ... SUCCESS [0.604s]
[INFO] Apache Karaf :: Management  SUCCESS [0.053s]
[INFO] Apache Karaf :: Management  SUCCESS [0.538s]
[INFO] Apache Karaf :: Features :: Management  SUCCESS [0.805s]
[INFO] Apache Karaf :: Features :: OBR Resolver .. SUCCESS [0.705s]
[INFO] Apache Karaf :: Admin . SUCCESS [0.045s]
[INFO] Apache Karaf :: Admin :: Core . SUCCESS [3.386s]
[INFO] Apache Karaf :: Admin :: Command .. SUCCESS [0.862s]
[INFO] Apache Karaf :: Admin :: Management ... SUCCESS [0.939s]
[INFO] Apache Karaf :: Deployer .. SUCCESS [0.067s]
[INFO] Apache Karaf :: Deployer :: Spring  SUCCESS [0.710s]
[INFO] Apache Karaf :: Deployer :: Blueprint . SUCCESS [0.709s]
[INFO] Apache Karaf :: Deployer :: Features .. SUCCESS [0.580s]
[INFO] Apache Karaf :: Deployer :: Karaf Archive (.kar) .. SUCCESS [0.813s]
[INFO] Apache Karaf :: Deployer :: Wrap Non OSGi Jar . SUCCESS [0.368s]
[INFO] Apache Karaf :: Shell :: Various Commands . FAILURE [0.766s]
[INFO] Apache Karaf :: Shell :: ConfigAdmin Commands . SKIPPED
[INFO] Apache Karaf :: Shell :: Log Commands . SKIPPED
[INFO] Apache Karaf :: Shell :: OSGi Commands  SKIPPED
[INFO] Apache Karaf :: Shell :: PackageAdmin Commands  SKIPPED
[INFO] Apache Karaf :: Shell :: SSH .. SKIPPED
[INFO] Apache Karaf :: Shell :: Service Wrapper .. SKIPPED
[INFO] Apache Karaf :: Shell :: Development Commands . SKIPPED
[INFO] Apache Karaf :: Shell :: SCR Commands . SKIPPED
[INFO] Apache Karaf :: Shell :: Web Commands . SKIPPED
[INFO] Apache Karaf :: JAAS :: Jasypt Encryption . SKIPPED
[INFO] Apache Karaf :: JAAS :: Command ... SKIPPED
[INFO] Apache Karaf :: Client  SKIPPED
[INFO] Apache Karaf :: Management :: MBeans .. SKIPPED
[INFO] Apache Karaf :: Management :: MBeans :: Bundles ... SKIPPED
[INFO] Apache Karaf :: Management :: MBeans :: Services .. SKIPPED
[INFO] Apache Karaf :: Management :: MBeans :: System  SKIPPED
[INFO] Apache Karaf :: Management :: MBeans :: Packages .. SKIPPED
[INFO] Apache Karaf :: Management :: MBeans :: Config  SKIPPED
[INFO] Apache Karaf :: Management :: MBeans :: Dev ... SKIPPED
[INFO] Apache Karaf :: Management :: MBeans :: Log ... SKIPPED
[INFO] Apache Karaf :: Management :: MBeans :: OBR ... SKIPPED
[INFO] Apache Karaf :: Management :: MB

Re: [VOTE] Switch from svn to git

[Andreas Pieber]

hey, there is no 0 option :-)

still +1 for the switch. Would make forking and experimenting (and
especially getting the changes back) so much easier...

Kind regards,
Andreas


On Tue, Jun 25, 2013 at 11:12 AM, Jean-Baptiste Onofré wrote:

> Hi all,
>
> to follow the discussion that we had some weeks ago, I start here a formal
> vote to migrate our scm from svn to git.
>
> Please vote to approve this switch:
>
> [ ] +1 Approve the switch (from svn to git)
> [ ] -1 Do not approve the switch (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Concern about new feature in blue-print core ( ie blueprint-core-1.1.1-SNAPSHOT is now blueprint-1.2-SNAPSHOT )

[Andreas Pieber]

Hey Dan,

Basically not a bad idea, but you should rather ask this question on the
aries list instead of the karaf one. Not all ppl having a word in this are
on both lists.

Kind regards,
Andreas


On Mon, Jun 17, 2013 at 1:38 AM, Dan Tran  wrote:

> Due to https://issues.apache.org/jira/browse/ARIES-1082
>
> which pumps blueprint-core from 1.1.1-SNAPSHOT to 1.2.0-SNAPSHOT
>
> This means karaf 2.3.2 will also pick it up eventually ( since
> 1.1.1-SNAPSHOT is no longer support )
>
> isn't better to release blueprint-core-1.1.1 first before adding new
> feature? to reduce regression in karaf 2.3.2?
>
> Thanks
>
> -D
>

Re: Debug pax-exam unit test

[Andreas Pieber]

is it possible that intellij has troubles with two debug processes at the
same time? try to run the tests regularly and attach the remote debugger.
Does this do the trick?

Kind regards,
Andreas


On Tue, Jun 11, 2013 at 12:00 PM, Charles Moulliard wrote:

> Even if I use this option, I cannot attach from intellij a remote process
> on the port 5005 when I start also in intellij the unit test in debug mode.
> So is there another magic thing to do ?
>
>
> On Tue, Jun 11, 2013 at 11:12 AM, Achim Nierbeck  >wrote:
>
> > Hi Charles,
> >
> > afairc something like this should be sufficient :)
> >
> > debugConfiguration("5005", true),
> >
> > regards, Achim
> >
> >
> > P.S. you might also take a look here:
> >
> >
> >
> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest-karaf/src/test/java/org/ops4j/pax/web/itest/karaf/KarafBaseTest.java#L89
> >
> >
> > 2013/6/11 Charles Moulliard 
> >
> > > Has added this option to the Unit test config
> > >
> > >
> > >
> >
>  vmOption("-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"),
> > > systemTimeout(0),
> > >
> > > but when the unit test is launched, I get this exception
> > >
> > > java.rmi.NotBoundException: b7cb86c5-596e-4265-be00-a3c8d38c28ff
> > > at sun.rmi.registry.RegistryImpl.lookup(RegistryImpl.java:114)
> > > at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
> > > at
> sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:390)
> > > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:248)
> > > at sun.rmi.transport.Transport$1.run(Transport.java:159)
> > > at java.security.AccessController.doPrivileged(Native Method)
> > > at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
> > > at
> > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
> > > at
> > >
> > >
> >
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
> > > at
> > >
> > >
> >
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
> > > at
> > >
> > >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> > > at
> > >
> > >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> > > at java.lang.Thread.run(Thread.java:680)
> > > at
> > >
> > >
> >
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
> > > at
> > >
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
> > > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:359)
> > > at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
> > > at
> > >
> > >
> >
> org.ops4j.pax.exam.rbc.client.intern.RemoteBundleContextClientImpl.getRemoteBundleContext(RemoteBundleContextClientImpl.java:263)
> > > at
> > >
> > >
> >
> org.ops4j.pax.exam.rbc.client.intern.RemoteBundleContextClientImpl.waitForState(RemoteBundleContextClientImpl.java:234)
> > > at
> > >
> > >
> >
> org.apache.karaf.tooling.exam.container.internal.KarafTestContainer.waitForState(KarafTestContainer.java:599)
> > > at
> > >
> > >
> >
> org.apache.karaf.tooling.exam.container.internal.KarafTestContainer.start(KarafTestContainer.java:183)
> > > at
> > >
> > >
> >
> org.ops4j.pax.exam.spi.reactors.AllConfinedStagedReactor.invoke(AllConfinedStagedReactor.java:67)
> > >
> > >
> > > On Tue, Jun 11, 2013 at 10:44 AM, Achim Nierbeck <
> > bcanh...@googlemail.com
> > > >wrote:
> > >
> > > > Hi Charles,
> > > >
> > > > as Karaf is started as a separate jvm process in the pax-exam-karaf
> > setup
> > > > you need to enable remote debugging.
> > > >
> > > > Regards, Achim
> > > >
> > > >
> > > > 2013/6/11 Charles Moulliard 
> > > >
> > > > > Hi,
> > > > >
> > > > > Is there something to be able do debug a unit test class using
> > > pax-exam2
> > > > ?
> > > > > I have added a break point in one the bundle that I would like to
> > debug
> > > > but
> > > > > when pax-exam + karaf container is started then the debugger never
> > > stops
> > > > > there ? Do we have to start a remote debugger ?
> > > > >
> > > > > Regards,
> > > > >
> > > > > --
> > > > > Charles Moulliard
> > > > > Apache Committer / Architect (RedHat)
> > > > > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Apache Karaf  Committer & PMC
> > > > OPS4J Pax Web 
> > Committer
> > > &
> > > > Project Lead
> > > > OPS4J Pax for Vaadin <
> > http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
> > > > Commiter & Project Lead
> > > > blog 
> > > >
> > >
> > >
> > >
> > > --
> > > Charles Moulliard
> > > Apache Committer / Architect @RedHat
> > > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
> > >
> >
> >
> >
> > --
> >
> > Apache Karaf  Committer & PMC
> > OPS4J Pax Web  Committer
> &
> 

Re: [VOTE] Apache Karaf Cellar 2.2.6 release

[Andreas Pieber]

OK, build works; notice file looks fine and samples are working.

+1

Kind regards,
Andreas


On Sun, May 19, 2013 at 8:38 AM, Jean-Baptiste Onofré wrote:

> Hi all,
>
> I submit Apache Karaf Cellar 2.2.6 release to your vote.
>
> Release Notes:
> http://svn.apache.org/repos/**asf/karaf/cellar/tags/cellar-**
> 2.2.6/RELEASE-NOTES
>
> Staging repository:
> https://repository.apache.org/**content/repositories/**orgapachekaraf-015/
>
> 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.
>
> Thanks
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf Cellar 2.3.0 release

[Andreas Pieber]

build works, basic exmaples work and the notice file also looks fine to me.

+1

Kind regards,
Andreas


On Tue, May 21, 2013 at 11:59 AM, Jean-Baptiste Onofré wrote:

> +1 (binding)
>
> Regards
> JB
>
>
> On 05/19/2013 08:02 AM, Jean-Baptiste Onofré wrote:
>
>> Hi all,
>>
>> I submit Apache Karaf Cellar 2.3.0 release to your vote.
>>
>> This is the first release of Cellar on the 2.3.x branch, fully
>> compatible with Karaf 2.3.x.
>>
>> Release Notes:
>> http://svn.apache.org/repos/**asf/karaf/cellar/tags/cellar-**
>> 2.3.0/RELEASE-NOTES
>>
>>
>> Staging repository:
>> https://repository.apache.org/**content/repositories/**
>> orgapachekaraf-014/
>>
>> 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.
>>
>> Thanks
>> Regards
>> JB
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Karaf 2.2.11

[Andreas Pieber]

I built the code, and run some of my projects on it. Looks pretty good!

+1

Kind regards,
Andreas


On Sat, Apr 27, 2013 at 6:19 AM, Jamie G.  wrote:

> The repository URL link should be to
> https://repository.apache.org/content/repositories/orgapachekaraf-146/
>
> -Jamie
>
> On Saturday, April 27, 2013, Jamie G. wrote:
>
> > Hi,
> >
> > We resolved 20 issues in this release (web page will be published post RC
> > promotion):
> >
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-
> > 2.2.11-release.page
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-146/<
> https://repository.apache.org/content/repositories/orgapachekaraf-046/>
> >
> > Release tags:
> > https://svn.apache.org/repos/asf/karaf/tags/karaf-2.2.11/
> >
> > 2.2.x Dependencies table:
> >
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-
> > 2.2.x.page
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote will be open for 72 hours.
> >
>

Re: [UPDATE] Karaf 2.2.x release branch status.

[Andreas Pieber]

+1 from my side too.

Kind regards,
Andreas


On Fri, Apr 26, 2013 at 1:52 PM, Jean-Baptiste Onofré wrote:

> +1 (just give me a hour this afternoon to check Jira).
>
> Regards
> JB
>
>
> On 04/26/2013 01:45 PM, Jamie G. wrote:
>
>> Hi All,
>>
>> We'd like to schedule a Karaf 2.2.x patch update release. There currently
>> are 19 resolved issues on the branch that we'd like to make available.
>> Remaining issues on 2.2.11 will be moved to 2.2.12.
>>
>> - The Karaf Team
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Help testing in Karaf 2.3.1

[Andreas Pieber]

One remark to the testing thing:

the problem is that most of the packaging thing is not under the control of
us but rather exam itself. Some of the most active exam maintainers are not
listening on this list --> ops4j might be a good resource too.

Kind regards,
Andreas


On Tue, Apr 16, 2013 at 9:18 PM, Jean-Baptiste Onofré wrote:

> Hi,
>
> could you try to use src/main/resources/OSGI-INF/**blueprint ?
> The path that you use doesn't look correct to me.
>
> Regards
> JB
>
>
> On 04/16/2013 06:30 PM, glsilverman wrote:
>
>> Well, if I put all my classes under src/test/java, and the blueprint file
>> under src/test/resource/OSGI_INF/**blueprint, the test works. But this
>> just
>> means that I can't test the code in src/main/java, which is what is
>> needed.
>>
>> Is there any way to accomplish this with the Karaf test container?
>>
>>
>>
>> --
>> View this message in context: http://karaf.922171.n3.nabble.**
>> com/Help-testing-in-Karaf-2-3-**1-tp4028453p4028460.html
>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Help testing in Karaf 2.3.1

[Andreas Pieber]

Hey,

a) is it possible that you've missed the relevant methods in your question?
b) I think the user list might have been the better place to ask, but
anyhow:
c) IIRC your entire test bundles is deployed into the container, so e.g. a
blueprint file from the correct location (
src/test/resources/OSGI_INF/blueprint should startup. But be aware of
racing conditions here since there's no mechanism waiting for your test
bundle to become a full and real bundle; ASAP RCP is working your tests are
run!

Kind regards,
Andreas


On Tue, Apr 16, 2013 at 2:40 AM, glsilverman  wrote:

> I'm testing with KarafDistributionConfiguration and TestProbeBuilder, but
> it
> seems the KarafTestContainer can only recognize existing bundles. For
> example, if I want to test a blueprint.xml file and the beans it generates
> from classes in src/main/java, how do I set up the configuration? In normal
> JUnit tests, I can put the xml file under src/test/resources and it will be
> picked up automatically, but not with the KarafTestContainer.
>
> I'm using a custom KarafTestSupport class. Here are the relevant methods:
>
>
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Help-testing-in-Karaf-2-3-1-tp4028453.html
> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>

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

[Andreas Pieber]

I also second Jamie on this one. +1 for the RC1 "tech preview" release.

Kind regards,
Andreas


On Thu, Mar 14, 2013 at 8:41 PM, Achim Nierbeck wrote:

> Hi,
>
> I'm with Jamie here, we're longing for this RC now for quite some time and
> actually I'm personally quite happy that we did get some immediate feedback
> of things that don't work :D
> Since it's a RC I also tend to get on with it.
> Let's focus on stabilizing now!
>
> regards, Achim
>
>
> 2013/3/14 Jamie G. 
>
> > The vote for Apache Karaf 3.0.0.RC1 is still active.
> >
> > At the current moment I'm torn between holding off this build
> > candidate for those immediate issues to be resolved, OR allowing the
> > RC to continue as it's a technology preview build not intended for
> > production. Personally I'm leaning towards continuing forward, marking
> > the above as known issues with this RC preview.
> >
> > Comments are encouraged.
> >
> > Cheers,
> > Jamie
> >
> > On Thu, Mar 14, 2013 at 8:12 AM, Jean-Baptiste Onofré 
> > wrote:
> > > Thanks for the update. I gonna take a look what is populated in system
> > repo
> > > (and if system repo is correctly used).
> > >
> > > Regards
> > > JB
> > >
> > >
> > > On 03/14/2013 11:34 AM, Charles Moulliard wrote:
> > >>
> > >> -1
> > >>
> > >> I don't know if this is a "internet" side effect but some basics
> > >> functionalities are not longer there when we start Karaf 3.0.0.RC1
> > without
> > >> internet connection (log:display subshell is not there, shortcuts have
> > >> disapeared, ...)
> > >>
> > >> https://gist.github.com/cmoulliard/b9f75b98bcb0a5e78d96
> > >>
> > >>
> > >> On Thu, Mar 14, 2013 at 11:05 AM, Łukasz Dywicki
> > >> wrote:
> > >>
> > >>> I have mixed feelings about putting my vote here.. but I have to do
> > this:
> > >>>
> > >>> -1  From me
> > >>>
> > >>> Minimal distro have broken instance script, basically it doesn't
> work.
> > >>>
> > >>> Best regards,
> > >>> Łukasz Dywicki
> > >>> --
> > >>> l...@code-house.org
> > >>> Twitter: ldywicki
> > >>> Blog: http://dywicki.pl
> > >>> Code-House - http://code-house.org
> > >>>
> > >>> Wiadomość napisana przez Christoph Gritschenberger <
> > >>> christoph.gritschenber...@gmail.com> w dniu 13 mar 2013, o godz.
> > 10:31:
> > >>>
> >  +1
> > 
> >  kind regards,
> >  christoph
> > 
> >  On 2013-03-12 04:26, Jamie G. wrote:
> > >
> > > Hi,
> > >
> > > We resolved 964 issues in this release (web page will be published
> > > post RC promotion):
> > >
> > >>>
> > >>>
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-3.0.0.RC1-release.page
> > >
> > >
> > > NOTE: This is a technology preview release candidate.
> > >
> > > Staging repository:
> > >
> > https://repository.apache.org/content/repositories/orgapachekaraf-019/
> > >
> > > Release tags:
> > > https://svn.apache.org/repos/asf/karaf/tags/karaf-3.0.0.RC1/
> > >
> > > 3.0.x Dependencies table:
> > >
> > >>>
> > >>>
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-3.0.x.page
> > >
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > This vote will be open for 72 hours.
> > >
> > 
> > 
> > >>>
> > >>>
> > >>
> > >>
> > >
> > > --
> > > Jean-Baptiste Onofré
> > > jbono...@apache.org
> > > http://blog.nanthrax.net
> > > Talend - http://www.talend.com
> >
>
>
>
> --
>
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> OPS4J Pax for Vaadin 
> Commiter & Project Lead
> blog 
>

Re: [Discuss] Karaf and Pax Exam 3.x

[Andreas Pieber]

As already stated @PaxExam-503 I'm fine with it too. Should also speed up
the Karaf build a bit again :-)

Kind regards,
Andreas


On Tue, Mar 12, 2013 at 11:27 AM, Achim Nierbeck wrote:

> Hey guys,
>
> I'm +1 for moving the pax-exam-karaf code base back closer to the pax-exam
> code base.
>
> regards, Achim
>
>
> 2013/3/12 Jean-Baptiste Onofré 
>
> > Hi Harald,
> >
> > Having Karaf container in Pax Exam directly looks better to me.
> >
> > It's easier to bootstrap different Karaf distribution than embedding new
> > Pax Exam version (with dependencies like Runner) in karaf-pax-exam.
> >
> > Regards
> > JB
> >
> >
> > On 03/11/2013 09:01 PM, Harald Wellmann wrote:
> >
> >> All@Karaf,
> >>
> >> at OPS4J, there is an ongoing discussion about Karaf support in Pax
> >> Exam, and in my role of Pax Exam Project Lead, I would like to bring up
> >> this subject to the Karaf team, hoping to set up a roadmap for making
> >> Karaf work with Pax Exam 3.x.
> >>
> >> Some background:
> >>
> >> - The Karaf Test Container, originally started by Andreas Pieber as a
> >> separate project, is now part of the Karaf code base.
> >>
> >> - On Karaf trunk, this container is based on Pax Exam 2.6.0.
> >>
> >> - The container and existing tests use some Pax Exam APIs that were
> >> deprecated in Pax Exam 2.4.0 and have been removed in Pax Exam 3.0.0,
> >> along with the deprecrated Pax Runner Test Container.
> >>
> >> - For this reason, people using Pax Exam to test Karaf-based
> >> applications can't simply upgrade to Pax Exam 3.0.0. (Unfortunately,
> >> nobody noticed or complained about that in the pre-3.0.0 release phase
> >> of Pax Exam.)
> >>
> >> - New Pax Exam options for provisioning Karaf features have been
> >> contributed by Christoph Läubrich to Pax Exam master (targeting 3.1.0 or
> >> later), currently not backed by any integration tests.
> >>
> >> Summing up the discussion [1] at OPS4J so far, we would like to achieve
> >> the following goals:
> >>
> >> - Tests based on the Karaf Exam Container (including but not limited to
> >> integration tests of the Karaf project) can be upgraded to Pax Exam 3.x
> >> with little or no code changes.
> >>
> >> - If any future refactorings either in Exam or in Karaf break the Karaf
> >> Exam container, there is a bunch of failing regression tests in at least
> >> one of the two projects.
> >>
> >> - The Karaf Exam Container and all Karaf-specific Exam options are
> >> centralized either in Apache Karaf or in OPS4J Pax Exam, to avoid
> >> tangled responsibilities between two communities.
> >>
> >> Those of you who've watched the progress of Pax Exam towards 3.0.0 will
> >> know that Pax Exam now offers a whole lot of test containers for
> >> third-party runtimes like GlassFish, JBoss AS, Tomcat etc., backed by a
> >> fairly extensive regression test matrix. So a Karaf test container would
> >> be just another member of the family.
> >>
> >> On the other hand, it might make sense to move the recent Karaf-related
> >> additions from Pax Exam to the Karaf project.
> >>
> >> To be sure, nobody at OPS4J wants to rip out a chunk of the Karaf
> >> codebase just to make Pax Exam bigger ;-)
> >>
> >> The basic question is, what is the best way to make things work smoothly
> >> for all Karaf-cum-Exam users - I'm offering my support, and I'm open to
> >> all options.
> >>
> >> So much for now - I'm looking forward to hearing your opinions.
> >>
> >> [1] http://team.ops4j.org/browse/**PAXEXAM-503<
> http://team.ops4j.org/browse/PAXEXAM-503>
> >>
> >> Best regards,
> >> Harald
> >>
> >>
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
> Commiter & Project Lead
> blog <http://notizblog.nierbeck.de/>
>

Re: [Discuss] Let Hudson comment on jira issues

[Andreas Pieber]

fine with me too.

Kind regards,
Andreas


On Mon, Mar 11, 2013 at 3:39 PM, Filippo Balicchia wrote:

> I'm agree too,
> as already Łukasz mentioned it can improve the quality code.
>
> Regards
>
> --Filippo
>
> 2013/3/11 Achim Nierbeck 
>
> > fine with me.
> >
> > regards, Achim
> >
> >
> > 2013/3/11 Łukasz Dywicki 
> >
> > > That's something really good from quality point of view. For
> webconsole I
> > > had local gerrit installation with hudson verifying every commit before
> > > moving to trunk.
> > >
> > > Wiadomość napisana przez Jean-Baptiste Onofré  w dniu
> > 11
> > > mar 2013, o godz. 10:25:
> > >
> > > > Hi Christian,
> > > >
> > > > Agree with you.
> > > >
> > > > If the others are OK, I will setup our Hudson build with this
> feature.
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On 03/11/2013 10:21 AM, Christian Schneider wrote:
> > > >> Hi all,
> > > >>
> > > >> I have seen a nice Hudson feature at the Syncope project that might
> be
> > > >> interesting for us.
> > > >> Since jira is not connected to svn anymore we have the problem that
> we
> > > >> can not directly see the code changes related to a jira issue
> anymore.
> > > >> So often people add the commit log from svnsearch or similar to show
> > > >> what they changed. The problem is that it is easy to forget this.
> > > >>
> > > >> In Syncope Hudson comments on each relevant jira entry. So jira
> shows
> > > >> the build status and the changes in svn. Here is an example:
> > > >> https://issues.apache.org/jira/browse/SYNCOPE-245
> > > >>
> > > >> I think it would make sense to also add this feature to the karaf
> > > builds.
> > > >>
> > > >> Christian
> > > >>
> > > >
> > > > --
> > > > Jean-Baptiste Onofré
> > > > jbono...@apache.org
> > > > http://blog.nanthrax.net
> > > > Talend - http://www.talend.com
> > >
> > >
> >
> >
> > --
> >
> > Apache Karaf  Committer & PMC
> > OPS4J Pax Web  Committer
> &
> > Project Lead
> > OPS4J Pax for Vaadin 
> > Commiter & Project Lead
> > blog 
> >
>

Re: Problems with karaf documentation

[Andreas Pieber]

I think we should try to always offer both version. The spitted one is
better for linking, googling, ... but the single page version is great for
me looking for something specific opening the entire page and doing strg+f
on it :)


On Mon, Mar 4, 2013 at 8:15 AM, Christian Schneider  wrote:

> Am 04.03.2013 05:06, schrieb Andreas Pieber:
>
>
>>  - It should be possible to link directly to a certain feature. So the
>>> documentation should be available in separate pages per feature
>>>
>>>  I'm not quite sure how this should look like. I think it's a mixture
>> between features and concepts right now which doesn't sound too bad to me.
>> What do you have in mind?
>>
> I am not thinking of anything fancy. I simply thought about having the
> documentation split into separate pages and not only as a single file.
> This should already be the case I think. I just wanted to emphasize that
> it is necessary to have it.
>
>
> Christian
>
> --
>  Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
>

Re: Problems with karaf documentation

[Andreas Pieber]

Hey,


On Sun, Mar 3, 2013 at 12:00 PM, Christian Schneider <
ch...@die-schneider.net> wrote:
>
> I would like to offer the web documentation in a layout with the following
> goals:
> - Links should be as stable as possible, so google as well as other
> websites can link to us
> - Google should link to a current and useful page when given a search term
> related to a karaf feature like "karaf security" or similar
>

I definitely second you on those two points.


> - It should be possible to link directly to a certain feature. So the
> documentation should be available in separate pages per feature
>

I'm not quite sure how this should look like. I think it's a mixture
between features and concepts right now which doesn't sound too bad to me.
What do you have in mind?

Kind regards,
Andreas

So what do you think?
>
> Christian
>
> --
>  Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
>

Re: [UPDATE] Karaf website with scm-publish

[Andreas Pieber]

Sounds like not all of us have permissions to push the site?

Kind regards,
Andreas


On Mon, Mar 4, 2013 at 2:59 AM, Jamie G.  wrote:

> Hi,
>
> I've tried the goal:
> mvn clean install scm-publish:publish-scm
>
> However I keep getting:
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Could not copy content to scm checkout
>
> Embedded error: Destination
>
> '/x1/asf/site_trunk/target/scmpublish-checkout/css/scalate/.svn/text-base/console.css.svn-base'
> exists but is read-only
>
> Is there something I'm missing in setting up to update the website?
>
> /x1/asf/site_trunk is my check out of
> https://svn.apache.org/repos/asf/karaf/site/trunk.
>
> Cheers,
> Jamie
>
> On Fri, Feb 22, 2013 at 6:21 AM, Jean-Baptiste Onofré 
> wrote:
> > Hi all,
> >
> > FYI, INFRA has setup our resources (both for dist and website) to use
> > scm-pubsub.
> >
> > I've published a new version of the Karaf website this morning.
> >
> > From now, please use the following goal to update the Karaf website:
> >
> > mvn clean install scm-publish:publish-scm
> >
> > I'm going to review the Karaf subprojects "sub-site" management (Cellar,
> > WebConsole, EIK, Cave) and the different manual deployment.
> >
> > Regards
> > JB
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Karaf version 2.3.1

[Andreas Pieber]

+1 for recutting
On 28 Feb 2013 21:15, "Achim Nierbeck"  wrote:

> +1 to get the release train rolling again :-)
>
> Regards, Achim
>
> sent from mobile device
> Am 28.02.2013 21:12 schrieb "Jamie G." :
>
> > I'd like to re-cut the 2.3.1 RC then seeing as we have resolved the
> > recent minimal distribution startup error.
> >
> > Cheers,
> > Jamie
> >
> > On Thu, Feb 28, 2013 at 2:18 PM, Daniel Kulp  wrote:
> > >
> > > On Feb 28, 2013, at 9:25 AM, Dan Tran  wrote:
> > >
> > >> now that the Vote has been canceled, I have a second thought on those
> > >> 2 bugs i found.  Can Aries team address this quickly? Since those are
> > >> regression bugs.
> > >>
> > >> Sorry, cant help to ask.
> > >
> > > Nothing in Aries goes quickly…. why do you think 2.3.1 has taken so
> > long.  :-(
> > >
> > > I'd personally suggest getting 2.3.1 out now and when Aries does get
> > around to getting things fixed, get a 2.3.2.  Might be a couple weeks,
> > maybe a month, whatever.  I'd like to see more releases more often rather
> > than keep waiting for Aries.
> > >
> > > That's my $0.02 worth.
> > >
> > > Dan
> > >
> > >
> > >>
> > >> Thanks
> > >>
> > >> -D
> > >>
> > >> On Thu, Feb 28, 2013 at 3:32 AM, Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > wrote:
> > >>> Agree,
> > >>>
> > >>> The distro should start out of the box.
> > >>>
> > >>> I revert my vote to -1.
> > >>>
> > >>> Regards
> > >>> JB
> > >>>
> > >>>
> > >>> On 02/28/2013 11:42 AM, Jamie G. wrote:
> > 
> >  I tend to agree with that reasoning - our distros need to at least
> >  startup out of the box.
> > 
> >  I'm going to post a -1 on this release due to the minimal distro not
> >  starting. Once this issue is resolved another RC will be posted for
> >  review and vote.
> > 
> >  Cheers,
> >  Jamie
> > 
> >  On Thu, Feb 28, 2013 at 6:42 AM, Ioannis Canellos <
> ioca...@gmail.com>
> >  wrote:
> > >
> > > The minimal distribution fails to start because its missing
> > > the org.apache.karaf.jaas.authz-2.3.1.jar from the system repo.
> > > Having one of two flavor not being able to start, seems like a show
> > > stopper, but I am not sure. What do you thing?
> > >
> > > --
> > > *Ioannis Canellos*
> > > *
> > >
> > > **
> > > Blog: http://iocanel.blogspot.com
> > > **
> > > Twitter: iocanel
> > > *
> > >>>
> > >>>
> > >>> --
> > >>> Jean-Baptiste Onofré
> > >>> jbono...@apache.org
> > >>> http://blog.nanthrax.net
> > >>> Talend - http://www.talend.com
> > >
> > > --
> > > Daniel Kulp
> > > dk...@apache.org - http://dankulp.com/blog
> > > Talend Community Coder - http://coders.talend.com
> > >
> >
>

Re: Board report for March, 2013

[Andreas Pieber]

+1 kind regards, Andreas
On 28 Feb 2013 19:17, "Jean-Baptiste Onofré"  wrote:

> Hi all,
>
> as I will be in vacation tonight for one week (with probably a "limited"
> Internet connection, and my wife will watch me ;)), I have anticipated the
> Karaf board report, to give you the maximum of time to review.
>
> So, I created the board report for March, 2013 here:
> https://cwiki.apache.org/**confluence/display/KARAF/**Board+Reports
>
> Please review it and update it if I forgot something.
>
> I plan to submit the report on March, 9 (as soon as I'm back from
> vacation).
>
> Thanks !
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: New Karaf features on github

[Andreas Pieber]

we did, but iirc we neither come to a final conclusion nor where the future
steps fixed.

Kind regards,
Andreas


On Wed, Feb 27, 2013 at 8:20 AM, Jean-Baptiste Onofré wrote:

> Hi,
>
> we already discuss to "isolate" Spring, Enterprises, etc features, in
> order to release "independently" from the Karaf "distribution".
>
> Let me find the discussion thread.
>
> Regards
> JB
>
>
> On 02/27/2013 08:17 AM, Krzysztof Sobkowiak wrote:
>
>> Hi
>>
>> Perhaps we should have a separate subproject/repository for the enterprise
>> features. The wouldn't block Karaf releases but could be updated after a
>> new Karaf version is released (e.g. if the enterprise features need some
>> dependencies included in standard Karaf features) or after a new
>> enterprise
>> library is released. Another solution would be such a repository as a SMX
>> subproject. There is already repository for osgifying external bundles
>> (Could be there committed any osgified libraries or should they be
>> compatible with Apache license?). There could be something similar for
>> enterprise features.
>>
>> In my opinion the current Karaf enterprise features repository should
>> still
>> be part of Karaf as it is a integral part of Karaf and many other features
>> depend on them. I mean we could have a separate subproject for any other
>> 3rd party enterprise libraries which other users could use in their
>> projects.
>>
>> I don't know whether all  eterprise libraries fulfill  the rules to be
>> dependencies of Apache project. If no, It could be only a Github project.
>>
>> Regards
>> Krzysztof
>>
>> On 27 February 2013 06:26, Andreas Pieber  wrote:
>>
>>
>>>
>>> In general I still get a stall feeling in my stomage seeing all those
>>> enterprise features. Keeping them directly at Karaf sounds like a bad
>>> idea.
>>> We have already problems with the other enterprise features and their
>>> versions (e.g. Spring). Maybe it's slowly getting time to decide how we
>>> want to manage such external feature bundles? I add the dev list for CC
>>> to
>>> get this question explicitly to the dev community.
>>>
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Idea: Allow users to patch feature files

[Andreas Pieber]

I have to admit one thing: all of those ideas (as summed up nicely by
Ioannis) sound VERY tempting. They would solve some of the problems we're
facing in production and would definitely help many people.

BUT I'm definitely with Guillaume. This feels like we're opening the gates
to Hell introducing a LOT of possible problems which are anything than
intuitive!

Wouldn't it be easier providing the tooling providing the correct
features.xml files manually? For example I could think of something like
the mapping features but only for "compile time use" instead of runtime
use. E.g. extending our Karaf Plugin to supporting the url mapping. This
could produce the patched feature files with their own versions in quite a
minimalistic style. Maybe we could even pack this into a simple command
line tool also allowing end users to do this step before starting Karaf.
Finally it's all about fixing problems devs introduce because they weren't
thinking (or lacking the knowledge) while creating the feature files.

Does this sound completely off the road? Would this make sense?

Kind regards,
Andreas


On Tue, Feb 26, 2013 at 10:24 PM, Guillaume Nodet  wrote:

> While I don't have any problem at introducing a kind of mapping, I do fear
> the abuses it can lead to.
> I don't really want to add a feature to be able to fix broken things.
>  Valid use cases, sure, broken features descriptors, no.
> So what I mean is that if we allow any kind of global mapping, we can
> easily end up screwing the features even more, i.e. if I override the
> spring stuff as mentionned below, i won't be able to deploy any feature
> that does need the 2.x release of spring (because of version ranges on the
> packages such as [2.5,3) for example).
>
>
> On Tue, Feb 26, 2013 at 10:05 PM, Ioannis Canellos  >wrote:
>
> > Some of the views expressed so far:
> >
> > i) Allow defining an alternate location for a feature repository.
> > ii) Allow overriding a feature repository or bundle url using a mapping.
> > iii) Using version feature version ranges to resolve the right version to
> > use.
> >
> > Some thoughts about each idea.
> >
> > i) I'd love to be able to do that, even though in most cases modifying
> the
> > feature repo in the system directory does work for me.
> > We could take this one step further an be able to modify the feature repo
> > itself, using the editor we have in trunk (mostly as a dev tool).
> >
> > ii) I like this idea too. This would solve the recent problem we had with
> > spring versions. We could just let the user define a mapping like
> > mvn:org.springframework/*/[3,4] = mvn:org.springframework/*/3.1.2.RELEASE
> > and it would be awesome.
> >
> > iii) This would definetely solve a lot of problems, without direct user
> > interaction. I think that we should maybe start with this point but maybe
> > also grant the user the power to do things like i) and ii).
> >
> > I hope I didn't miss anything.
> >
> > --
> > *Ioannis Canellos*
> > *
> >
> > **
> > Blog: http://iocanel.blogspot.com
> > **
> > Twitter: iocanel
> > *
> >
>
>
>
> --
> 
> Guillaume Nodet
> 
> Red Hat, Open Source Integration
>
> Email: gno...@redhat.com
> Web: http://fusesource.com
> Blog: http://gnodet.blogspot.com/
>

Re: New Karaf features on github

[Andreas Pieber]

On Tue, Feb 26, 2013 at 12:55 PM, Tcharl  wrote:

> Hi, where to push, may I clone Karaf?
>

Exactly. There's a github mirror at https://github.com/apache/karaf. You
can clone this one and provide pull requests as you're used to. We'll get
notified about them on the dev list.

Some additional comments:

a) Why do you have some MANIFEST.MF files in the resource folders of your
features
b) Some parts of the features might be interesting to include into Karaf
features (e.g. the Spring extensions)

In general I still get a stall feeling in my stomage seeing all those
enterprise features. Keeping them directly at Karaf sounds like a bad idea.
We have already problems with the other enterprise features and their
versions (e.g. Spring). Maybe it's slowly getting time to decide how we
want to manage such external feature bundles? I add the dev list for CC to
get this question explicitly to the dev community.

Kind regards,
Andreas


I also made a little helloworld (not sure it is working but the spirit is
> here) :
>
> https://github.com/Tcharl/Karaf-and-Virgo-osgiliath-reference-helloworld/tree/master/helloworld
>
>
> See you soon!
>
>
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/New-Karaf-features-on-github-tp4027864p4027884.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>

Re: pax url 1.5.2 release

[Andreas Pieber]

no objections from my point of view; do you have all required permissions?

Kind regards,
Andreas


On Fri, Feb 15, 2013 at 7:03 PM, Andrei Pozolotin <
andrei.pozolo...@gmail.com> wrote:

> *Hello*
>
> if there are not objections, I will cut pax url 1.5.2 release today
> http://team.ops4j.org/browse/PAXURL-213
> https://issues.apache.org/jira/browse/KARAF-2193
>
> Thank you,
>
> Andrei
>
>

Re: blueprint annotations?

[Andreas Pieber]

The last time I've given this a shot (~6 month ago) the annotations were by
far not sufficient to get everything required done; have you checked? Is it
possible in the meantime?

Kind regards,
Andreas


On Fri, Feb 15, 2013 at 4:34 PM, Andrei Pozolotin <
andrei.pozolo...@gmail.com> wrote:

> *Hello,*
>
> I am curious if there are plans to migrate karaf commands to
> blueprint annotations
> http://aries.apache.org/modules/blueprintannotation.html
> and to drop OSGI-INF/blueprint/*.xml
>
> ?
>
> Thank you,
>
> Andrei
>
>

Re: karaf-maven-plugin ci-build-profile failures

[Andreas Pieber]

It seams so;

Do you have a fix for this? (@Brian any idea?)

Jamie, JB, or someone else with permissions to our Jenkins instance; we
might want to include the profile for our integration runs? :-)

Kind regards,
Andreas


On Sat, Feb 9, 2013 at 4:16 PM, Andrei Pozolotin  wrote:

> I presume this profile is not really running now on ci?
>
> cd karaf/tooling/karaf-maven-plugin
> mvn install -P ci-build-profile
>
> [INFO] --- maven-invoker-plugin:1.6:run (integration-test) @
> karaf-maven-plugin ---
> [INFO] Building: test-recursive/pom.xml
> [INFO] run script
>
> /work/git/barchart-apache-karaf/tooling/karaf-maven-plugin/target/it/test-recursive/verify.bsh
> [INFO] ..SUCCESS (4.6 s)
> [INFO] Building: test-check-dependencies-failure/pom.xml
> [INFO] run script
>
> /work/git/barchart-apache-karaf/tooling/karaf-maven-plugin/target/it/test-check-dependencies-failure/verify.bsh
> [INFO] ..FAILED (5.1 s)
> [INFO]   The post-build script returned false.
> [INFO] Building: test-basic-generation/pom.xml
> [INFO] run script
>
> /work/git/barchart-apache-karaf/tooling/karaf-maven-plugin/target/it/test-basic-generation/verify.bsh
> [INFO] ..FAILED (4.3 s)
> [INFO]   The post-build script returned false.
> [INFO] Building: test-check-dependencies/pom.xml
> [INFO] run script
>
> /work/git/barchart-apache-karaf/tooling/karaf-maven-plugin/target/it/test-check-dependencies/verify.bsh
> [INFO] ..FAILED (5.5 s)
> [INFO]   The post-build script returned false.
> [INFO] Building: test-aggregate-features/pom.xml
> [INFO] run script
>
> /work/git/barchart-apache-karaf/tooling/karaf-maven-plugin/target/it/test-aggregate-features/verify.bsh
> [INFO] ..FAILED (4.7 s)
> [INFO]   The post-build script returned false.
> [INFO] Building: test-type-classifier/pom.xml
> [INFO] run script
>
> /work/git/barchart-apache-karaf/tooling/karaf-maven-plugin/target/it/test-type-classifier/verify.bsh
> [INFO] ..FAILED (3.7 s)
> [INFO]   The post-build script returned false.
> [INFO] Building: test-input-file/pom.xml
> [INFO] run script
>
> /work/git/barchart-apache-karaf/tooling/karaf-maven-plugin/target/it/test-input-file/verify.bsh
> [INFO] ..FAILED (3.7 s)
> [INFO]   The post-build script returned false.
> [INFO] -
> [INFO] Build Summary:
> [INFO]   Passed: 1, Failed: 6, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] *  test-check-dependencies-failure/pom.xml
> [ERROR] *  test-basic-generation/pom.xml
> [ERROR] *  test-check-dependencies/pom.xml
> [ERROR] *  test-aggregate-features/pom.xml
> [ERROR] *  test-type-classifier/pom.xml
> [ERROR] *  test-input-file/pom.xml
> [INFO] -
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 38.654s
> [INFO] Finished at: Sat Feb 09 09:07:14 CST 2013
> [INFO] Final Memory: 25M/373M
> [INFO]
> 
>
>

Re: [UPDATE] Karaf branches and features in Karaf 2.3.x

[Andreas Pieber]

nothing to add; +1

Kind regards,
Andreas


On Thu, Feb 7, 2013 at 4:33 PM,  wrote:

> Hi all,
>
> following a discussion started a couple of weeks ago, just an update about
> Karaf branches and releases:
>
> - karaf-2.x: I'm going to create this branch asap (let say tonight or
> tomorrow). This branch will be the codebase for Karaf 2.4, Karaf 2.5, etc.
> This branch will be created starting from the current karaf-2.3.x one.
> - karaf-2.3.x: this branch stays as it is and it becomes *MAINTENANCE/GA*
> branch. It means no new features, no new commands, only bug fixes. I will
> remove new features from this branch (for instance shell:date command, etc)
> to respect this *MAINTENANCE/GA* "mode". I will look for new features or
> improvements using Jira.
> - karaf-2.2.x: as soon as Karaf 2.4.0 will be released (on the karaf-2.x
> branch), this branch will go in EOL mode (and an announcement will be send
> to the users).
>
> In terms of releases planning:
> - Karaf 2.3.1 is waiting for Aries JMX 1.1.1 and Pax Web 1.1.12 releases.
> I will tackle the Pax Web release with Achim, and ping Dan about the Aries
> release.
> - Karaf 3.0.0.RC1 is waiting for Aries JMX 1.1.1 release. It would be cool
> to fix a couple of issues around sub-shell here, but it's not blocker for
> RC1 IMHO.
> - we can plan to cut off Karaf 2.4 in 6 weeks after 2.3.1.
> - I propose a Karaf 2.2.11 with latest bug fixes before the switch to EOL
> mode.
>
> WDYT ?
>
> Thanks,
> Regards
> JB
>
>

Re: Karaf 2.3.x and Karaf 3.0.x support ASM in Version 4.1, why?

[Andreas Pieber]

cheater :P but as long as it works... well better than nothing.

kind regards,
Andreas

On Tue, Jan 22, 2013 at 8:50 AM, Achim Nierbeck  wrote:
> oops 
>
> though some good news for the ASM stuff, I was able to create a workaround
> for Pax-Web. A fragment Bundle attached to xbean binds the version to [3.1,
> 4.0). Now Pax-Web 3.0.0.M2 will be usable with Karaf 3.0 again :-)
>
> regards, Achim
>
>
> 2013/1/22 Andreas Pieber 
>
>> Outsch, I just set the release date of Karaf 3 in my private Calendar
>> to 2014... :-)
>>
>> Kind regards,
>> Andreas
>>
>> On Mon, Jan 21, 2013 at 6:11 PM, Achim Nierbeck 
>> wrote:
>> > looks like this issue at xbean is going to block aries and pax-web
>> > https://issues.apache.org/jira/browse/XBEAN-230
>> >
>> > regards, Achim
>> >
>> >
>> > 2013/1/21 Achim Nierbeck 
>> >
>> >> hmm, interesting.
>> >> Aries Annotations won't work with this either ...
>> >>
>> >> regards, Achim
>> >>
>> >>
>> >> 2013/1/21 j...@nanthrax.net 
>> >>
>> >> It was a requirement for Aries Proxy update.
>> >>>
>> >>> Regards
>> >>> JB
>> >>>
>> >>> --
>> >>> Jean-Baptiste Onofré
>> >>> jbono...@apache.org
>> >>> http://blog.nanthrax.net
>> >>> Talend - http://wwx.talend.com
>> >>>
>> >>> - Reply message -
>> >>> From: "Achim Nierbeck" 
>> >>> To: 
>> >>> Subject: Karaf 2.3.x and Karaf 3.0.x support ASM in Version 4.1, why?
>> >>> Date: Mon, Jan 21, 2013 6:12 am
>> >>>
>> >>>
>> >>> Hi guys,
>> >>>
>> >>> anyone know why we moved to version 4.1 of ASM in Karaf 2.3 and 3.0?
>> >>> Cause this is an issue for Pax-Web right now (at least if working with
>> >>> xbean-finder) and surely will also be an issue for Aries Annotation
>> >>> support.
>> >>> To my knowledge the Aries Annotation scanner also uses xbean-finder in
>> >>> version 3.x which needs ASM 3.1 and not 4.x.
>> >>> If needed we gonna need to raise an issue at the xbean project to
>> tighten
>> >>> the range for ASM to [3.1, 4.0)
>> >>>
>> >>>
>> >>> regards, Achim
>> >>>
>> >>> --
>> >>>
>> >>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> >>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>> Committer &
>> >>> Project Lead
>> >>> OPS4J Pax for Vaadin <
>> http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
>> >>> Commiter & Project Lead
>> >>> blog <http://notizblog.nierbeck.de/>
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>> Committer &
>> >> Project Lead
>> >> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home
>> >
>> >> Commiter & Project Lead
>> >> blog <http://notizblog.nierbeck.de/>
>> >>
>> >
>> >
>> >
>> > --
>> >
>> > Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>> &
>> > Project Lead
>> > OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
>> > Commiter & Project Lead
>> > blog <http://notizblog.nierbeck.de/>
>>
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
> Commiter & Project Lead
> blog <http://notizblog.nierbeck.de/>

Re: Karaf 2.3.x and Karaf 3.0.x support ASM in Version 4.1, why?

[Andreas Pieber]

Outsch, I just set the release date of Karaf 3 in my private Calendar
to 2014... :-)

Kind regards,
Andreas

On Mon, Jan 21, 2013 at 6:11 PM, Achim Nierbeck  wrote:
> looks like this issue at xbean is going to block aries and pax-web
> https://issues.apache.org/jira/browse/XBEAN-230
>
> regards, Achim
>
>
> 2013/1/21 Achim Nierbeck 
>
>> hmm, interesting.
>> Aries Annotations won't work with this either ...
>>
>> regards, Achim
>>
>>
>> 2013/1/21 j...@nanthrax.net 
>>
>> It was a requirement for Aries Proxy update.
>>>
>>> Regards
>>> JB
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://wwx.talend.com
>>>
>>> - Reply message -
>>> From: "Achim Nierbeck" 
>>> To: 
>>> Subject: Karaf 2.3.x and Karaf 3.0.x support ASM in Version 4.1, why?
>>> Date: Mon, Jan 21, 2013 6:12 am
>>>
>>>
>>> Hi guys,
>>>
>>> anyone know why we moved to version 4.1 of ASM in Karaf 2.3 and 3.0?
>>> Cause this is an issue for Pax-Web right now (at least if working with
>>> xbean-finder) and surely will also be an issue for Aries Annotation
>>> support.
>>> To my knowledge the Aries Annotation scanner also uses xbean-finder in
>>> version 3.x which needs ASM 3.1 and not 4.x.
>>> If needed we gonna need to raise an issue at the xbean project to tighten
>>> the range for ASM to [3.1, 4.0)
>>>
>>>
>>> regards, Achim
>>>
>>> --
>>>
>>> Apache Karaf  Committer & PMC
>>> OPS4J Pax Web  Committer &
>>> Project Lead
>>> OPS4J Pax for Vaadin 
>>> Commiter & Project Lead
>>> blog 
>>>
>>
>>
>>
>> --
>>
>> Apache Karaf  Committer & PMC
>> OPS4J Pax Web  Committer &
>> Project Lead
>> OPS4J Pax for Vaadin 
>> Commiter & Project Lead
>> blog 
>>
>
>
>
> --
>
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> OPS4J Pax for Vaadin 
> Commiter & Project Lead
> blog 

Re: svn commit: r1436343 - in /karaf/branches/karaf-2.2.x/deployer: blueprint/src/main/java/org/apache/karaf/deployer/blueprint/ features/src/main/java/org/apache/karaf/deployer/features/ spring/src/m

[Andreas Pieber]

just my 0.02€ but maybe we don't want to duplicate the same code thrice? :-)

Kind regards,
Andreas

On Mon, Jan 21, 2013 at 2:41 PM,   wrote:
> Author: gnodet
> Date: Mon Jan 21 13:41:10 2013
> New Revision: 1436343
>
> URL: http://svn.apache.org/viewvc?rev=1436343&view=rev
> Log:
> [KARAF-2134] Deployers do not support mvn urls well
>
> Modified:
> 
> karaf/branches/karaf-2.2.x/deployer/blueprint/src/main/java/org/apache/karaf/deployer/blueprint/BlueprintTransformer.java
> 
> karaf/branches/karaf-2.2.x/deployer/features/src/main/java/org/apache/karaf/deployer/features/FeatureTransformer.java
> 
> karaf/branches/karaf-2.2.x/deployer/spring/src/main/java/org/apache/karaf/deployer/spring/SpringTransformer.java
>
> Modified: 
> karaf/branches/karaf-2.2.x/deployer/blueprint/src/main/java/org/apache/karaf/deployer/blueprint/BlueprintTransformer.java
> URL: 
> http://svn.apache.org/viewvc/karaf/branches/karaf-2.2.x/deployer/blueprint/src/main/java/org/apache/karaf/deployer/blueprint/BlueprintTransformer.java?rev=1436343&r1=1436342&r2=1436343&view=diff
> ==
> --- 
> karaf/branches/karaf-2.2.x/deployer/blueprint/src/main/java/org/apache/karaf/deployer/blueprint/BlueprintTransformer.java
>  (original)
> +++ 
> karaf/branches/karaf-2.2.x/deployer/blueprint/src/main/java/org/apache/karaf/deployer/blueprint/BlueprintTransformer.java
>  Mon Jan 21 13:41:10 2013
> @@ -64,7 +64,7 @@ public class BlueprintTransformer {
>  // Build dom document
>  Document doc = parse(url);
>  // Heuristicly retrieve name and version
> -String name = url.getPath();
> +String name = getPath(url);
>  int idx = name.lastIndexOf('/');
>  if (idx >= 0) {
>  name = name.substring(idx + 1);
> @@ -185,6 +185,28 @@ public class BlueprintTransformer {
>  return db.parse(url.toString());
>  }
>
> +protected static String getPath(URL url) {
> +if (url.getProtocol().equals("mvn")) {
> +String[] parts = url.toExternalForm().substring(4).split("/");
> +String groupId;
> +String artifactId;
> +String version;
> +String type;
> +String qualifier;
> +if (parts.length < 3 || parts.length > 5) {
> +return url.getPath();
> +}
> +groupId = parts[0];
> +artifactId = parts[1];
> +version = parts[2];
> +type = (parts.length >= 4) ?  "." + parts[3] : ".jar";
> +qualifier = (parts.length >= 5) ? "-" + parts[4] :  "";
> +return groupId.replace('.', '/') + "/" + artifactId + "/"
> ++ version + "/" + artifactId + "-" + version + qualifier 
> + type;
> +}
> +return url.getPath();
> +}
> +
>  protected static void copyInputStream(InputStream in, OutputStream out) 
> throws Exception {
>  byte[] buffer = new byte[4096];
>  int len = in.read(buffer);
>
> Modified: 
> karaf/branches/karaf-2.2.x/deployer/features/src/main/java/org/apache/karaf/deployer/features/FeatureTransformer.java
> URL: 
> http://svn.apache.org/viewvc/karaf/branches/karaf-2.2.x/deployer/features/src/main/java/org/apache/karaf/deployer/features/FeatureTransformer.java?rev=1436343&r1=1436342&r2=1436343&view=diff
> ==
> --- 
> karaf/branches/karaf-2.2.x/deployer/features/src/main/java/org/apache/karaf/deployer/features/FeatureTransformer.java
>  (original)
> +++ 
> karaf/branches/karaf-2.2.x/deployer/features/src/main/java/org/apache/karaf/deployer/features/FeatureTransformer.java
>  Mon Jan 21 13:41:10 2013
> @@ -36,7 +36,7 @@ public class FeatureTransformer {
>
>  public static void transform(URL url, OutputStream os) throws Exception {
>  // Heuristicly retrieve name and version
> -String name = url.getPath();
> +String name = getPath(url);
>  int idx = name.lastIndexOf('/');
>  if (idx >= 0) {
>  name = name.substring(idx + 1);
> @@ -72,6 +72,28 @@ public class FeatureTransformer {
>  os.close();
>  }
>
> +private static String getPath(URL url) {
> +if (url.getProtocol().equals("mvn")) {
> +String[] parts = url.toExternalForm().substring(4).split("/");
> +String groupId;
> +String artifactId;
> +String version;
> +String type;
> +String qualifier;
> +if (parts.length < 3 || parts.length > 5) {
> +return url.getPath();
> +}
> +groupId = parts[0];
> +artifactId = parts[1];
> +version = parts[2];
> +type = (parts.length >= 4) ?  "." + parts[3] : ".jar";
> +qualifier = (parts.length >= 5) ? "-" + parts[4] :  "";
> +return groupId.replace('.', '/') + "/" + 

Re: [PROPOSAL] Karaf release policy and branches

[Andreas Pieber]

I think so too. If we ONLY backport real bugs and nothing else it would be
quite minimal imho. Let the branches grow as needed :-)
Kind regards, Andreas
On Jan 16, 2013 6:09 PM, "Jean-Baptiste Onofré"  wrote:

> 2.2.10 is a kind of particular, because it should have been a minor
> release (and not a micro).
>
> Anyway, stop working on it and support is not the same thing IMHO.
>
> Let say, we get 2.4 out:
> - we will work on 2.x branch (for 2.4.0, 2.5.0-SNAPSHOT, etc)
> - we can "for transition purpose" support 2.3.x and 2.2.x: it's just bug
> fixes on those branches.
>
> WDYT ?
>
> Regards
> JB
>
> On 01/16/2013 05:57 PM, Ioannis Canellos wrote:
>
>> Currently we are at 2.3.0 and 2.2.10. Does it mean that if we get out 2.4
>> to provide new features to our users, we will stop working on 2.2.x?
>> How would this work when we get 3.0.0 out?
>>
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [DISCUSS] Switching to Git

[Andreas Pieber]

Nope, they're just git repos; and IIRC we're still not allowed
directly merging from github (adding the branch as remote branch and
cherry-pick the commit)... (are we?)

Kind regards,
Andeas

On Thu, Jan 17, 2013 at 10:33 PM, Andrei Pozolotin
 wrote:
> primary benefit of github is pull request and code review tools / workflow;
>
> will new karaf git repo provide these?
>
>  Original Message 
> Subject: Re: [DISCUSS] Switching to Git
> From: Andreas Pieber 
> To: Apache Karaf 
> Date: Thu 17 Jan 2013 09:26:07 AM CST
>> BUT all git repos will still be mirrored to github. So you can pull
>> them however you like.
>>
>> Kind regards,
>> Andreas
>>
>> On Thu, Jan 17, 2013 at 4:18 AM, Freeman Fang  wrote:
>>> Hi,
>>>
>>> I don't think the repo would be hosted on github.
>>>
>>> Btw, if you have any issue to access the github, try the blog[1] here, 
>>> yeah, it's in Chinese, but it's not a problem for you, :-)
>>> [1]http://blog.chinaunix.net/uid-9078996-id-2010324.html
>>> －
>>> Freeman(Yue) Fang
>>>
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
>>> Web: http://fusesource.com | http://www.redhat.com/
>>> Twitter: freemanfang
>>> Blog: http://freemanfang.blogspot.com
>>> http://blog.sina.com.cn/u/1473905042
>>> weibo: @Freeman小屋
>>>
>>> On 2013-1-17, at 上午10:20, Tang Yong wrote:
>>>
>>>> I want to ask if switching into git, whether using github to create karaf 
>>>> source repository or not? Because I am behind proxy, I wish that once 
>>>> switching into git, I can use "http" protocol to clone git repo not only 
>>>> "git" protocol.
>>>>
>>>> Thanks
>>>> --Tang
>>>>
>>>> Freeman Fang wrote:
>>>>> +1 to use git
>>>>> －
>>>>> Freeman(Yue) Fang
>>>>> Red Hat, Inc. FuseSource is now part of Red Hat
>>>>> Web: http://fusesource.com | http://www.redhat.com/
>>>>> Twitter: freemanfang
>>>>> Blog: http://freemanfang.blogspot.com
>>>>> http://blog.sina.com.cn/u/1473905042
>>>>> weibo: @Freeman小屋
>>>>> On 2013-1-16, at 下午5:10, Guillaume Nodet wrote:
>>>>>> What do you guys think about switching from svn to git ?
>>>>>> I think most of us already use git-svn so I think it would benefit us all
>>>>>> to use a native git repo instead.
>>>>>>
>>>>>> --
>>>>>> 
>>>>>> Guillaume Nodet
>>>>>> 
>>>>>> Blog: http://gnodet.blogspot.com/
>>>>>> 
>>>>>> FuseSource, Integration everywhere
>>>>>> http://fusesource.com
>

Re: [DISCUSS] Switching to Git

[Andreas Pieber]

BUT all git repos will still be mirrored to github. So you can pull
them however you like.

Kind regards,
Andreas

On Thu, Jan 17, 2013 at 4:18 AM, Freeman Fang  wrote:
> Hi,
>
> I don't think the repo would be hosted on github.
>
> Btw, if you have any issue to access the github, try the blog[1] here, yeah, 
> it's in Chinese, but it's not a problem for you, :-)
> [1]http://blog.chinaunix.net/uid-9078996-id-2010324.html
> －
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: http://fusesource.com | http://www.redhat.com/
> Twitter: freemanfang
> Blog: http://freemanfang.blogspot.com
> http://blog.sina.com.cn/u/1473905042
> weibo: @Freeman小屋
>
> On 2013-1-17, at 上午10:20, Tang Yong wrote:
>
>> I want to ask if switching into git, whether using github to create karaf 
>> source repository or not? Because I am behind proxy, I wish that once 
>> switching into git, I can use "http" protocol to clone git repo not only 
>> "git" protocol.
>>
>> Thanks
>> --Tang
>>
>> Freeman Fang wrote:
>>> +1 to use git
>>> －
>>> Freeman(Yue) Fang
>>> Red Hat, Inc. FuseSource is now part of Red Hat
>>> Web: http://fusesource.com | http://www.redhat.com/
>>> Twitter: freemanfang
>>> Blog: http://freemanfang.blogspot.com
>>> http://blog.sina.com.cn/u/1473905042
>>> weibo: @Freeman小屋
>>> On 2013-1-16, at 下午5:10, Guillaume Nodet wrote:
 What do you guys think about switching from svn to git ?
 I think most of us already use git-svn so I think it would benefit us all
 to use a native git repo instead.

 --
 
 Guillaume Nodet
 
 Blog: http://gnodet.blogspot.com/
 
 FuseSource, Integration everywhere
 http://fusesource.com
>>
>

Re: [DISCUSS] Switching to Git

[Andreas Pieber]

I'm using git on 98% of my projects and using git-svn on all asf
projects; thanks to git-svn and the good mirror system of the ASF in
fact I don't really care. I would use git that and that way :-)

+0

Kind regards,
Andreas

On Wed, Jan 16, 2013 at 11:07 AM, Guillaume Nodet  wrote:
> The ASF supports git now.  The ASF would not allow the canonical repo not
> to be hosted at the ASF anyway.
> A bunch of project have already switched to git:
> https://git-wip-us.apache.org/repos/asf
>
>
> On Wed, Jan 16, 2013 at 11:04 AM, Christian Schneider <
> ch...@die-schneider.net> wrote:
>
>> +1
>>
>> Where would we host this repo? Does apache have its own git
>> infrastructure or would we use github?
>>
>> Christian
>>
>> On 16.01.2013 10:10, Guillaume Nodet wrote:
>> > What do you guys think about switching from svn to git ?
>> > I think most of us already use git-svn so I think it would benefit us all
>> > to use a native git repo instead.
>> >
>>
>>
>
>
> --
> 
> Guillaume Nodet
> 
> Blog: http://gnodet.blogspot.com/
> 
> FuseSource, Integration everywhere
> http://fusesource.com

Re: Create Karaf 2.4.x branch

[Andreas Pieber]

Actually I would even prefer Achims proposal. Since we almost always
add new features this would make the transition ways more logical.
Maybe we should also combine this with timed released (2 months?).
Micros are only bug-fix backports and we can cut those as required.

Kind regards,
Andreas

On Tue, Jan 15, 2013 at 5:53 PM, Achim Nierbeck  wrote:
> +1, and actually I think we might just skip 2.3.1 and call it a 2.4 after
> this one is applied :D
>
> what do you think
>
> regards, Achim
>
>
> 2013/1/15 Ioannis Canellos 
>
>> +1 on creating a 2.4 branch.
>> Personally I am ok at adding new features on micro releases as long as they
>> don't change the API, especially considering the speed at which we bring
>> out new major and minor ones.
>>
>> --
>> *Ioannis Canellos*
>> *
>>
>> **
>> Blog: http://iocanel.blogspot.com
>> **
>> Twitter: iocanel
>> *
>>
>
>
>
> --
>
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> OPS4J Pax for Vaadin 
> Commiter & Project Lead
> blog 

Re: Create Karaf 2.4.x branch

[Andreas Pieber]

maybe the solution should rather be increasing the speed of the minor
releases; as long as we keep to semver.org I don't see any problems by
it.

Kind regards,
Andreas

On Tue, Jan 15, 2013 at 5:46 PM, Ioannis Canellos  wrote:
> +1 on creating a 2.4 branch.
> Personally I am ok at adding new features on micro releases as long as they
> don't change the API, especially considering the speed at which we bring
> out new major and minor ones.
>
> --
> *Ioannis Canellos*
> *
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *

Create Karaf 2.4.x branch

[Andreas Pieber]

Hey Guys,

I would like to commit Karaf-1563 [1] to the 2.x line; but the only
branch available now is 2.3.x; while I know that a common argument now
will be that we should rather focus on 3.x I simply don't like the
idea to apply new features to micro releases. Those should always be
stable and new features simply cant gurantee this!

Kind regards,
Andreas

[1] https://issues.apache.org/jira/browse/KARAF-1563

Re: Text editing in the Karaf console

[Andreas Pieber]

Definitely a BIG +1. I've done some quick editing with your patch,
karaf and the editor and I must admit I REALLY like it. Although not
perfect it would have been so incredible useful to have such a tool in
the runtime environment from time to time I'm strongly +1 to simply
include it as it and enhance/improve it as required.

Kind regards,
Andreas

On Mon, Jan 14, 2013 at 1:59 PM, Ioannis Canellos  wrote:
> I've update issue:  https://issues.apache.org/jira/browse/KARAF-2044
>
> with 2 patches, one for trunk and one for 2.3.x.
>
> If there are no objections I'd like to commit those and maybe also for
> 2.2.x.
>
> --
> *Ioannis Canellos*
> *
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *

Re: [Discuss] Apache Karaf 2.3.1 RC in two weeks time?

[Andreas Pieber]

+1

Kind regards, Andreas
On Jan 8, 2013 6:17 PM, "Jamie G."  wrote:

> Hi All,
>
> First off, happy new year to the community, secondly, I'd like to
> schedule Apache Karaf 2.3.1 RC for two weeks time from now.
>
> We have a lot of resolved issues at the moment, and several issues in
> progress. I think 2 weeks should be sufficient to close up these
> in-flight issues, then prep for the RC build.
>
> Are there any issues that anyone sees as a show stopper that would
> require a longer development window?
>
> Cheers,
> Jamie
>

Re: [VOTE] Apache Karaf EIK 0.9.0 release

[Andreas Pieber]

Built/Test and give it a short look; Legal things (NOTICE; ...) seams to be
in place too. Artifacts are valid too.

+1

Kind regards,
Andreas


On Wed, Jan 9, 2013 at 3:10 AM, Jean-Baptiste Onofré wrote:

> +1 (binding)
>
> Regards
> JB
>
>
> On 01/04/2013 09:55 PM, Jean-Baptiste Onofré wrote:
>
>> Hi all,
>>
>> this is the first release of Eclipse Integration for Karaf (EIK).
>>
>> You can have detail of the release in the RELEASE-NOTES:
>> http://svn.apache.org/repos/**asf/karaf/eik/trunk/RELEASE-**NOTES
>>
>> Staging repository:
>> https://repository.apache.org/**content/repositories/**
>> orgapachekaraf-088/
>>
>> 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.
>>
>> Thanks !
>>
>> Regards
>> JB
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Clean karaf.data/cache or karaf.data (KARAF-1563)

[Andreas Pieber]

Thank you very much for the review; I've corrected this and uploaded the
new patch. If there aren't any further comments I'll apply the patch to the
master and the 2.x branch.


On Fri, Jan 4, 2013 at 12:48 PM, Christoph Gritschenberger <
christoph.gritschenber...@gmail.com> wrote:

> The option descriptions are the same for "clean", and "clean cache".
> Aside from that, the patch works great.
>
> kind regards,
> christoph
>
> On 02/01/13 10:28, Andreas Pieber wrote:
> > Hey guys,
> >
> > I've attached a patch to [1]. Basically what it enables you is to either
> > delete your entire data folder on every reboot (or only the cache
> > directory). In addition the same options had been added to the restart
> > command. Finally the same option is also possible "one-time" by putting a
> > clean_all or clean_cache file into your data folder. Does this make sense
> > to you? Any further extensions wished for? Otherwise I'll apply to karaf
> > 2.4 and 3.0
> >
> > Kind regards,
> > Andreas
> >
> > [1] https://issues.apache.org/jira/browse/KARAF-1563
> >
>
>
>

Re: Text editing in the Karaf console

[Andreas Pieber]

well, in that case I think a github project might be the best solution.
Independently we can still include it in trunk as a reference then (which
would still have my +1)..

Kind regards,
Andreas


On Thu, Jan 3, 2013 at 1:55 PM, Ioannis Canellos  wrote:

> I am not sure if having it as part of the Karaf trunk would be a really
> good idea.
> Such editor can have a wider scope than the container itself and at its
> early days it could use a faster release cycle and/or contributions from
> other communities with similar needs that are not using karaf.
>
> Of course, there is always the maintenance burden of an extra subproject
> which we should take into consideration.
>
> Thoughts?
>
> --
> *Ioannis Canellos*
> *
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *
>

Clean karaf.data/cache or karaf.data (KARAF-1563)

[Andreas Pieber]

Hey guys,

I've attached a patch to [1]. Basically what it enables you is to either
delete your entire data folder on every reboot (or only the cache
directory). In addition the same options had been added to the restart
command. Finally the same option is also possible "one-time" by putting a
clean_all or clean_cache file into your data folder. Does this make sense
to you? Any further extensions wished for? Otherwise I'll apply to karaf
2.4 and 3.0

Kind regards,
Andreas

[1] https://issues.apache.org/jira/browse/KARAF-1563

Re: Text editing in the Karaf console

[Andreas Pieber]

TBH I would neither have a problem putting this directly on trunk. +1 from
my side.

Kind regards,
Andreas


On Fri, Dec 28, 2012 at 4:24 PM, Jean-Baptiste Onofré wrote:

> Hi Ioannis,
>
> it could be awesome to have a kind of vi in Karaf shell ;)
>
> It could be very interesting to mix your text editor with internal (Karaf)
> commands and external (system) commands.
>
> +1 to start to take a look on that on trunk.
>
> Regards
> JB
>
>
> On 12/28/2012 04:21 PM, Ioannis Canellos wrote:
>
>> I took a stub at creating a console text editor written in java based on
>> jansi and jline.
>>
>> The current implementation is quite simple, loads the whole file into the
>> memory and allows simple text editing operations, scrolling and also
>> undo/redo, paste, save etc.
>>
>> There is a lot of cleaning up to do and a lot of space for improvements
>> and
>> I was wondering which would be the ideal home for this project.
>>
>> Thoughts?
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Karaf version 2.2.10

[Andreas Pieber]

Hey,

You've forgotten me ;-)

Kind regards,
Andreas


On Fri, Dec 21, 2012 at 7:06 PM, Jamie G.  wrote:

> Hi,
>
> The vote has passed with the following result :
>
>   +1 (binding): Jean-Baptiste Onofré, Freeman Fang, Achim Nierbeck,
> Ioannis Canellos and Jamie Goodyear.
>   +1 (non binding): Christian Schneider, and Johan Edstrom
>
> I will copy this release to the Karaf dist directory and promote the
> artifacts to the central Maven repository.
>
> Cheers,
> Jamie
>
> On Fri, Dec 21, 2012 at 12:51 PM, Jamie G. 
> wrote:
> > +1
> >
> > All the signatures check out green :)
> >
> > I'm going to give a little bit of extra time for people to get their
> > vote in - the 72 hour period ends in about another hour.
> >
> > Cheers,
> > Jamie
> >
> > On Thu, Dec 20, 2012 at 1:21 PM, Johan Edstrom 
> wrote:
> >> +1 Non binding.
> >> And Merry New Festivus and all that!
> >>
> >> On Dec 20, 2012, at 9:48 AM, Ioannis Canellos 
> wrote:
> >>
> >>> +1
> >>>
> >>> --
> >>> *Ioannis Canellos*
> >>> *
> >>>
> >>> **
> >>> Blog: http://iocanel.blogspot.com
> >>> **
> >>> Twitter: iocanel
> >>> *
> >>
>

Re: [VOTE] Release Karaf version 2.2.10

[Andreas Pieber]

build & tests run fine; license/notice looks fine; signatures are OK; build
artifacts work OK with my tests.

BUT looking at the release notes I still think that we should finally adopt
to semver ;-)

+1 (binding)

Kind regards,
Andreas


On Thu, Dec 20, 2012 at 12:11 AM, Achim Nierbeck wrote:

> +1 (binding)
>
> regards, Achim
>
>
> 2012/12/19 Christian Schneider 
>
> > I tested Karaf 2.2.10 on Linux with CXF 2.7.0 and 2.7.1 and Camel 2.10.3.
> >
> > Looks good
> > +1 (non binding)
> >
> > Christian
> >
> >
> >
> > On 18.12.2012 18:10, Jamie G. wrote:
> > > Hi,
> > >
> > > We resolved 55 issues in this release (web page will be published post
> > > RC promotion):
> > >
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.2.10-release.page
> > >
> > > Staging repository:
> > > https://repository.apache.org/content/repositories/orgapachekaraf-046/
> > >
> > > Release tags:
> > > https://svn.apache.org/repos/asf/karaf/tags/karaf-2.2.10/
> > >
> > > 2.2.x Dependencies table:
> > >
> >
> https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.2.x.page
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > This vote will be open for 72 hours.
> >
> >
>
>
> --
>
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> OPS4J Pax for Vaadin 
> Commiter & Project Lead
> blog 
>

Re: [PROPOSAL] Release planning

[Andreas Pieber]

Nothing to add; I like the plans :-) +1 to 0.9 and +1 to get Karaf out ASAP
Aries is done.

Kind regards,
Andreas


On Mon, Dec 17, 2012 at 11:24 AM, Jamie G.  wrote:

> 1) 0.9.0 makes sense to me, +1
>
> 2) +1, I'd like to add a 2.2.10 release to the list as well.
>
> Cheers,
> Jamie
>
> On Mon, Dec 17, 2012 at 5:57 AM, Filippo Balicchia 
> wrote:
> > Hi Jb,
> >
> > for 1)
> > +1 In IMHO use minor number is the best choice.
> >
> > for 2)
> >
> > +1
> >
> >
> > Regards.
> >
> > --Filippo
> >
> >
> > 2012/12/17 Achim Nierbeck :
> >> Hi JB,
> >>
> >> for 1) I think it's to early to give it a major number version
> therefore a
> >> 0.9.0 version fits probably best.
> >> so +1
> >>
> >> for 2) everything sounds like a good plan.
> >> +1
> >>
> >> regards, Achim
> >>
> >>
> >> 2012/12/17 Jean-Baptiste Onofré 
> >>
> >>> Hi all,
> >>>
> >>> I would like to plan some releases in the following weeks.
> >>>
> >>> 1/ EIK
> >>> EIK is now ready for a first release. I will close a couple of issues
> >>> today and review the legal stuff (especially the NOTICE and LICENSE
> files,
> >>> as we "use" some Eclipse parts).
> >>> I propose to cut off EIK 3.0.0 this week. By the way, is 3.0.0 version
> >>> make sense for you ? My proposal would be to change to 0.9 version as
> it's
> >>> the first EIK one.
> >>>
> >>> 2/ Karaf
> >>> Both trunk and karaf-2.3.x have an issue with Aries Blueprint (some
> >>> bundles stay in GracePeriod forever at startup). Dan tried a fix in
> Aries
> >>> that he reverted. I'm working on it and I will probably update to Aries
> >>> SNAPSHOTs in Karaf. I will request the help of Guillaume and Dan, both
> to
> >>> help me around the fix, and to plan an Aries release as well.
> >>> In the mean time, I will move forward on the Karaf 2.3.x pending
> issues.
> >>> As soon as we have a new Aries release, we can:
> >>> - release 2.3.1
> >>> - release 3.0.0.RC1
> >>>
> >>> WDYT ?
> >>>
> >>> Regards
> >>> JB
> >>> --
> >>> Jean-Baptiste Onofré
> >>> jbono...@apache.org
> >>> http://blog.nanthrax.net
> >>> Talend - http://www.talend.com
> >>>
> >>
> >>
> >>
> >> --
> >>
> >> Apache Karaf  Committer & PMC
> >> OPS4J Pax Web 
> Committer &
> >> Project Lead
> >> OPS4J Pax for Vaadin  >
> >> Commiter & Project Lead
> >> blog 
>

Re: [VOTE] Release Apache Karaf Cellar 2.2.5 (3rd try)

[Andreas Pieber]

I'm sorry, tested and checked at the morning already. Looks good to me.

+1

Kind regards,
Andreas
On Dec 3, 2012 9:09 PM, "Jean-Baptiste Onofré"  wrote:

> I propose to extend as this release looks OK and we had votes on the two
> first tries.
>
> Regards
> JB
>
> On 12/03/2012 07:29 PM, Jamie G. wrote:
>
>> All the signatures were good. Given this vote is past due should an
>> extension be granted? I don't see a new cut being required..
>>
>> Jamie
>>
>> On Thu, Nov 29, 2012 at 6:37 PM, Jean-Baptiste Onofré 
>> wrote:
>>
>>> Hi all,
>>>
>>> We solved 27 issues in this release that you can find in the
>>> RELEASE-NOTES:
>>> http://svn.apache.org/repos/**asf/karaf/cellar/tags/cellar-**
>>> 2.2.5/RELEASE-NOTES
>>>
>>> Staging repository:
>>> https://repository.apache.org/**content/repositories/**
>>> orgapachekaraf-098/
>>>
>>> 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.
>>>
>>> Thanks
>>> 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
>

Re: Text editing in the Karaf console

[Andreas Pieber]

@Ioannis: That's a really great idea! You'll definitely have my Kudos for
that :-)

@Guillaume: Why unix specifc? You've e.g. edit in windows (as Ioannis
noticed).

@JB Executing native commands could be kind of dangerous. For example, just
because Karaf need some permissions to modify /etc/xyz you might don't like
your users to do so directly via Karaf (rm -rf /etc/xyz).

Kind regards,
Andreas

On Sun, Dec 2, 2012 at 10:35 PM, Jean-Baptiste Onofré wrote:

> Hi Ioannis,
>
> interesting, especially if it works with multiple platform.
>
> It could be tricky to "maintain" ;) but interesting for the users.
>
> Around the same area, I would like to add an escape character (like !) to
> execute native command directly from the Karaf shell (like !ls -l for
> instance).
>
> Regards
> JB
>
>
> On 12/02/2012 06:40 PM, Ioannis Canellos wrote:
>
>> Hi guys,
>>
>> One feature I've always liked to have in the karaf console is the ability
>> to edit text files. See https://issues.apache.org/**
>> jira/browse/KARAF-2044 
>>
>> I took a stub last night, to integrate existing editors that might be
>> present in the system with the Karaf console (e.g. vi, nano or edit in
>> windows).
>> To my surprise starting the editor as a new Process and wiring input and
>> output seems to just work.
>>
>> There are just a few things I'd like to solve before committing and I
>> wanted some ideas:
>>
>> i) I can pass the terminal height and width to the process, but how do I
>> get those values get updated if I resize while the editor is open?
>> ii) Some editor don't take kindly the delete character and prefer
>> backspace
>> (changing ascii 127 to ascii 8). Is this safe to do. Is there a better way
>> to handle it?
>> iii) After closing the editor, the console sometimes gets "flaky" arrow
>> keys might stop working etc.
>>
>> Thoughts?
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Board report for December, 2012

[Andreas Pieber]

+1; nothing to add from my point of view

Kind regards,
Andreas


On Sat, Dec 1, 2012 at 7:39 PM, Jean-Baptiste Onofré wrote:

> Hi all,
>
> I prepared the board report for December, 2012:
>
> https://cwiki.apache.org/**confluence/display/KARAF/**Board+Reports
>
> Please, review it and update it if I forgot something.
> I would like to send the report quickly.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: RFC on proposal to allow hooks into Karaf shutdown

[Andreas Pieber]

OK, I think this  is a completely different problem I would rather
like to discuss on a different thread. But my short analyses here: if
you give main a shot, you'll notice that there's already some
exit-code/restart logic... a new var cold_restart which will set a
fixed exit code (e.g. 99) would do the job. WDYT?

Kind regards,
Andreas

On Fri, Nov 30, 2012 at 5:35 AM, Dan Tran  wrote:
> In the same line i also like to see this
> https://issues.apache.org/jira/browse/KARAF-1180  but not sure how to
> implement it
>
> -D
>
> On Thu, Nov 29, 2012 at 8:24 PM, Andreas Pieber  wrote:
>> Short answer: why not :-)
>>
>> Longer answer: I've though about it for some time now (since you
>> provided this proposal on the user list) but I cannot really come up
>> with a counter argument speaking against this.
>>
>> So, from my point of view it's definitely worth giving this a shot!
>>
>> Kind regards,
>> Andreas
>>
>> On Fri, Nov 30, 2012 at 5:15 AM, Raman Gupta  wrote:
>>> I sent this to the users mailing list, but it probably belongs more on
>>> dev. I'd like to hook into the Karaf shutdown process at a higher
>>> level than the OSGi bundle shutdown. The bundle shutdown starts
>>> prematurely shutting down services and such that are necessary for
>>> work in progress to complete.
>>>
>>> For now, I've implemented this with a custom Karaf command that
>>> executes my application shutdown, and then delegates to the Karaf
>>> StopCommand to shutdown Karaf itself. However, this is not an ideal
>>> solution as it requires my custom command to be explicitly executed.
>>> For example, it will not run when a user does a normal kill or Ctrl-D
>>> in the console.
>>>
>>> Ideally, Karaf would have a "ShutdownHook" interface/service I could
>>> implement in my bundles -- for each one of these registered, Karaf
>>> would execute them before stopping the framework bundles. Based on an
>>> initial look at the Karaf source, I'm thinking the best place to do
>>> this is:
>>>
>>> ./main/src/main/java/org/apache/karaf/main/Main.java
>>>
>>> Just before the call to framework.stop(), we use the BundleContext to
>>> obtain and execute a shutdown method on all services that implement a
>>> new "FrameworkShutdownHook" interface.
>>>
>>> Then, proceed to framework.stop().
>>>
>>> Thoughts on this approach? If the devs are OK with it, I can
>>> implement  this.
>>>
>>> Regards,
>>> Raman Gupta
>>> Principal
>>> VIVO Systems

Re: RFC on proposal to allow hooks into Karaf shutdown

[Andreas Pieber]

Short answer: why not :-)

Longer answer: I've though about it for some time now (since you
provided this proposal on the user list) but I cannot really come up
with a counter argument speaking against this.

So, from my point of view it's definitely worth giving this a shot!

Kind regards,
Andreas

On Fri, Nov 30, 2012 at 5:15 AM, Raman Gupta  wrote:
> I sent this to the users mailing list, but it probably belongs more on
> dev. I'd like to hook into the Karaf shutdown process at a higher
> level than the OSGi bundle shutdown. The bundle shutdown starts
> prematurely shutting down services and such that are necessary for
> work in progress to complete.
>
> For now, I've implemented this with a custom Karaf command that
> executes my application shutdown, and then delegates to the Karaf
> StopCommand to shutdown Karaf itself. However, this is not an ideal
> solution as it requires my custom command to be explicitly executed.
> For example, it will not run when a user does a normal kill or Ctrl-D
> in the console.
>
> Ideally, Karaf would have a "ShutdownHook" interface/service I could
> implement in my bundles -- for each one of these registered, Karaf
> would execute them before stopping the framework bundles. Based on an
> initial look at the Karaf source, I'm thinking the best place to do
> this is:
>
> ./main/src/main/java/org/apache/karaf/main/Main.java
>
> Just before the call to framework.stop(), we use the BundleContext to
> obtain and execute a shutdown method on all services that implement a
> new "FrameworkShutdownHook" interface.
>
> Then, proceed to framework.stop().
>
> Thoughts on this approach? If the devs are OK with it, I can
> implement  this.
>
> Regards,
> Raman Gupta
> Principal
> VIVO Systems

Re: [VOTE] Release Apache Karaf Cellar 2.2.5

[Andreas Pieber]

+1 source build with tests work, signatures are ok. Simple samples work
too. Looks good to me.

Kind regards, Andreas
On Nov 26, 2012 11:05 PM, "Jean-Baptiste Onofré"  wrote:

> Hi all,
>
> We solved 27 issues in this release that you can find in the RELEASE-NOTES:
> http://svn.apache.org/repos/**asf/karaf/cellar/tags/cellar-**
> 2.2.5/RELEASE-NOTES
>
> Staging repository:
> https://repository.apache.org/**content/repositories/**orgapachekaraf-079/
>
> 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.
>
> Thanks
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Karaf Cellar 2.2.5

[Andreas Pieber]

+1

Kind regards,
Andreas

On Sat, Nov 24, 2012 at 10:07 AM, Ioannis Canellos  wrote:
> +1
> --
> *Ioannis Canellos*
> *
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *