Well for one of my dev machines, we've removed all the source, build files,
property files, samples, and templates out of the folders. Multiple SDK's
stored in a shared parent folder. The sdk folders are labeled things like
"Flex 4.14.1" / "Flex 4.13.0" / "Flex 4.6.0". I have them setup in FD so if I
need to change the SDK used in a project I can simply select it out of a drop
down in the project properties.
If I need to debug the SDK, I would grab the latest SDK source from
development and have it as a project separately. If the problem doesn't exist
there, it may be time to update to the latest SDK. If it still exists, then
add a patch to the develop branch and put a workaround / monkey patch the
current project.
It's harder for us to just recompile the current sdk with changes, since
that would change the RSLs and also affect our shared modules in use.
-Mark
-----Original Message-----
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Monday, November 16, 2015 11:14 AM
To: dev@flex.apache.org
Subject: Re: Those @#*$^ Environment Variables
On 11/16/15, 5:23 AM, "Kessler CTR Mark J" <mark.kessler....@usmc.mil>
wrote:
>
> One my ideas for improvement would be to change the way we do binary
>packages. The strip out everything from the binary package except the
>bare bones of what is required. So just keep it the libraries, asdocs,
>licenses, notices and such. Keeping the source 100% separate since the
>binaries are not official anyways. This would allow us to have a
>smaller, less cluttered structure. Would make it easier to have folders
>with multiple version of the SDK binaries available as well.
Can you provide another level of detail as to what you mean? What would
you kick out of the binary package? We’ve always shipped the AS source
for the SWCs so they can be used in debugging.
-Alex
