Return-Path: X-Original-To: apmail-aries-dev-archive@www.apache.org Delivered-To: apmail-aries-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 F380AC6DF for ; Tue, 15 May 2012 16:12:10 +0000 (UTC) Received: (qmail 77579 invoked by uid 500); 15 May 2012 16:12:10 -0000 Delivered-To: apmail-aries-dev-archive@aries.apache.org Received: (qmail 77494 invoked by uid 500); 15 May 2012 16:12:10 -0000 Mailing-List: contact dev-help@aries.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aries.apache.org Delivered-To: mailing list dev@aries.apache.org Received: (qmail 77478 invoked by uid 99); 15 May 2012 16:12:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2012 16:12:09 +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 (nike.apache.org: domain of holly.k.cummins@googlemail.com designates 209.85.212.170 as permitted sender) Received: from [209.85.212.170] (HELO mail-wi0-f170.google.com) (209.85.212.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2012 16:12:03 +0000 Received: by wibhm6 with SMTP id hm6so2653879wib.5 for ; Tue, 15 May 2012 09:11:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=b9Jgref1VdpIieF82V+Dg4rAa/RsT3w7FeD6OUoCb2g=; b=YNCIBCvSrOQGv77ihZ+FJziK6fomo/r7fz6oLoztkn/fqE3i3G14Wm60o5bEohrw1q Dk+snrF+QTTtZbISjE5hAPxQ0hsdCmPfDMnJn/c2ZuVFGe1CgzdghxlOqaD0fsI/F663 4bwMDcljEImxyAvi5ywlJ67rkYlFas3e70hqCqCjiI6M235ruhrFNoM2M7oCrUJUhJIl eZVUUorLZgDfcNefXCLFLtwlgQlXVxCi27CFHGu1hM6m9W5pF9p26T5VBA12lD2yQQTb pLjbIg1qcKX77LyUoP3CgB/YWNYm5D8sA3OMpySPtzmUOGZq+jyb3J8gVHlezB8I4I++ fKnA== MIME-Version: 1.0 Received: by 10.180.83.72 with SMTP id o8mr4566786wiy.5.1337098303502; Tue, 15 May 2012 09:11:43 -0700 (PDT) Received: by 10.227.6.205 with HTTP; Tue, 15 May 2012 09:11:43 -0700 (PDT) In-Reply-To: References: Date: Tue, 15 May 2012 17:11:43 +0100 Message-ID: Subject: Re: Incoming code: The Big Move to 1.0.0 From: Holly Cummins To: dev@aries.apache.org Content-Type: text/plain; charset=ISO-8859-1 Comments inline. On Mon, May 14, 2012 at 12:40 PM, Alasdair Nottingham wrote: > Holly, > > Have we addressed the utils defect that includes a list of things that are > required for a 1.0 release? I think that's https://issues.apache.org/jira/browse/ARIES-582, which is resolved. > Also the RecursiveBundleTracker behaves > differently if you run on an R4.3 framework to an R4.2 framework. It > doesn't work with our application isolation model (which it was designed to > do) and works differently if we had a resolver hook isolation > implementation (if we don't). I think that needs to be resolved. Having it > behave weirdly isn't good. Aha, this is https://issues.apache.org/jira/browse/ARIES-827, isn't it? Which is unresolved, sadly. > I also think we need to ensure we pass the OSGi CTs for things like > blueprint, JMX etc before we release a 1.0 level (people will be surprised > if we don't). I think blueprint still has a few issues, although JNDI > passed last time I ran the CT as did JMX (well there were failures, but the > failures were due to bad tests). I think this makes sense. I'll have a look at running the Blueprint CTs first, since that's the component I'm intending to release first. > > Thanks > Alasdair > > P.S. Thanks for doing work here. > > On 11 May 2012 10:55, Guillaume Nodet wrote: > >> I wonder if it would make sense to move all packages to 1.0 version ? >> >> On Tue, May 8, 2012 at 1:19 PM, Holly Cummins < >> holly.k.cummins@googlemail.com> wrote: >> >> > Hi all, >> > >> > I'm just about to commit the big change which moves most Aries components >> > to 1.0.0 bundle and package versions. You may need to do a full rebuild, >> > starting with parent and eva-maven-plugin, to populate your maven repo. >> > >> > I've left some components I judged to be pre-1.0.0 at their current >> > versions. I also think jmx will need revisiting once jmx-next is merged >> > across. Even so, there were a lot of changes, so I undoubtedly got some >> > things wrong! Please let me know if you spot any errors or omissions or >> if >> > you think it all just looks terrible. >> > >> > Holly >> > >> >> >> >> -- >> ------------------------ >> Guillaume Nodet >> ------------------------ >> Blog: http://gnodet.blogspot.com/ >> ------------------------ >> FuseSource, Integration everywhere >> http://fusesource.com >> > > > > -- > Alasdair Nottingham > not@apache.org