Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <4648D734.9060606@ungoverned.org>
Date: Mon, 14 May 2007 17:40:04 -0400
From: "Richard S. Hall" <heavy@ungoverned.org>
User-Agent: Thunderbird 2.0.0.0 (X11/20070419)
MIME-Version: 1.0
To: dev@felix.apache.org
Subject: Re: Support for Fragment Bundles
References: <4648a79f.5f3eac67.7a31.26ab@mx.google.com>
 <4648A9C9.9030306@ungoverned.org>
 <9A6213D6CEDE5147A5FA6559410C363D01E07272@Mail1.ktd.com>
 <4648D3CA.1070802@ungoverned.org>
 <9A6213D6CEDE5147A5FA6559410C363D01E07291@Mail1.ktd.com>
In-Reply-To: <9A6213D6CEDE5147A5FA6559410C363D01E07291@Mail1.ktd.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Rick Litton wrote:
> Glad to know that there IS such a plan. I would like to assist just in
> case you need any help.

Well, the plan is to be R4 compliant...probably R4.1 now...but the path 
to hell is paved with good intentions... ;-)

> BTW, that generic capability/requirement
> model... was it implemented in require-bundle or OBR?  It sounds similar
> to what I've implemented at work to customize OBR in order to
> "recognize" locally installed bundles. 
>   

It was implemented in require-bundle using the concepts defined for OBR2...

-> richard
> Rick Litton
>
> -----Original Message-----
> From: Richard S. Hall [mailto:heavy@ungoverned.org] 
> Sent: Monday, May 14, 2007 2:26 PM
> To: dev@felix.apache.org
> Subject: Re: Support for Fragment Bundles
>
> Rick Litton wrote:
>   
>> Is there any plan to support fragment bundles (3.14 of R4) soon in
>> Felix?  I noticed that an issue has been opened -- FELIX-29 -- but no
>> work seems to have been done on it yet.  Is there any reason or
>>     
> concern
>   
>> why it is being postponed?  Thanks.
>>     
>
> There is a plan, just need to find the time...
>
> The work on adding support for require-bundle was essentially a 
> preliminary step for fragments too, since we added a generic 
> capability/requirement model, which will hopefully be useful for 
> fragment dependencies too.
>
> I doubt this will happen "soon" since it is probably the most 
> complicated feature of all those yet implemented, but it will happen. 
> First, we have to get another release out and finish off a few other 
> things yet. Stay tuned.
>
> -> richard
>