+1 to removing the code from the plugin and setting 459 to 3.0 as well.

Jamie

On Mon, Feb 14, 2011 at 12:53 PM, Andreas Pieber <[email protected]> wrote:
> +1 for removing the code from the plugin and setting 459 to 3.0
>
> kind regards,
> andreas
>
> On Mon, Feb 14, 2011 at 05:19:49PM +0100, Guillaume Nodet wrote:
>> Didn't we defer the new packaging to 3.0 ? We haven't removed the code
>> in the plugin though, maybe we should ...
>>
>> On Mon, Feb 14, 2011 at 17:10, Jamie G. <[email protected]> wrote:
>> > Hi All,
>> >
>> > Just reviewing the outstanding issues for 2.2.0, does anyone want to
>> > pick up the below issue or can I bump it up to fix for 2.2.1?
>> > https://issues.apache.org/jira/browse/KARAF-459
>> >
>> > Cheers,
>> > Jamie
>> >
>> > On Mon, Feb 14, 2011 at 9:36 AM, Jamie G. <[email protected]> wrote:
>> >> Sounds good, please let us know when all your documentation updates are 
>> >> in :)
>> >>
>> >> On Mon, Feb 14, 2011 at 4:29 AM, Jean-Baptiste Onofré <[email protected]> 
>> >> wrote:
>> >>> On my side, I'm working on:
>> >>> KARAF-433
>> >>> KARAF-437
>> >>> KARAF-435
>> >>>
>> >>> It's not blocking points (just documentation), but it could be fine to 
>> >>> have
>> >>> it in the manual for 2.2.0 release.
>> >>> I should have finished this afternoon.
>> >>>
>> >>> Regards
>> >>> JB
>> >>>
>> >>> On 02/14/2011 08:57 AM, Guillaume Nodet wrote:
>> >>>>
>> >>>> Is there anything left or should we start the release process asap ?
>> >>>>
>> >>>> On Tue, Feb 8, 2011 at 16:51, Jamie G.<[email protected]>  wrote:
>> >>>>>
>> >>>>> Hi,
>> >>>>>
>> >>>>> Thanks for all your feedback. We've fixed multiple bugs/problems on
>> >>>>> the release branch and will start building a release candidate
>> >>>>> shortly. Thanks again for all your contributions.
>> >>>>>
>> >>>>> -The Karaf Team
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>
>> >>
>> >
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>

Reply via email to