Well technically if you're just developing a patch a better would be to
monkey patch the Flex SDK.
Just create a folder structure under your source dir that matches the files
you want to patch.
For example:
MyProject
src
spark
components
TextInput.as
The compiler will pick up and use your TextInput.as because it's a file
with a newer timestamp than the one in the SDK.
On Mon, Feb 29, 2016 at 4:51 AM, XaviConde <javier.co...@gruposame.com>
wrote:
> Hi everyone,
>
> I've downloaded and built successfully flex 4.15.0 from source, following
> the steps in README (ant main, ant frameworks-rsls, ant -f installer.xml).
> From Flex Builder, I've configured the new SDK from Preferences as an
> available SDK. Then, I've selected the newly built SDK for my project, and
> tested both application and SDK successfully.
>
> Later on I've made some changes to the SDK source code, but when I try to
> run 'ant main' again, the build fails with
> 'apache-flex-sdk-4.15.0-src\modules\compiler\build.xml:171: Warning: Could
> not find file C:\...\apache-flex-sdk-4.15.0-src\in\flex-tool-api.jar to
> copy.'
>
> According to the instructions in README, in order to prepare the SDK for an
> IDE, I have to run 'ant -f installer.xml'. But when I run this step, the
> folder 'in' is removed, so I can't build the source anymore, unless I run
> 'ant super-clean main'.
>
> Is there any way to build the source from Flex Builder as a project so I
> don't have to run 'ant main super-clean' every time I change the sources?
>
> Thanks in advance!
>
>
>
> --
> View this message in context:
> http://apache-flex-development.2333347.n4.nabble.com/Developing-Flex-SDK-with-Flex-Builder-tp51743.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
