true. Also, setting tsa none will not use a timestamp at all which
will cause issues once the cerificate used for signing is expired and
you want to update the AIR application.
I mixed that up with a similar error message I had during signing so
it actually really is a JVM / runtime issue as the b
ovira
Gesendet: Dienstag, 5. Juni 2012 15:05
An: flex-dev@incubator.apache.org
Betreff: Re: [jira] [Commented] (FLEX-48) Building the SDK with Java 7
hav you tried to use "-tsa none" (I think this was the setting to not use the
timestamp)
2012/6/5 Dirk Eismann
> Hey,
>
> FYI, t
hav you tried to use "-tsa none" (I think this was the setting to not use
the timestamp)
2012/6/5 Dirk Eismann
> 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 someti
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
[
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
[
https://issues.apache.org/jira/browse/FLEX-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257203#comment-13257203
]
Christophe Herreman commented on FLEX-48:
-
The upgrade involved quite a few steps. On
[
https://issues.apache.org/jira/browse/FLEX-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257123#comment-13257123
]
Martin Heidegger commented on FLEX-48:
--
I patched the sources, now it mentions something
