Return-Path: X-Original-To: apmail-karaf-user-archive@minotaur.apache.org Delivered-To: apmail-karaf-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 750D4D84F for ; Tue, 9 Oct 2012 13:59:58 +0000 (UTC) Received: (qmail 50961 invoked by uid 500); 9 Oct 2012 13:59:58 -0000 Delivered-To: apmail-karaf-user-archive@karaf.apache.org Received: (qmail 50921 invoked by uid 500); 9 Oct 2012 13:59:58 -0000 Mailing-List: contact user-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@karaf.apache.org Delivered-To: mailing list user@karaf.apache.org Received: (qmail 50909 invoked by uid 99); 9 Oct 2012 13:59:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2012 13:59:58 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bengt.rodehav@gmail.com designates 209.85.212.174 as permitted sender) Received: from [209.85.212.174] (HELO mail-wi0-f174.google.com) (209.85.212.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2012 13:59:53 +0000 Received: by mail-wi0-f174.google.com with SMTP id hq7so4717100wib.3 for ; Tue, 09 Oct 2012 06:59:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=on3MNWydSDKooNIos2QLSxuyIhWEg6rsrg/sAf2KFzM=; b=Uo68D60n+nq1rLwA0z0L5q3D1WclliLGFV6R58liH8mFP7q86oSCmn5xwXlvcnLuMv kXaOw2ERYJ8gyel0AxVkFqjxEtsrBLm8ciy/6D8IV0y+sBzsj+z0Vb0H0++ErHdCwocp lDP53kLTo46SNTIXL/wpFVAsemAF9eo6WV7IO6FjE+wzv9+5JtGWA63hPCa5R9LwCyoF 7hG4o6YJygGMOuxT4RlwpltGuovqKZrH3EAraA1UHJTdlSi8d7pVdaxUPIvNB1iPPhZZ 8BKqFGaMQlEZvSDBAzmVRdX6k+2BRTZbqdzVUDJkdlQTgMtRaXxVAILDxLtm9sjYNut0 hjAg== MIME-Version: 1.0 Received: by 10.180.86.202 with SMTP id r10mr4955141wiz.12.1349791172592; Tue, 09 Oct 2012 06:59:32 -0700 (PDT) Sender: bengt.rodehav@gmail.com Received: by 10.194.32.228 with HTTP; Tue, 9 Oct 2012 06:59:32 -0700 (PDT) In-Reply-To: References: Date: Tue, 9 Oct 2012 15:59:32 +0200 X-Google-Sender-Auth: boxB5mXJYh6tFeTI0z10Y_M32rc Message-ID: Subject: Re: Apache Karaf 2.3.0 vs 2.2.x From: Bengt Rodehav To: user@karaf.apache.org Content-Type: multipart/alternative; boundary=f46d044280ba5d053a04cba0bf65 X-Virus-Checked: Checked by ClamAV on apache.org --f46d044280ba5d053a04cba0bf65 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable OK - good. I wasn't aware that 0.3.1 fixed this issue. TBH I find it extremely hard to keep track of Aries different releases and what's included in what release. I can't even find any information about the 0.3.1 release on theire web site. I can't even find the release notes for the current (1.0.0?) release. As a developer it=B4s pretty hard to upgrade your Aries dependencies on you= r own since I have no idea which versions of which modules have actually been tested and verified together. This might have improved now but the idea of releasing every little module on its own instead of providing a complete set of modules that are known to work together is not very user friendly. I tend to rely on projects like Karaf and use the version of Aries that you use. So, I'm glad you guys solved it for me. Thanks, /Bengt 2012/10/9 Achim Nierbeck > Hi Bengt, > > to my knowledge Karaf 2.2.9 uses a 0.3.1 (or higher) which also > includes the corresponding Bug-Fix and therefore should work. > > regards, Achim > > 2012/10/9 Bengt Rodehav : > > Just a question since I've seen that Karaf 2.3.0 is in the works. > > > > I've just encountered a bug in Aries Proxy 0.3 (Aries-908 in JIRA) that > > causes Proxy 0.3 to fail with JVM 1.6.0_33 and later. This has been > fixed > > in Aries but I noticed that Karaf 2.2.9 still uses Proxy 0.3. Karaf 2.3= .0 > > seems to have been upgrade to Proxy 1.0 (which should work). > > > > Are there any plans to release a Karaf 2.2.10 with a new proxy version? > > Otherwise, I believe many people may encounter the same problem I did > when > > upgrading their JVM version. For me personally I'm waiting for the 2.3.= 0 > to > > be released and then I'll upgrade my custom distribution. Not sure how > > people generally do this but a 2.2.10 with an upgraded proxy might be > needed > > for some people. > > > > /Bengt > > > > -- > > Apache Karaf Committer & PMC > OPS4J Pax Web > Committer & Project Lead > OPS4J Pax for Vaadin > Commiter & Project > Lead > blog > --f46d044280ba5d053a04cba0bf65 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable OK - good. I wasn't aware that 0.3.1 fixed this issue.

TBH I find it extremely hard to keep track of Aries different releases a= nd what's included in what release. I can't even find any informati= on about the 0.3.1 release on theire web site. I can't even find the re= lease notes for the current (1.0.0?) release.

As a developer it=B4s pretty hard to upgrade your Aries= dependencies on your own since I have no idea which versions of which modu= les have actually been tested and verified together. This might have improv= ed now but the idea of releasing every little module on its own instead of = providing a complete set of modules that are known to work together is not = very user friendly. I tend to rely on projects like Karaf and use the versi= on of Aries that you use. So, I'm glad you guys solved it for me.

Thanks,

/Bengt

<= /div>


2012/10/9 Achim Nierbeck <bcanhome@googlemail.com>
Hi Bengt,

to my knowledge Karaf 2.2.9 uses a 0.3.1 (or higher) which also
includes the corresponding Bug-Fix and therefore should work.

regards, Achim

2012/10/9 Bengt Rodehav <bengt@rode= hav.com>:
> Just a question since I've= seen that Karaf 2.3.0 is in the works.
>
> I've just encountered a bug in Aries Proxy 0.3 (Aries-908 in JIRA)= that
> causes Proxy 0.3 =A0to fail with JVM 1.6.0_33 and later. This has been= fixed
> in Aries but I noticed that Karaf 2.2.9 still uses Proxy 0.3. Karaf 2.= 3.0
> seems to have been upgrade to Proxy 1.0 (which should work).
>
> Are there any plans to release a Karaf 2.2.10 with a new proxy version= ?
> Otherwise, I believe many people may encounter the same problem I did = when
> upgrading their JVM version. For me personally I'm waiting for the= 2.3.0 to
> be released and then I'll upgrade my custom distribution. Not sure= how
> people generally do this but a 2.2.10 with an upgraded proxy might be = needed
> for some people.
>
> /Bengt



--

Apache Karaf <htt= p://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/>

--f46d044280ba5d053a04cba0bf65--