Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C98629FBF for ; Mon, 28 May 2012 17:17:48 +0000 (UTC) Received: (qmail 39026 invoked by uid 500); 28 May 2012 17:17:48 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 38977 invoked by uid 500); 28 May 2012 17:17:48 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 38968 invoked by uid 99); 28 May 2012 17:17:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 May 2012 17:17:48 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sberyozkin@gmail.com designates 209.85.215.169 as permitted sender) Received: from [209.85.215.169] (HELO mail-ey0-f169.google.com) (209.85.215.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 May 2012 17:17:40 +0000 Received: by eaan1 with SMTP id n1so853609eaa.0 for ; Mon, 28 May 2012 10:17:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=gXeW9+38tXIA9xrG7Kmx5dXoni73CQzp8vms1ZMJn8o=; b=VHK5D8kw8QSyudv/dLVVrL74Z2JLo9xIvQPtdP4vLzS34s/aZTP8p25HJuNRSXR34s dqQ/wnvofPXS+9U0gsRlFWsYYikRPM5PA80f+fx30CZ5rkJbUZrZwTbh8zWvPEC/AtI4 V5wHMTqq9nfiMgW/wQPpqRY1zwFyu/Q4XI8QCbwuldPSBhLdMYlGMNt+c/WZ9Q2+HTMh CxGHWEFNnh+b2k4v0tJ2eNOHcPNdaF1+T4zmYPjbkC2nZ8N+MuW43y1tddG3nKUd+Fqs 9+qg/2XuFERN7j4exeAZK1yndTpRUlIUj3lRqSeoNy38WUjcnGORqBmygUoQgOF5nbyF PNrQ== Received: by 10.14.22.8 with SMTP id s8mr2356990ees.33.1338225439478; Mon, 28 May 2012 10:17:19 -0700 (PDT) Received: from [192.168.2.3] ([89.100.190.158]) by mx.google.com with ESMTPS id y54sm39424147eef.10.2012.05.28.10.17.18 (version=SSLv3 cipher=OTHER); Mon, 28 May 2012 10:17:18 -0700 (PDT) Message-ID: <4FC3B31D.4060506@gmail.com> Date: Mon, 28 May 2012 18:17:17 +0100 From: Sergey Beryozkin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: dev@cxf.apache.org Subject: Re: Thoughts about DOSGI 1.3.2 release References: <4FC3A916.3000001@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi David On 28/05/12 18:09, David Bosschaert wrote: > Sounds good, Sergey. I'm all for releasing frequently. > > One of the things that I think would be good to tackle is to migrate > to OSGi Blueprint (from of the current Spring-based approach). Is that > something that you were thinking of looking at? > Not really. Some users would like to use Blueprint but not be bound to Aries. So for me it's a DOSGI 1.4 level issue which will require a significant time investment. Cheers, Sergey > Cheers, > > David > > On 28 May 2012 17:34, Sergey Beryozkin wrote: >> Hi >> >> I'm thinking of starting working toward releasing DOSGI 1.3.2. >> I think I'll spend the next 2 or months on fixing few issues I can find some >> time for, given that there's a lot of other CXF/etc work that needs to be >> taken care of. >> I'd like to suggest that the next release will be 1.3.2 as opposed to 1.4.0. >> Moving to CXF 2.6.1 at the DOSGI level will be a pretty major effort, giving >> that a minimal bundle in CXF 2.6.x has gone. >> >> It seems that there are still quite a few issues there that are important to >> be fixed for the base/simple DOSGI applications to work reliably and given >> that 2.5.x branch is still relatively 'young', I'd probably prefer to stay >> on 2.5.x (2.5.4 for DOSGI 1.3.2 and might be CXF 2.5.5/2.5.6 for DOSGI >> 1.3.3), simply to make the most of the limited time that I will be able to >> spend on DOSGi, before making a major switch to CXF 2.6.x - and hoping by >> that time many of the 'basic' DOSGI features have been fixed... >> >> Thanks, Sergey >>