Re: remove jclouds-karaf and other maintenance burdens

2019-04-08 Thread Ignasi Barrera
I totally agree with Andrew's point, but we need to be careful when deprecating this. There are projects that rely on our OSGi support (take Apache Brooklyn IIRC as an example), and we don't want to leave them orphan, at least with a clear direction and position from jclouds. The only real reason

Re: remove jclouds-karaf and other maintenance burdens

2019-04-08 Thread Jean-Baptiste Onofré
Up to you guys. An alternative would be to move jclouds-karaf as karaf subproject (like decanter, cave, etc). Thoughts ? Regards JB On 08/04/2019 22:56, Ignasi Barrera wrote: > I totally agree with Andrew's point, but we need to be careful when > deprecating this. There are projects that rely

Re: remove jclouds-karaf and other maintenance burdens

2019-04-08 Thread Francois Papon
Hi JB, I think it make sense to move it as a Karaf subproject as we started the Kloud initiative. regards, François Papon fpa...@apache.org Le 09/04/2019 à 09:24, Jean-Baptiste Onofré a écrit : > Up to you guys. > > An alternative would be to move jclouds-karaf as karaf subproject (like >