Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C95B85.8952BFF7"
Subject: RE: Would it make sense to add a Distributed-OSGi component to
 CXF-Jira?
Date: Thu, 11 Dec 2008 06:41:43 -0500
Message-ID: 
 <C9D84D2ABB857D4596AF69377F48488B03B90A@MAIL02.bedford.progress.com>
Thread-Topic: Would it make sense to add a Distributed-OSGi component to
 CXF-Jira?
Thread-Index: AclbhBrKa6ODyoyYTGuM7+lEV6bZNgAAVW6I
References: <a1e060230812110327x98d79cpb8c2cfdb483712ef@mail.gmail.com>
From: "Eoghan Glynn" <eoglynn@progress.com>
To: <davidb@apache.org>, <dev@cxf.apache.org>

------_=_NextPart_001_01C95B85.8952BFF7
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Yep agreed, makes sense to have a separate distributed OSGi category in =
JIRA.

Cheers,
Eoghan


-----Original Message-----
From: david.bosschaert@gmail.com on behalf of davidb@apache.org
Sent: Thu 11/12/2008 11:27
To: dev@cxf.apache.org
Subject: Would it make sense to add a Distributed-OSGi component to =
CXF-Jira?
=20
Hi all,

Currently all of the bugs against the Distributed OSGi code are filed
in the 'OSGi' component in CXF. However I think this is potentially
confusing as the 'OSGi' component really hints to me that it relates
to OSGi properties of core CXF (e.g. the way OSGi metadata is added to
OSGi-bundelized CXF libraries).

Since this is quite a different area from the code that implements the
Distributed OSGi specification I was wondering would it make sense to
add a 'Distributed OSGi' component to JIRA as well for bugs relating
to that code?

Cheers,

David


------_=_NextPart_001_01C95B85.8952BFF7--