Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Arnoud Bos <arnoud@artim-interactive.nl>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-21--66882044
Subject: Re: Which build tool to build the Apache Flex SDK(was: Ant vs. Maven
 vs. Gradle)
Date: Tue, 28 Feb 2012 12:13:56 +0100
In-Reply-To: 
 <CAH=GR+FnZPKrn=_O5sqvWUo8BDOirV=0EUhYg28agGnz5jQ-_A@mail.gmail.com>
To: flex-dev@incubator.apache.org
References: 
 <CAH=GR+FnZPKrn=_O5sqvWUo8BDOirV=0EUhYg28agGnz5jQ-_A@mail.gmail.com>
Message-Id: <9150B7B0-6F57-458E-B5F1-806B29B61460@artim-interactive.nl>

--Apple-Mail-21--66882044
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Can't we stick with ant and deploy the resulting=20
artefacts (.swc etc) with maven ant plugin in a public maven repo?

Seems that people want the sdk available via maven that doesn't mean it =
has to be build by maven itself

On Feb 28, 2012, at 12:03 PM, Yennick Trevels wrote:

> I'm splitting up the previous thread because there was imo too much
> confusion between which build tool to use for the Flex SDK and which =
build
> tools we should support (aka create artifacts for). These are two =
totally
> different discussions.
>=20
> This thread can be used to discuss which build tool we should use to =
build
> to Flex SDK.


--Apple-Mail-21--66882044--