Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B739ECE1E for ; Tue, 5 Jun 2012 12:29:26 +0000 (UTC) Received: (qmail 20555 invoked by uid 500); 5 Jun 2012 12:29:26 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 20226 invoked by uid 500); 5 Jun 2012 12:29:24 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 20182 invoked by uid 99); 5 Jun 2012 12:29:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2012 12:29:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 60E8614001F for ; Tue, 5 Jun 2012 12:29:23 +0000 (UTC) Date: Tue, 5 Jun 2012 12:29:22 +0000 (UTC) From: "Christofer Dutz (JIRA)" To: flex-dev@incubator.apache.org Message-ID: <1627020829.39240.1338899363399.JavaMail.jiratomcat@issues-vm> In-Reply-To: <292360662.1710.1334771920166.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (FLEX-48) Building the SDK with Java 7 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLEX-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289368#comment-13289368 ] Christofer Dutz commented on FLEX-48: ------------------------------------- I was just working on Flexmojos to support JDK 1.7 and stumbled over a problem with the Air ApplicationPackager ... I know that this is not really related to "building" the SDK with 1.7 but in "using" it with 1.7, but I thought my report should fit here: As soon as I am using the ApplicationPackager with JDK 1.7 I am getting the following exception: Caused by: com.adobe.pki.TimestampException: Could not generate timestamp: handshake alert: unrecognized_name at com.adobe.ucf.UCFSigner.getTimeStampFromURL(UCFSigner.java:381) at com.adobe.ucf.UCFSigner.computeSignatureTimestamp(UCFSigner.java:343) at com.adobe.ucf.UCFSigner.createTimestampXML(UCFSigner.java:297) at com.adobe.ucf.UCFSigner.getSignatureXML(UCFSigner.java:177) at com.adobe.ucf.UCFOutputStream.finalizeSig(UCFOutputStream.java:343) at com.adobe.air.AIROutputStream.finalizeSig(AIROutputStream.java:157) at com.adobe.air.ApplicationPackager.createPackage(ApplicationPackager.java:87) at net.flexmojos.oss.plugin.air.packager.FlexmojosAIRPackager.createPackage(FlexmojosAIRPackager.java:59) at net.flexmojos.oss.plugin.air.SignAirMojo.doPackage(SignAirMojo.java:327) ... 26 more I guess it would be good to add UCFSigner to the list of potentially non-1.7-compilant components. > Building the SDK with Java 7 > ---------------------------- > > Key: FLEX-48 > URL: https://issues.apache.org/jira/browse/FLEX-48 > Project: Apache Flex > Issue Type: Improvement > Reporter: Christophe Herreman > Assignee: Bertrand Delacretaz > Attachments: ImageCacher.patch, SpriteTranscoder.patch, downloads.patch, java-7.patch, modules-build.xml.patch, modules-compiler-build.xml.patch, modules-thirdparty-batik-build.xml.patch > > > I've changed the SDK a bit to be able to build it with Java 7. Everything seems to compile, although that is no guarantee that things will actually work. > The main problem is the Batik dependency. The version used by the trunk version is 1.6. When building with Java 7, this results in some compiler errors for classes in the com.sun.* packages. So I've updated the build scripts to use Batik version 1.7 (there is an option to NOT use the Sun classes in the build file of that version) and resolved some more compilation issues (missing dependency xml-apis-ext.jar, API changes in the dependencies). > Attached is a patch with the changes. Please try this out if you have a moment and let me know if this works for you. These changes are compatible with Java 6, so when applying the patch you should still be able to build the SDK without changing your Java installation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira