Hey, FYI, this is not necessarily a JDK / runtime problem. It could also just mean that the remote timestamp server is not accessible. IIRC there was a thread somewhere sometime ago on another mailing list about this topic and how to solve it. I will look it up.
End of the story is that the same can happen in Flash Builder as well when packaging with timestamp (happened to me quite often a few times and then worked fine since then) Dirk. 2012/6/5 Christofer Dutz (JIRA) <j...@apache.org>: > > [ > 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 > >
