aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Bosschaert <david.bosscha...@gmail.com>
Subject Re: Moving JMX-Next from the sandbox back into the main trunk
Date Wed, 14 Nov 2012 19:29:25 GMT
I have done this now. The contents of sandbox/jmx-next has been moved back
into jmx (with SVN history).
See: http://svn.apache.org/viewvc?view=revision&revision=1409307

I hope I didn't mess up things :)

Cheers,

David


On 14 November 2012 18:55, David Bosschaert <david.bosschaert@gmail.com>wrote:

> As nobody has voiced any concerns I'm going to do this soon.
> BTW thanks Felix for the +1.
>
> Best regards,
>
> David
>
>
> On 12 November 2012 15:08, Felix Meschberger <fmeschbe@adobe.com> wrote:
>
>> +1 (non binding).
>>
>> Thanks and Regards
>> Felix
>>
>> Am 12.11.2012 um 13:05 schrieb David Bosschaert:
>>
>> > Hi all,
>> >
>> > The JMX-Next code in Aries (in the sandbox/jmx-next) code base is done
>> now
>> > (as far as I can see) and I think it's ready to move back into the main
>> > codebase.
>> >
>> > JMX-Next implements the OSGi/JMX specification from the Enterprise R5
>> spec,
>> > it's actually the Reference Implementation of that spec, and as such it
>> > also passes all of the OSGi JMX CT tests. I've also pulled over changes
>> > made to the main JMX code base that were made in the mean time.
>> >
>> > Would everyone be ok with me moving it back to the main Aries codebase?
>> >
>> > Cheers,
>> >
>> > David
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message