Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Sender: Christian Schneider <cschneider111@gmail.com>
Subject: Re: [Discuss] Providing typical felix dependencies as a pom
To: dev@felix.apache.org
References: <57861182.2010300@die-schneider.net>
 <57872542.4010107@nanthrax.net> <5787524B.9010809@die-schneider.net>
 <57877DC2.5010800@nanthrax.net> <57878A64.5040301@die-schneider.net>
 <57878AB6.4060506@nanthrax.net> <57878BB1.1000005@die-schneider.net>
 <57878C77.9020604@nanthrax.net>
From: Christian Schneider <chris@die-schneider.net>
Message-ID: <57878DCF.7000604@die-schneider.net>
Date: Thu, 14 Jul 2016 15:04:15 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <57878C77.9020604@nanthrax.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
archived-at: Thu, 14 Jul 2016 13:04:25 -0000

Yes. That is the reason why I propose to adapt and release the bom about 
every 6 months to catch up with the changes.
Of course we can choose any time interval.

I would volunteer to provide the initial pom and also do the regular 
updates if no one else does it.

Christian

On 14.07.2016 14:58, Jean-Baptiste Onofré wrote:
>
> I'm still puzzled where to define such BoM.
> In Karaf, we already do the validation of the versions all together 
> (that's one of the Karaf purpose). So, it's the most straight forward 
> way.
> In Felix, as we provide each dependency individually, we have to 
> remember to update and provide the BoM.
>
> Regards
> JB
>
>


-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com