> > > >> >> wrote:
> > > > >> >>
> > > > >> >>> What error do you get if you don't apply the
> workaround?
> > > > >> >>>
> > &g
> > >> >>> >This is still an issue, and the workaround below is
> required
> > for me
> > > >> >>>to be
> > > >> >>> >able to run 'ant' on the royale-asjs pr
> > >> >>>
> > > >> >>> >Just to keep this fresh:
> > > >> >>> >
> > > >> >>> >This is still an issue, and the workaround below is
> required
> &
t; >> >>>to be
> > >> >>> >able to run 'ant' on the royale-asjs project...
> > >> >>> >
> > >> >>> >EdB
> > >> >>> >
> > >> >>> >
> > >> >>> >
> > >> >>>
to run 'ant' on the royale-asjs project...
> > >> >>> >
> > >> >>> >EdB
> > >> >>> >
> > >> >>> >
> > >> >>> >
> > >> >>> >On Thu, Nov 16, 20
;>> >
> >> >>> >> I did several fresh pulls of the repos yesterday while testing
> >> >>>as2wasm
> >> >>> >>and
> >> >>> >> I can faithfully reproduce the issue(s). I can also reliably
make
> >&
;>> >able to run 'ant' on the royale-asjs project...
> >> >>> >
> >> >>> >EdB
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >On Thu, Nov 16, 2017 at 8:01 AM, Erik de Bruin >
> >> >>> wrote:
> >> >>> >
> >> >>>
gt; >>>as2wasm
>> >>> >>and
>> >>> >> I can faithfully reproduce the issue(s). I can also reliably make
>> >>>it go
>> >>> >> away if I do these things:
>> >>> >>
>> >>> >&g
duce the issue(s). I can also reliably make
> >>>it go
> >>> >> away if I do these things:
> >>> >>
> >>> >> - comment out the ant task in the 'CoreTest' target in
> >>> >>frameworks/build.xml
> >>> >> - remove th
;> >>
>>> >> EdB
>>> >>
>>> >>
>>> >>
>>> >> On Thu, Nov 16, 2017 at 7:43 AM, Yishay Weiss
>>><yishayj...@hotmail.com>
>>> >> wrote:
>>> >>
>>> >>> Thanks for t
it after
>> >>>playing
>> >>> around with some scripts, cleaning my changes and checking out from
>> >>>git the
>> >>> unit tests aren’t being run anymore and so I’m not getting it. I’ll
>> >>>come
>> >>> back to it w
:
> >>
> >>> Thanks for the pointers Alex. Funnily I stopped getting it after
> >>>playing
> >>> around with some scripts, cleaning my changes and checking out from
> >>>git the
> >>> unit tests aren’t being run anymore and so I’m not g
, cleaning my changes and checking out from
>>>git the
>>> unit tests aren’t being run anymore and so I’m not getting it. I’ll
>>>come
>>> back to it when it starts itching again, but for now I can work.
>>>
>>>
>>>
>>>
>
and checking out from git the
>> unit tests aren’t being run anymore and so I’m not getting it. I’ll come
>> back to it when it starts itching again, but for now I can work.
>>
>>
>>
>>
>> From: Alex Harui <aha...@adobe.com.
017 6:41:20 PM
> To: dev@royale.apache.org
> Subject: Re: Ant Build Problem
>
> My working copies are all torn up with the refactoring and I'd prefer not
> to have to stop and build up another working copy to debug this, assuming
> I can even reproduce it.
>
> The facto
.
From: Alex Harui <aha...@adobe.com.INVALID>
Sent: Wednesday, November 15, 2017 6:41:20 PM
To: dev@royale.apache.org
Subject: Re: Ant Build Problem
My working copies are all torn up with the refactoring and I'd prefer not
to have to stop and build up another workin
;> the result is the same.
>>
>> FWIW this is ROYALE_COMPILER_HOME which appears to not resolve
>>correctly:
>> C:\dev\flexjs\royale-asjs\frameworks\projects\Core\src\test\royale>echo
>> %ROYALE_COMPILER_HOME%
>> C:\dev\flexjs\royale-asjs/js
>> Fr
/js
From: Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, November 15, 2017 12:01 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Ant Build Problem
It works for me. It looks like your ROYALE_SWF_COMPILER_HOME is pointing to a
different location than mine.
He
LER_HOME}\lib
> does not exist.
>
>
>
> ________
> From: Alex Harui <aha...@adobe.com.INVALID>
> Sent: Tuesday, November 14, 2017 8:22:01 PM
> To: dev@royale.apache.org
> Subject: Re: Ant Build Problem
>
> The FlexUnit comp
royale\${ROYALE_COMPILER_HOME}\lib
does not exist.
From: Alex Harui <aha...@adobe.com.INVALID>
Sent: Tuesday, November 14, 2017 8:22:01 PM
To: dev@royale.apache.org
Subject: Re: Ant Build Problem
The FlexUnit compile is trying to use the Ant tasks instead of dire
./../js/projects/${ant.project.name}JS
>/src/main/config/compile-js-config.xml" />
>
>
>From: Alex Harui<mailto:aha...@adobe.com.INVALID>
>Sent: Tuesday, November 14, 2017 7:35 PM
>To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>Subject: R
he.org<mailto:dev@royale.apache.org>
Subject: Re: Ant Build Problem
Even if you did, it is still pretty easy for an environment variable or
Ant property to get you to use a compiler in another folder, so keep an
eye open for that. The Ant scripts usually report what compiler folder
they are using.
I updated compiler and typedefs as well. Will have a look tomorrow.
From: Alex Harui <aha...@adobe.com.INVALID>
Sent: Tuesday, November 14, 2017 6:25:55 PM
To: dev@royale.apache.org
Subject: Re: Ant Build Problem
I haven't seen that. You are w
I haven't seen that. You are working with relatively new test code, IIRC.
Could be you are using very old compiler?
HTH,
-Alex
On 11/14/17, 3:26 AM, "Yishay Weiss" wrote:
>[mxmlc]
>C:\dev\flexjs\royale-asjs\frameworks\projects\Core\src\test\royale\flexUni
24 matches
Mail list logo