Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 12047 invoked from network); 3 Mar 2007 06:07:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2007 06:07:26 -0000 Received: (qmail 92599 invoked by uid 500); 3 Mar 2007 06:07:34 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 92571 invoked by uid 500); 3 Mar 2007 06:07:34 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 92562 invoked by uid 99); 3 Mar 2007 06:07:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 22:07:34 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 22:07:24 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D6D6271433B for ; Fri, 2 Mar 2007 22:07:04 -0800 (PST) Message-ID: <4022165.1172902024877.JavaMail.jira@brutus> Date: Fri, 2 Mar 2007 22:07:04 -0800 (PST) From: "Jason Dillon (JIRA)" To: dev@activemq.apache.org 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 In-Reply-To: <22625418.1172789282830.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38649 ] Jason Dillon commented on AMQ-1185: ----------------------------------- It looks better now... though something else has popped up in the G 1.2 branch which is causing some major problems which prevent me from verifying that the current AMQ 4.1-SNAPSHOT resolves the spec compliance issues. Hopefully we'll have that sorted out soonish. :-( > 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-2.diff, AMQ-1185-activeio-retro.diff, 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.