flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: Installing SDK on CI enviroments
Date Mon, 12 May 2014 04:39:09 GMT
4.12 introduced installer.xml.  There are flags to shut-off the prompts.
However, it might be better if you set up your CI a bit differently.  The
purpose of the installer.xml and other scripts are to build up the Apache
Flex code into an IDE compatible SDK.  In theory, a CI server doesn't need
an IDE compatible SDK, it just needs to compile.

For licensing reasons, Apache Flex SDKs can be used outside of IDEs as
specified in the README.  You can grab the binary artifact, pre-install
the non-Apache stuff, point to it with environment variables, and you are
all set.  If you need the optional downloads (BlazeDS demoting support and
embedded font support) you can just download the required jars and place
them as needed.

Yes, it is a bit more work, but then you are no longer defeating our
attempt at making sure you understand the licensing implications.


On 5/11/14 7:45 AM, "chrismatheson" <chris@matheson.it> wrote:

>im working with TravisCI and i currently directly download the FlexSDK
>adobe and use that which works perfectly for me.
>I would like to upgrade to use the latest Apache SDK's and have run into a
>bit of a bump.
>The docs for getting the latest SDK from apache's build server say that it
>can be  done via ant
>, however i can't see permalinks for older versions (4.11 / 4.12) only for
>skipping that one for the moment, i downloaded the 4.13 SDK and ran the
>installer.xml ant task which then prompted me to agree to the licence. Im
>happy to do this but is there a way to default the answer to "y" so that
>SDK can be installed 100% by scripts ?
>any pointers would be fantastic, only just getting to grips with ant task
>runner etc.
>View this message in context:
>Sent from the Apache Flex Users mailing list archive at Nabble.com.

View raw message