[DISCUSS] Move some modules around

[Daniel Kulp <dk...@apache.org>]

I'd like to move some modules around in the src tree.   Basically, we've been 
hanging some stuff off of modules in distribution that really are no longer 
tied completely to the distribution.  In particular, a lot of the stuff in 
there is actually more important for OSGi than for the actual CXF 
distribution.    The karaf stuff, for example, really has nothing to do with 
the distribution at all.

I'd like to create a top level /osgi directory.   In there, we'd move the 
distribution/karaf and distribution/bundles directories.   Eventually, we 
could create an "/osgi/tests" or something that could include specific OSGi 
related tests. (pax-exam based maybe?)    I don't think the artifact/group 
id's of anything needs to change.  Just the parent location entries in the 
poms.  

Is everyone OK with that?  Does it make sense?

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

Re: [DISCUSS] Move some modules around

[Sergey Beryozkin <sb...@gmail.com>]

+1.

I'm also thinking of splitting rt/frontend/jaxrs a bit later on, to have 
the core module, the existing client API which I'd like to maintain 
after moving to jaxrs 2.0, and a module containing various extensions

Cheers, Sergey

On 27/09/11 20:45, Daniel Kulp wrote:
>
> I'd like to move some modules around in the src tree.   Basically, we've been
> hanging some stuff off of modules in distribution that really are no longer
> tied completely to the distribution.  In particular, a lot of the stuff in
> there is actually more important for OSGi than for the actual CXF
> distribution.    The karaf stuff, for example, really has nothing to do with
> the distribution at all.
>
> I'd like to create a top level /osgi directory.   In there, we'd move the
> distribution/karaf and distribution/bundles directories.   Eventually, we
> could create an "/osgi/tests" or something that could include specific OSGi
> related tests. (pax-exam based maybe?)    I don't think the artifact/group
> id's of anything needs to change.  Just the parent location entries in the
> poms.
>
> Is everyone OK with that?  Does it make sense?
>

Re: [DISCUSS] Move some modules around

[Jean-Baptiste Onofré <jb...@nanthrax.net>]

Hi Dan,

it makes sense for me. Especially, in the OSGi and Karaf ecosystem, a 
distribution is not really required, a feature could be enough 
(including specific OSGi bundles like the CXF Karaf commands).

Regards
JB

On 09/27/2011 09:45 PM, Daniel Kulp wrote:
>
> I'd like to move some modules around in the src tree.   Basically, we've been
> hanging some stuff off of modules in distribution that really are no longer
> tied completely to the distribution.  In particular, a lot of the stuff in
> there is actually more important for OSGi than for the actual CXF
> distribution.    The karaf stuff, for example, really has nothing to do with
> the distribution at all.
>
> I'd like to create a top level /osgi directory.   In there, we'd move the
> distribution/karaf and distribution/bundles directories.   Eventually, we
> could create an "/osgi/tests" or something that could include specific OSGi
> related tests. (pax-exam based maybe?)    I don't think the artifact/group
> id's of anything needs to change.  Just the parent location entries in the
> poms.
>
> Is everyone OK with that?  Does it make sense?
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [DISCUSS] Move some modules around

[Willem Jiang <wi...@gmail.com>]

+1 for the change.
There are some OSGi tests which are based on pax-exam in 
camel/trunk/tests/camel-itest-osgi can be took as an example.

On 9/28/11 3:45 AM, Daniel Kulp wrote:
>
> I'd like to move some modules around in the src tree.   Basically, we've been
> hanging some stuff off of modules in distribution that really are no longer
> tied completely to the distribution.  In particular, a lot of the stuff in
> there is actually more important for OSGi than for the actual CXF
> distribution.    The karaf stuff, for example, really has nothing to do with
> the distribution at all.
>
> I'd like to create a top level /osgi directory.   In there, we'd move the
> distribution/karaf and distribution/bundles directories.   Eventually, we
> could create an "/osgi/tests" or something that could include specific OSGi
> related tests. (pax-exam based maybe?)    I don't think the artifact/group
> id's of anything needs to change.  Just the parent location entries in the
> poms.
>
> Is everyone OK with that?  Does it make sense?
>


-- 
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
          http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang

Re: [DISCUSS] Move some modules around

[Freeman Fang <fr...@gmail.com>]

+1

Freeman
On 2011-9-28, at 上午3:45, Daniel Kulp wrote:

>
> I'd like to move some modules around in the src tree.   Basically,  
> we've been
> hanging some stuff off of modules in distribution that really are no  
> longer
> tied completely to the distribution.  In particular, a lot of the  
> stuff in
> there is actually more important for OSGi than for the actual CXF
> distribution.    The karaf stuff, for example, really has nothing to  
> do with
> the distribution at all.
>
> I'd like to create a top level /osgi directory.   In there, we'd  
> move the
> distribution/karaf and distribution/bundles directories.    
> Eventually, we
> could create an "/osgi/tests" or something that could include  
> specific OSGi
> related tests. (pax-exam based maybe?)    I don't think the artifact/ 
> group
> id's of anything needs to change.  Just the parent location entries  
> in the
> poms.
>
> Is everyone OK with that?  Does it make sense?
>
> -- 
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
> Talend - http://www.talend.com

---------------------------------------------
Freeman Fang

FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com