OK, trying to close this down. Nobody objected to the plan to defer
announcing Installer 3.0 and switching the config.xml until 4.12.1 comes
out, so that's the plan I'm working towards.
The vote has been open a while. I'm ready to add my vote and send results
but first:
1) I still can't repro: "Error: Inconsistant linkage in
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/libs/air/airg
lobal.swc(flash.utils:ByteArray, flash.utils:CompressionAlgorithm,
flash.utils:IDataInput2, flash.utils:IDataOutput2),
'flash.utils:ByteArray' is marked as extern, but 'flash.utils:IDataInput2'
is not"
Justin: can you provide more explicit steps to reproduce?
I tried "Change FLEX_HOME to point to a 4.12 SDK, (that's been set up with
AIR
4.0) and try run ant in ant_for_air directory." but that worked correctly
for me.
What is AIR_HOME pointing to? In the
vote thread you mentioned someone about the "Latest SDK" and "Latest
develop branch" so I'm not sure how those factor in.
2) Since we have agreed to defer the announcement and config switch,
Justin, do you wish to change your vote before the final tally?
Thanks,
-Alex
On 3/16/14 8:45 PM, "Alex Harui" <aha...@adobe.com> wrote:
>
>
>On 3/16/14 7:56 AM, "Maurice Amsellem" <maurice.amsel...@systar.com>
>wrote:
>
>>>Please try it yourself.
>>Ok, but I couldn't find in this thread a detaild description of the
>>issue. Could you please point me to the exact mail, and if none, describe
>>what needs to be tested.
>Use the RC7 to install 4.12. Then compile as many of your existing
>projects as you have time for, and maybe try creating a new project.
>You'll get a compile error about missing a locale.
>>
>>> I have to defer to the non-en_US folks on these matters. One question:
>>>do all of your projects set the locale chain explicitly? If so, >then I
>>>think this issue does not affect you. I think it will only affect you
>>>if you have projects that do not have locales for your country that you
>>>built >relying on the default SDK locale being set to en_US. Erik, for
>>>example, is doing work for a US-based company and may get caught
>>>building some >library if it only has en_US resources and does not
>>>explicitly set en_US in the build script or project properties.
>>
>>Usually, we set en_US as a fallback locale on all our projects compiler
>>options, along with the other supported locales (en_GB, fr_FR, es_SP,
>>etc...).
>>The localChain is then dynamically set from some external settings
>>(typically, Browser or system locale).
>>If the locale is not found, we simply fall back to en_US.
>>So if I understand you, my projects won't be affected.
>That's my expectation. Justin got ant_on_air to fail for a non-en_US
>install because that particular project only has an en_US locale but
>specifies locale/{locale} in the source-path but doesn't hardcode the
>locale to en_US. I think folks who use RC7 in a non-en_US locale and for
>some reason don't have other locales for their locale will see this kind
>of error because in the past it would find en_US instead. But I think
>most folks have specified a set of locales in the locale chain that match
>their locales.
>
>-Alex
>
