flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Mclean (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLEX-14630) Flex-SDK cannot be built entirely from source
Date Sun, 28 Apr 2013 05:04:15 GMT

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

Justin Mclean resolved FLEX-14630.

    Resolution: Fixed

Apache Flex provides source code for modified version of bartik, velocity, etc
> Flex-SDK cannot be built entirely from source
> ---------------------------------------------
>                 Key: FLEX-14630
>                 URL: https://issues.apache.org/jira/browse/FLEX-14630
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: .Unspecified - Compiler
>    Affects Versions: Adobe Flex SDK Previous
>         Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>            Reporter: Adobe JIRA
> Steps to reproduce:
> 1. Download the Flex SDK source code
> 2. Delete all binary files
> 3. Download and install all dependencies
> 4. Attempt to build the SDK 
>  Actual Results:
>         The SDK will not build because the code relies on a number of binaries that no
source is provided for.  Adobe bundles modified jars of batik ( http://www.adobeforums.com/webx/.59b4ec04
) and velocity ( http://www.adobeforums.com/webx/.59b4ebf6 ) that are required for compilation
and can be found nowhere else.  The sdk will build without Adobe's patched version of xerces
( also bundled ), but then mxmlc and fdb will report incorrect line numbers.  Bundled binaries
of avmplus are also required for asdoc, but that source may be available as part of the tamarin
>  Expected Results:
>         Flex-sdk should be fully open-source.
>  Workaround (if any):
>         Use Adobe's provided binaries, or write a lot of code.

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