If you don't get errors in the output for compiling the Date tests without the
Flash variables, that implies that an older compiler is running. The latest
should be picking up the field-readonly and result in those compile errors in
the console output, but since the compile errors are expected that should not
result in a failure. The failure might be something else like some sensitivity
to your time zone. So check the junit-reports file and see what it says failed
if you can reproduce it.
Same for typedefs. It seems like you aren't running the latest compiler. Are
you just running "ant" from royale-typedefs? Maybe it is picking up the jars
from royale-asjs that haven't been updated yet. You can add some <echo>
statements to the js/build.xml and see what ROYALE_TRANSPILER_HOME is
calculated to be.
HTH,
-Alex
On 7/25/18, 11:12 PM, "Harbs" <harbs.li...@gmail.com> wrote:
> On Jul 26, 2018, at 2:55 AM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>
> I took a closer look. If you are getting ASDateTest failures, you will
need to open compiler/target/junit-reports/TEST-as.ASDateTests.xml and see what
the failure is. The compile errors in the output are expected and should not
cause test failures.
I’ll try to look at this again. I was only getting the errors when I
compile with the Flash environment variables.
> If you are having a problem with field-readonly, it implies that the
compiler you are using is stale.
compiler-externc/src/main/java/org/apache/royale/compiler/clients/ExternCConfiguration.java
should contain an entry for field-readonly.
My source does contain the entry. That’s what’s really weird. I confirmed
that externs was wiped and regenerated when I compile. Is there some file I
might be missing?
>
> HTH,
> -Alex
>
> On 7/25/18, 12:52 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>
> I rolled back royale-typedefs to before the Date changes to enable my
compilation. It does seem to me like we need to figure this out though…
>
> Harbs
>
>> On Jul 25, 2018, at 9:59 AM, Harbs <harbs.li...@gmail.com> wrote:
>>
>> I tried without environment vars and that might have made a difference.
I’ using these normally:
>>
>> export ROYALE_COMPILER_REPO=/Apache/royale-compiler
>> export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler
>> export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player
>> export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\
Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
>> export ROYALE_HOME=/Apache/royale-asjs
>>
>> I’m now getting field-readonly error again… :-(
>>
>>> On Jul 25, 2018, at 9:52 AM, Harbs <harbs.li...@gmail.com> wrote:
>>>
>>> Weird. I ran ant all again and it’s no longer getting this error, but
it’s failing again on the Date tests (4 failures).
>>>
>>>> On Jul 25, 2018, at 9:43 AM, Harbs <harbs.li...@gmail.com
<mailto:harbs.li...@gmail.com>> wrote:
>>>>
>>>> Yes I did, but it looks like that does not clear the files in the
typedefs repo.
>>>>
>>>> I just manually deleted all the target folders in typedefs and now I’m
getting a new error:
>>>>
>>>> externc:
>>>> [java] Unknown tag:field-readonly
>>>> [java] 0.362347459 seconds
>>>> [java]
org.apache.royale.compiler.exceptions.ConfigurationException.UnknownVariable[var='field-readonly',
line='178',
source='/Apache/royale-typedefs/js/src/main/config/externc-config.xml'].
>>>> [java]
/Apache/royale-typedefs/js/src/main/config/externc-config.xml (line: 178)
>>>>
>>>> Where is field-readonly supposed to be defined?
>>>>
>>>>> On Jul 24, 2018, at 8:58 PM, Alex Harui <aha...@adobe.com.INVALID
<mailto:aha...@adobe.com.INVALID>> wrote:
>>>>>
>>>>> Did you run "ant wipe-all" in royale-compiler?
>>>>>
>>>>> On 7/24/18, 10:47 AM, "Harbs" <harbs.li...@gmail.com
<mailto:harbs.li...@gmail.com>> wrote:
>>>>>
>>>>> I’m currently getting the following errors:
>>>>>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F3Wpg&data=02%7C01%7Caharui%40adobe.com%7Cae7cd23df8204531b26108d5f18d8d46%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636680512616417047&sdata=SjmjSTlfL3tBEAHR7o%2FEx4akD7LhTx0QQqk3w1Bkt%2F0%3D&reserved=0
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F3Wpg&data=02%7C01%7Caharui%40adobe.com%7Cae7cd23df8204531b26108d5f18d8d46%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636680512616417047&sdata=SjmjSTlfL3tBEAHR7o%2FEx4akD7LhTx0QQqk3w1Bkt%2F0%3D&reserved=0>
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F3Wpg&data=02%7C01%7Caharui%40adobe.com%7Cae7cd23df8204531b26108d5f18d8d46%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636680512616417047&sdata=SjmjSTlfL3tBEAHR7o%2FEx4akD7LhTx0QQqk3w1Bkt%2F0%3D&reserved=0
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F3Wpg&data=02%7C01%7Caharui%40adobe.com%7Cae7cd23df8204531b26108d5f18d8d46%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636680512616417047&sdata=SjmjSTlfL3tBEAHR7o%2FEx4akD7LhTx0QQqk3w1Bkt%2F0%3D&reserved=0>>
>>>>>
>>>>> It looks like the Date tests are causing problems. Any ideas why?
>>>>>
>>>>> Harbs
>>>>>
>>>>
>>>
>>
>
>
>
