You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jason Dillon (JIRA)" <ji...@apache.org> on 2007/03/02 00:02:03 UTC

[jira] Updated: (AMQ-1185) ActiveMQ 4.1 has crept in some Java 5 APIs, which prevent it from being used on Java 1.4 JVMs

     [ https://issues.apache.org/activemq/browse/AMQ-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon updated AMQ-1185:
------------------------------

    Attachment: AMQ-1185.diff

Patch allows branches/activemq-4.1 to be built using JDK 1.4

> 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: https://issues.apache.org/activemq/browse/AMQ-1185
>             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.