It requires java8 to build the source.. .not on runtime.

We could still revisit that if needed though.

On Mon, Apr 6, 2015 at 10:37 PM, Hadrian Zbarcea <[email protected]> wrote:
> Actually I did try activemq6 too. It looks like it mandates java8, is that
> correct?
>
> I know of large deployments that still use java6 with an extended support
> contract from Oracle, btw.
>
> Cheers,
> Hadrian
>
>
> On 04/06/2015 03:58 PM, Bruce Snyder wrote:
>>
>> As I am digging into the HornetQ/ActiveMQ 6 code base I am seeing quite a
>> mix of logging in use or just simply referenced in various places. Here is
>> a list of items I have found:
>>
>> * System.out.println statements in many of the examples and tests as well
>> as several in the main code base
>> * A use of the SLF4J logger
>> * A reference to the old Log4jLogDelegateFactory
>> * A use of the Arjuna logger
>> * Some references to Log4J configs in some POMs
>>
>> Clearly these various items need to cleaned up aligned to a single logging
>> framework, not to mention appropriately documented. But this also raised
>> some really fundamental questions for me:
>>
>> * What is the advantage to using the JBoss Logging vs. SLF4J?
>> * Does JBoss Logging supply any logging providers to bind to other logging
>> frameworks?
>> * Does JBoss Logging provide parameterized logging?
>> * Where can I find some documentation on JBoss Logging (specifically how
>> it
>> works)? I'm looking everywhere and not finding anything besides the
>> HornetQ
>> logging docs (
>>
>> http://docs.jboss.org/hornetq/2.4.0.Final/docs/user-manual/html_single/index.html#logging).
>> If I can't find anything about how JBoss Logging works, clearly users will
>> be just as lost as I am at the moment.
>>
>> Can someone please help me to answer these questions?
>>
>> Bruce
>>
>



-- 
Clebert Suconic
http://community.jboss.org/people/[email protected]
http://clebertsuconic.blogspot.com

Reply via email to