flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J. Terry Corbet (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLEX-33633) Compiler fails to transcode embedded fonts
Date Thu, 25 Jul 2013 07:55:52 GMT

     [ https://issues.apache.org/jira/browse/FLEX-33633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

J. Terry Corbet closed FLEX-33633.

    Resolution: Cannot Reproduce

This was possibly a user cockpit error.  The download/installation, which apparently ran successfully,
was yet missing some jar files in the lib directory.  Upon re-down-loading/re-installing,
now three days later, with ostensibly the same set of options, there are additional files
in lib -- 37 today, versus 32 over the weekend.  Now the application successfully compiles
and executes the same as between Adobe Flex 4.6 layered with AIR 3.8 and Apache Flex similarly

I note that the air-config.xml file also, in the latest version, no longer requires the manual
intervention (AIR_HOME) as was required three days ago -- good fix.
> Compiler fails to transcode embedded fonts
> ------------------------------------------
>                 Key: FLEX-33633
>                 URL: https://issues.apache.org/jira/browse/FLEX-33633
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Embedded Fonts
>    Affects Versions: Apache Flex 4.10.0
>         Environment: Windows XP
>            Reporter: J. Terry Corbet
>            Priority: Blocker
> Existing AIR application with embedded fonts compiles properly with Flex 4.6 SDK but
fails with Apache 4.10.0.
> Apache air-config.xml is identical between the two environments, but when I look at the
contents of the two lib directories there seem to be a lot of font-related jar files missing.
 The ones from batik seem suspiciously absent, but a diff of the Apache lib and Flex lib directories
ought to be an easy way to compare for critical dependencies.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message