Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 41754 invoked from network); 2 Sep 2007 20:27:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Sep 2007 20:27:45 -0000 Received: (qmail 66871 invoked by uid 500); 2 Sep 2007 20:27:39 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 66785 invoked by uid 500); 2 Sep 2007 20:27:39 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 66773 invoked by uid 99); 2 Sep 2007 20:27:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Sep 2007 13:27:39 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.86.168.178] (HELO mxout-03.mxes.net) (216.86.168.178) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Sep 2007 20:27:33 +0000 Received: from [192.168.0.125] (unknown [80.240.191.89]) by smtp.mxes.net (Postfix) with ESMTP id BAB7E51931 for ; Sun, 2 Sep 2007 16:27:11 -0400 (EDT) Message-ID: <46DB1CA3.6020701@apache.org> Date: Sun, 02 Sep 2007 22:27:15 +0200 From: Grzegorz Kossakowski User-Agent: Thunderbird 2.0.0.5 (X11/20070719) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: OSGi integration component in JIRA References: <46DB0AD4.3030805@tuffmail.com> <46DB1061.8090303@nada.kth.se> In-Reply-To: <46DB1061.8090303@nada.kth.se> Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Daniel Fagerstrom pisze: > Grzegorz Kossakowski skrev: >> Hello, >> >> I tried to take a look at open issues for "Servlet Service Framework" >> component[1] and found out >> that most of these issues are not directly related to SSF at all. >> >> It's consequence of the fact that SSF component was Blocks-fw >> component and was renamed as most of >> blocks capabilities are handled by SSF now. However, when thinking >> about blocks-fw we had broader >> range of affairs in mind like creation of OSGi integration. Issues >> covering this integration are >> attributed to SSF which is wrong IMO. >> >> Therefore, I propose to create new component called OSGi integration >> and move all issues related to >> OSGi there. >> >> WDYT? > > +1 Done. -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/