Ahh, thanks, I much prefer the StandardEmitterMBean approach which
makes notifications a doddle.

Ian

On 22 February 2013 14:05, Justin Edelson <[email protected]> wrote:
> This is OK. Per our vote on dropping Java 5 support, you should feel free
> to update the version in the pom to 6 and commit. No per-module vote is
> required.
>
> Justin
>
>
> On Thu, Feb 21, 2013 at 4:49 PM, Ian Boston <[email protected]> wrote:
>
>> Found the problem, nothing to do with Mockito
>>
>> javax.management.StandardEmitterMBean
>>
>> was introduced in JDK 16 and contains bindings to APIs only available
>> in 1.6 or later.
>>
>> Since this is the standard way of implementing notifications I think I
>> will require JDK 1.6 in the bundle. I hope this is Ok. I can implement
>> in a compliant 1.5 way but that will require writing my own (less
>> performant) implementations of the notification APIs, which is
>> probably not a good idea.
>>
>> Ian
>>
>> On 21 February 2013 21:03, Carsten Ziegeler <[email protected]> wrote:
>> > Which java version do you use to build? OS?
>> > Where does the problem occur?
>> >
>> > I haven't seen this problem so far (OS X, Java 6) - except for the
>> > commons classloader where we did some magic with the test case and
>> > java 6.
>> >
>> > Carsten
>> >
>> > 2013/2/21 Ian Boston <[email protected]>:
>> >> Hi,
>> >> I am getting
>> >>
>> >> ERROR] Failed to execute goal
>> >> org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check (default) on
>> >> project org.apache.sling.event: Execution default of goal
>> >> org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check failed: An API
>> >> incompatibility was encountered while executing
>> >> org.codehaus.mojo:animal-sniffer-maven-plugin:1.9:check:
>> >> java.lang.NoSuchMethodError:
>> >> java.nio.CharBuffer.subSequence(II)Ljava/nio/CharBuffer;
>> >> [ERROR] -----------------------------------------------------
>> >>
>> >>
>> >> I think is due to a dependency rather (mockito) than the code since
>> >> indicating JDK 1.6 eliminated the problem. (-Dsling.java.version=6)
>> >>
>> >> Going all the way back to mockito 1.8.0 doesn't fix the issue. Has
>> >> anyone else seen the same problem ?
>> >> Ian
>> >
>> >
>> >
>> > --
>> > Carsten Ziegeler
>> > [email protected]
>>

Reply via email to