activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dillon (JIRA)" <>
Subject [jira] Commented: (AMQ-1185) ActiveMQ 4.1 has crept in some Java 5 APIs, which prevent it from being used on Java 1.4 JVMs
Date Fri, 02 Mar 2007 04:07:05 GMT


Jason Dillon commented on AMQ-1185:

Crap, crap, crap... there is a *ton* of Java 5 bits in activeio 3.1-SNAPSHOT, which ActiveMQ
is using.

I missed this before, as I was still compiling with JDK 1.5, but set the compiler to generate
1.4 classes.  But, when compiling activeio with JDK 1.4 it pukes up a bunch more stuff.

Perhaps activeio 3.1 needs to be retrotranslated so that activemq 4.1 can use -jdk14 versions
of this... pffff.

> ActiveMQ 4.1 has crept in some Java 5 APIs, which prevent it from being used on Java
1.4 JVMs
> ---------------------------------------------------------------------------------------------
>                 Key: AMQ-1185
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.1.1
>            Reporter: Jason Dillon
>            Priority: Blocker
>         Attachments: AMQ-1185.diff
> A few bits of Java 5 API has made it into the AMQ 4.1 branch, which prevent 4.1 from
being used on Java 1.4 JVMS.
> Apache Geronimo v1.2 needs AMQ 4.1 running on Java 1.4.
> So far I don't see anything major which prevents AMQ 4.1 from being compiled with Java
1.4... only a few minor changes to keep compatibility.  The alternative is of course to use
the retrotranslator-maven-plugin to generate 1.4 compatible jars for each module (the new
retrotranslator:translate-project makes this very easy to use, includes attaching jdk14 artifacts).
> But IMO, that would just add more complexity for AMQ 4.1 when only a few simple changes
will allow the it to be native 1.4... though you folks might consider using retrotranslator:translate-project
for trunk to create 1.4 compatible jars for the new AMQ (> 4.1.x) bits.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message