tldr; can't reproduce today
My download has the file already in it to.
# tar ztvf apache-flex-sdk-4.15.0-bin.tar.gz|grep flex-config.xml
-rw-r--r-- 0/0 19529 2016-01-04 00:38
apache-flex-sdk-4.15.0-bin/frameworks/flex-config.xml
-rw-r--r-- 0/0 19445 2016-01-04 00:38
apache-flex-sdk-4.15.0-bin/ide/flashbuilder/config/flex-config.xml
So then I untar that and check again:
# grep framework_ apache-flex-sdk-4.15.0-bin/frameworks/flex-config.xml
<rsl-url>framework_4.15.0.20160104.swf</rsl-url>
cd into the folder and run
# ant -f installer.xml -Dair.sdk.version=2.6
...answer yes to everything and wait a few minutes...
# grep framework_ frameworks/flex-config.xml
<rsl-url>framework_4.15.0.20160104.swf</rsl-url>
and it's there as expected.
Odd,
Tom
On 14/03/16 17:03, Alex Harui wrote:
Running individual targets in build.xml isn't guaranteed to work either.
The -config.xml handling in Ant is trying to compare what versions of
Flash and AIR the release manager used vs what you asked for. It is also
going to use a more recent date for the build number since it thinks you
are creating a release.
Let's back up to the beginning. I just ran the Ant install on my MacOSX
computer. I got the binary from one of the mirrors. Just expanding
apache-flex-sdk-4.15.0-bin-tar.gz gives me a flex-config.xml in
frameworks. Did you get one too or is it already missing?
The flex-config.xml in the package seems to be set for FP11.1. What are
you seeing before running "ant -f installer.xml"?
On 3/14/16, 9:32 AM, "Tom Chiverton" <[email protected]> wrote:
Except this has created entries in flex-config.xml for
framework_4.15.0.20160314.swf
rather than
framework_4.15.0.20160104.swf (as in the .../rsls/ folder).
But after a search and replace it's working, but I'm out of my depth
with Ant now :-)
Tom
On 14/03/16 14:57, Tom Chiverton wrote:
ant -f build.xml create-config
has created the files, but they haven't had the build numbers etc
substituted in. Running
ant -f installer.xml -Dair.sdk.version=2.6 fixup-config-files
appears to do that.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
