cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dav...@apache.org
Subject Re: Should DOSGi have it's own JIRA?
Date Thu, 17 Dec 2009 10:33:39 GMT
Yeah - I think its a good idea to put CXF DOSGi as a separate project in JIRA.

Thanks,

David

2009/12/17 Daniel Kulp <dkulp@apache.org>:
>
> Is there any objections to moving the DOSGI stuff out to it's own JIRA?  If
> not, I'll do so on Friday.   Speak now...  :-)
>
> Dan
>
>
> On Mon December 14 2009 2:39:17 pm Daniel Kulp wrote:
>> 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