You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Cooper Clauson (JIRA)" <ji...@apache.org> on 2014/08/29 00:41:10 UTC
[jira] [Issue Comment Deleted] (FLEX-34507) expected build.xml file
missing from Linux binary tarball apache-flex-sdk-4.13.0-bin.tar.gz
[ https://issues.apache.org/jira/browse/FLEX-34507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cooper Clauson updated FLEX-34507:
----------------------------------
Comment: was deleted
(was: Patch to build.xml in flex sdk with the goal that the binary release contain a build.xml in its root directory. The patch comments out a line in the build script that explicitly removes this file.
This patch has not been tested.
)
> expected build.xml file missing from Linux binary tarball apache-flex-sdk-4.13.0-bin.tar.gz
> -------------------------------------------------------------------------------------------
>
> Key: FLEX-34507
> URL: https://issues.apache.org/jira/browse/FLEX-34507
> Project: Apache Flex
> Issue Type: Bug
> Affects Versions: Apache Flex 4.13.0
> Environment: Linux
> Reporter: Cooper Clauson
> Attachments: build.xml.patch
>
>
> This page:
> http://flex.apache.org/download-binaries.html
> has a link to a binary download for Linux:
> http://www.apache.org/dyn/closer.cgi/flex/4.13.0/binaries/apache-flex-sdk-4.13.0-bin.tar.gz
> In the README instructions, the user is instructed to run "ant framework-rsls" in the untarred directory, direct quote:
> *****************************************
> Additionally, you will need to build the RSLS for the SDK before you run the
> batch files.
> cd <flex.dir>
> ant frameworks-rsls
> *******************************************
> However, there is no build.xml file in this directory.
> There is a build.xml file in the source distribution:
> http://www.apache.org/dyn/closer.cgi/flex/4.13.0/apache-flex-sdk-4.13.0-src.tar.gz
> The source distribution's build.xml file does contain a framework-rsls target. Is using this file a workaround?
--
This message was sent by Atlassian JIRA
(v6.2#6252)