Ok, thanks Alex. I will not do that then. I did not prefix the names with 'feature' anyway... I will push to 'amf_updates' branch for compiler and asjs inside the next couple of hours. I have more to do on this work, but it's moving forward - dynamic and IExternalizable are now supported, although I have not tested the short messaging stuff yet. I updated mxroyale\RemoteObjectAMFTest to use mxArrayCollection and that is working.
But there will be some things to discuss (will follow up on list tomorrow) and I still have a few more things queued up to work on with AMFBinaryData (IDynamicPropertyWriter, XML, Vectors - I did not test/check these yet, and perhaps something for Dictionary) On Fri, Mar 1, 2019 at 6:56 PM Alex Harui <[email protected]> wrote: > I haven't checked on the Maven Pipeline to see if it is operational or > not. IIRC, it was the only thing that required all 3 branches to have the > same name, and I think it had to start with feature/ or release/. For the > rest of us, it doesn't matter. You checkout the branch you want and build > it and it will end up being the code that is used. > > HTH, > -Alex > > On 2/28/19, 9:34 PM, "Greg Dove" <[email protected]> wrote: > > Hi Alex - or anyone else who knows - for setting up a compilable > branch, am > I supposed to commit to the same branch name in all three of : as-js, > typedefs and compiler ? I have only changes in asjs and compiler. But > I can > create a same name branch in typedefs as well if that is required.... > > Thanks, > Greg > > >
