Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Subject: Re: [Discuss] Using DS for decanter
To: dev@karaf.apache.org
References: <56B9DA14.6060006@die-schneider.net>
From: =?UTF-8?Q?Jean-Baptiste_Onofr=c3=a9?= <jb@nanthrax.net>
Message-ID: <56B9DC73.8040005@nanthrax.net>
Date: Tue, 9 Feb 2016 13:32:51 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B9DA14.6060006@die-schneider.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

+1 (as discussed ;))

Agree to use DS in 1.1.x branch that I will create just after 1.0.2 release.

Regards
JB

On 02/09/2016 01:22 PM, Christian Schneider wrote:
> I recently discussed with JB that the boilerplate code in decanter
> increases. One typical example is that a decanter module needs to
> reference EventAdmin, the Marshaller service and react on
> configurations. In many cases we also need to be able to work with
> ManagedServiceFactories.
>
> So for this case DS seems like a good idea. It can do all of the above
> with very simple annotations  and can now also do type safe configs.
>
> The only disadvantage is that we then need the scr feature. As it is
> quite small I think this is a good tradeoff.
>
> What do you think?
>
> If there is no push back then I would like to switch decanter to DS once
> the decanter release 1.0.2 is done. JB then wants to switch the master
> to 1.1.x which allows us to do some more changes then in a bugfix line.
>
> Christian
>

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