Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of carlos.rovira@gmail.com
 designates 209.85.161.175 as permitted sender)
MIME-Version: 1.0
Sender: carlos.rovira@gmail.com
In-Reply-To: 
 <CANi2vadoasQ8JZFgzbW8UL_rtqy4CaYYaTUrvghY3UeH28VwPg@mail.gmail.com>
References: 
 <292360662.1710.1334771920166.JavaMail.tomcat@hel.zones.apache.org>
	<1627020829.39240.1338899363399.JavaMail.jiratomcat@issues-vm>
	<CANi2vadoasQ8JZFgzbW8UL_rtqy4CaYYaTUrvghY3UeH28VwPg@mail.gmail.com>
Date: Tue, 5 Jun 2012 15:05:06 +0200
Message-ID: 
 <CAMFKFRiB_kCJ8Mg5YUWjfaOhTFxqG7b2K6xf-eV44vefchYGUQ@mail.gmail.com>
Subject: Re: [jira] [Commented] (FLEX-48) Building the SDK with Java 7
From: Carlos Rovira <carlos.rovira@codeoscopic.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=20cf303f6e82afbbad04c1b94cca

--20cf303f6e82afbbad04c1b94cca
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hav you tried to use "-tsa none" (I think this was the setting to not use
the timestamp)

2012/6/5 Dirk Eismann <bortsen@googlemail.com>

> 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) <jira@apache.org>:
> >
> >    [
> https://issues.apache.org/jira/browse/FLEX-48?page=3Dcom.atlassian.jira.p=
lugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13289368#co=
mment-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 real=
ly
> 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:38=
1)
> >        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.patc=
h
> >>
> >>
> >> 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 wi=
ll
> actually work.
> >> The main problem is the Batik dependency. The version used by the trun=
k
> 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 t=
he
> 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 compatibl=
e
> 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
> >
> >
>


--=20
Carlos Rovira
Director de Tecnolog=EDa
M: +34 607 22 60 05
F:  +34 912 35 57 77
<http://www.codeoscopic.com>
CODEOSCOPIC S.A. <http://www.codeoscopic.com>
Avd. del General Per=F3n, 32
Planta 10, Puertas P-Q
28020 Madrid

--20cf303f6e82afbbad04c1b94cca--