Is there any special things to do at compilation time ?
I mean I pulled the code, ant all, copied all the jars in the FlexJS SDK folder
and have the same result for the same command (print #ObjectReferenceNumber) ->
BURMAbortException sent from IJ and the same command from the comand line FDB
still works well as before.
Frédéric THOMAS
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: Re : Re: Re : Re: AW: AW: AW: [FlexJS] IntelliJ Integration
> Date: Tue, 9 Jun 2015 05:58:04 +0000
>
> OK, I checked in changes that support #ObjectReferenceNumber. Hopefully
> nothing else broke.
>
> Let me know,
> -Alex
>
> On 6/6/15, 8:08 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:
>
> >> Weird. I just tried it from my Eclipse setup and reproduced the
> >> BURMAbortException. So I’ll debug it on my end over the weekend.
> >
> >Thanks for trying and good luck with that, I'm totally lost, I also
> >verified that I receive that has been sent.
> >
> >Frédéric THOMAS
> >
> >
> >----------------------------------------
> >> From: aha...@adobe.com
> >> To: dev@flex.apache.org
> >> Subject: Re: Re : Re: Re : Re: AW: AW: AW: [FlexJS] IntelliJ Integration
> >> Date: Sat, 6 Jun 2015 14:42:38 +0000
> >>
> >>
> >>
> >> On 6/6/15, 7:35 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:
> >>
> >>>> I assume you can reproduce that from the command-line as well?
> >>>
> >>>Damn, I tried it thru the intellij dev tool to talk directly to the
> >>>debugger and had the same failure, the same command in FDB works !! I'm
> >>>even more lost, the same command sent to our legacy FDB thru this same
> >>>IJ
> >>>tool works too.
> >>
> >> Weird. I just tried it from my Eclipse setup and reproduced the
> >> BURMAbortException. So I’ll debug it on my end over the weekend.
> >>
> >> -Alex
> >>
> >
>
