I would recommend we keep all the files / scripts, both Mac and Win, in the download if possible. I ran into errors and other problems when we moved the SDK to a server for continuous integration. We went from a Mac machine to a Windows server and didn't know some or all of the Windows files were not part of the Mac download.
On Mon, Dec 15, 2014 at 2:15 PM, Alex Harui <aha...@adobe.com> wrote: > > > > On 12/15/14, 12:19 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > >- Remoting Support has been removed from license check list. I assume > >this was intentional as BlazeDS will now be baked in? (but isn't yet) > > Yes it is intentional for 4.14 to not have a “Remoting Support” option, > but I think you may have forgotten what that option does. The Apache Flex > SDK Installer has never installed BlazeDS. All it does is install one of > the BlazeDS jars so that MXMLC can parse services-config.xml for folks > using it for BlazeDS and other “remoting” products. > > In 4.14, that one jar (flex-messaging-common.jar) is already baked in. At > least, I see it in my install. There are still no plans to install all of > BlazeDS at this time. > > > >- Once the SDK has been installed (on OSX) and looking in the bin > >directory adl.bat and adt.bat are missing. All other files have .bat > >files as well. While not a normally an issue it does mean that the SDK > >once installed isn't portable across OSs. > > This is not new to 4.14. AFAICT, adl.bat and adt.bat are not in the AIR > SDK for Mac. I believe some other files are missing as well. I would not > want to make folks download both Mac and Win SDKs just to get these few > files. > > -Alex > >
