Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of rick.winscot@gmail.com
 designates 209.85.160.175 as permitted sender)
Date: Thu, 24 May 2012 15:45:33 -0400
From: Rick Winscot <rick.winscot@gmail.com>
To: flex-dev@incubator.apache.org
Message-ID: <9A9A019F03B34F7DAD28E0ADBDEDFA50@gmail.com>
In-Reply-To: 
 <CACK5iZc+beePVyvjBZbE_itKYHFMPVG_gxd0COvxep0zW1EjDw@mail.gmail.com>
References: 
 <CAMFKFRgOMM_h6Src_K3LiU60aJsbqyq7r3oGAaSvmG=eXqCtkg@mail.gmail.com>
 <CBE3B867.155F3%cframpto@adobe.com>
 <66E38C42347D6446BF7FCB22C3D3878072C87DD95B@ECCR06PUBLIC.exchange.local>
 <CAMFKFRhngiWZTa1vv+r-DbukU6ANoHQpq3N5T4d_kz8sVXcTKA@mail.gmail.com>
 <CACK5iZc+beePVyvjBZbE_itKYHFMPVG_gxd0COvxep0zW1EjDw@mail.gmail.com>
Subject: Re: Apache Flex structure to be BMS compliant (was Re: Library
 Versions used in Flex SDK)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4fbe8fdd_2c27173b_12d6b"

--4fbe8fdd_2c27173b_12d6b
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I agree with Om as well... we've resorted to driving the compiler directly via Groovy... and it's swell!

R 


On Thursday, May 24, 2012 at 2:39 PM, Om wrote:

> > 
> > 1) maintain the structure and use a tool (like you did) to transform the
> > sdk to maven compliant sdk.
> > 
> > 2) change sdk structure to get directly a maven compliant sdk
> > 
> > IMHO the best way should be 2), since now is the right time to make
> > changes. Maybe just as soon as Apache Flex 4.8 sdk will be released, right?
> > 
> > Tools should change to make Apache Flex SDK compliant.
> 
> I respectfully disagree. I think (1) is the way to go. This gives us
> (Flex SDK team) the freedom to maintain whatever structure we want. If
> some of us want to make it Maven compliant, they should write a tool to
> create a Maven-specific directory structure and maintain it either part of
> Apache Flex or outside of Apache Flex.
> 
> Maven is not the only build management system we want to support. Lots of
> folks use Ant, GradleFx, custom build scripts, etc. If we favor Maven,
> then it is not fair for the other tools.
> 
> Breaking existing tools like Flash Builder, IntelliJ just to make Maven
> work is not the best idea. We are at a very delicate point in terms of end
> users' confidence and trust. Lets not break the camel's back.
> 
> Thanks,
> Om
> 
> 


--4fbe8fdd_2c27173b_12d6b--