Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <DB5PR05MB12858EFE6A964F21476D54C9A24B0@DB5PR05MB1285.eurprd05.prod.outlook.com>
References: 
 <DB5PR05MB12858EFE6A964F21476D54C9A24B0@DB5PR05MB1285.eurprd05.prod.outlook.com>
Date: Fri, 2 Oct 2015 08:59:32 -0700
Message-ID: 
 <CADZSWG7c=2jyf6CRCvSW0Za3cZqSHS9siCGMVvW1vXDRo9+hWw@mail.gmail.com>
Subject: Re: [ENQUIRY] Some general feedback on our build system
From: Josh Tynjala <joshtynjala@gmail.com>
To: dev@flex.apache.org
Content-Type: multipart/alternative; boundary=001a11455e92e44afd0521213f10

--001a11455e92e44afd0521213f10
Content-Type: text/plain; charset=UTF-8

> Q1: Have you ever built flex-sdk, flex-falcon, flex-asjs, ...?

Yes.

> Q2: Did you have any problems with this?

I found that binaries of flex-sdk are easy to build. Just set up some
required variables in env.properties and run the binary-release target.

I've never properly finished a binary release build of flex-falcon or
flex-asjs. Something always seems to fail. I can usually get the JX
compiler JARs to build, so I end up copying them into a nightly to test my
changes.

> Q3: If you were having problems, would making this easier make you
contribute (more)?

It would certainly make me more confident in my contributions. An older
nightly may have slight differences compared to the latest code. I would
prefer to do a full build and test it standalone.

> Q4: Do you think it is important to have the latest development version
available as binaries (via Installer and Maven)?

I don't use Maven.

I don't doubt developers will want to try out nightlies from the installer
as FlexJS becomes more popular.

- Josh

--001a11455e92e44afd0521213f10--