On 7/22/13 4:27 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>HI,
>
>So what exactly do you think needs to be changed?
I don't think anything needs to change in Git. I think if your local
working copy reflects what is in Git and you haven't run the installer or
any of the ide scripts in that working copy, then if you build another RC
it will work. Related question: what does 'git status' show for your
working copy? Doesn't it show that frameworks/air-config.xml is modified?
I think that's another check: git status should be clean before building
an RC.
>Are the current config file and templates used for generating them
>correct?
I haven't looked closely, but they have been for all other prior RCs and
releases.
>
>Here's a list of all the config files.
>./frameworks/flex-config-template.xml
>./frameworks/flex-config.xml
>./ide/flashbuilder/config/flex-config.xml
>./frameworks/air-config.xml
>./ide/flashbuilder/config/air-config.xml
>./frameworks/airmobile-config.xml
>./ide/flashbuilder/config/airmobile-config.xml
>
>Of all these files only 2 use {airHome} - so it's certainly inconsistent.
Only frameworks/air*-config.xml should have {airHome}. The
frameworks/flex-config.* shouldn't since it doesn't get used for AIR, and
the ones in ide shouldn't because it can rely on having those files mixed
in.
>
> Also the path that do use looks like it assume that AIR is unpacked
>inside a Flex SDK.
> <path-element>{airHome}/frameworks/libs/air</path-element>
>
> Can you submit a patch/make the changes in develop to correct this.
Looks correct for me, and it worked in RC1. My AIR SDK which is external
to my working copy has that exact folder path.
I think if you can restore your working copy to reflect the state of repo
and run the scripts we'll be good to go.
I'm sorry this has been painful but again, I think we have to allow this
configuration with external AIR SDKs, even if it is mostly to satisfy
Apache guidelines.
-Alex
