Re: [FlexJS] Package name for mx.states.*

2014-11-25 Thread Alex Harui
On 11/25/14, 2:41 PM, "OmPrakash Muppirala" wrote: > >> I’m not sure if the hooks from FB are that low level. I can >> try it myself if you want. Did you make sure that FlexJS and not >>regular >> Flex is compiling the code? Is it using a FlexJS flex-config? Also, >>did >> you restart FB?

Re: [FlexJS] Package name for mx.states.*

2014-11-25 Thread OmPrakash Muppirala
> > >Yes, I have been using FB all this while with no issues. But it looks > >like FlexJSUI's mx.states has started deviating from the Flex SDK version. > >Which is manifesting as a problem now. > > In theory it should be ok to deviate from the API surface of the current > Flex SDK. Of course,

Re: [FlexJS] Package name for mx.states.*

2014-11-25 Thread Alex Harui
On 11/25/14, 11:02 AM, "OmPrakash Muppirala" wrote: >On Nov 25, 2014 10:56 AM, "Alex Harui" wrote: >> >> >> >> On 11/25/14, 10:45 AM, "OmPrakash Muppirala" >>wrote: >> >> >The mx.states package in FlexJSUI is causing a collision with the Flex >> >SDK's mx.states package. Is there a reason wh

Re: [FlexJS] Package name for mx.states.*

2014-11-25 Thread OmPrakash Muppirala
On Nov 25, 2014 10:56 AM, "Alex Harui" wrote: > > > > On 11/25/14, 10:45 AM, "OmPrakash Muppirala" wrote: > > >The mx.states package in FlexJSUI is causing a collision with the Flex > >SDK's mx.states package. Is there a reason why they have the same package > >names. > > I was previously unable

Re: [FlexJS] Package name for mx.states.*

2014-11-25 Thread Alex Harui
On 11/25/14, 10:45 AM, "OmPrakash Muppirala" wrote: >The mx.states package in FlexJSUI is causing a collision with the Flex >SDK's mx.states package. Is there a reason why they have the same package >names. I was previously unable to get FB to recognize a FlexJS SDK as a Flex SDK (needed to g

Re: [FlexJS] Package name for mx.states.*

2014-11-25 Thread OmPrakash Muppirala
> > I moved FlexJS up in the dependency list in the build path. I meant: I moved FlexJSUI up in the dependency list in the build path. On Tue, Nov 25, 2014 at 10:45 AM, OmPrakash Muppirala wrote: > The mx.states package in FlexJSUI is causing a collision with the Flex > SDK's mx.states package

[FlexJS] Package name for mx.states.*

2014-11-25 Thread OmPrakash Muppirala
The mx.states package in FlexJSUI is causing a collision with the Flex SDK's mx.states package. Is there a reason why they have the same package names. Why not org.apache.flex.states instead? Is there a way to tell FB to use FlexJSUI's mx.states.* instead of the Flex SDK's? Here is what I tried