cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin" <sbery...@progress.com>
Subject RE: Should DOSGi have it's own JIRA?
Date Mon, 14 Dec 2009 21:35:16 GMT
Hi,

Possibly yes for DOSGI, DOSGI RI project is a higher-level project given
that it incorporates CXF, and there is a link to the Distributed OSGi
project from the main CXF page so moving the issues part into a separate
JIRA should not affect the visibility of the project, as far as users
checking the CXF is concerned... David and Eoghan and others may have a
different opinion.

However, I'm much more pessimistic about moving the JAXRS component into
a separate subproject for a number of reasons. 

It is really another frontend, like Cobra and JAXWS. It is on the same
level as those frontends are. It is kind of contributing to CXF being
seen as a more complete framework capable of hosting different types of
services thus moving it away would start contributing to a more
'fragmented' view of what CXF is.
Another reason is that often enough CXF JAXRS fixes 'span' multiple
components in one go, say HTTP transport and common and the JAXRS
frontend itself. So it make it more difficult to push such fixes into
CXF JAXRS snapshots.

This is what I think at the moment.
Thanks, Sergey     
 

-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org] 
Sent: 14 December 2009 19:39
To: dev@cxf.apache.org
Subject: Should DOSGi have it's own JIRA?


Quick question:

What are peoples thoughts about pulling the DOSGi stuff from the "CXF"
JIRA 
into a separate CXFDOSGI (or just DOSGI) JIRA in the "Category: CXF"
section 
at:
https://issues.apache.org/jira/secure/BrowseProjects.jspa

There are pluses and minuses:
DOSGi has it's own release schedule, own version numbers,etc.... Thus,
having 
it's own project in JIRA allows it to track those things properly
without it 
affecting the main CXF project.

Also, DOSGi has it's own components such as its own build system, local
vs 
remote discovery, etc...   Having it's own JIRA project would allow
defining 
nice components for it's own uses.

On the minus side, it does kind of lower the visibility of the DOSGi
issues in 
the CXF JIRA since they wouldn't be there.   


One COULD argue that JAX-RS could also be pulled out.   However, the
JAX-RS 
stuff is currently part of the main build and released as part of the
full CXF 
stuff.  Thus, keeping it in is less of an issue.  If we eventually split
the 
builds into a "core", "webservices", "rest", etc... then it may make
sense to 
do so at that time.

Thoughts?

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

Mime
View raw message