Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Date: Thu, 8 Mar 2012 07:44:59 +0000 (UTC)
From: "Jeff Fairley (Commented) (JIRA)" <jira@apache.org>
To: flex-dev@incubator.apache.org
Message-ID: <2983066.38405.1331192699757.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <801328109.52828.1326900520179.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (FLEX-8) Make SDK build with Maven/Flexmojos and
 deploy release and snapshot artifacts to the Apache Maven repository
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FLEX-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225075#comment-13225075 ] 

Jeff Fairley commented on FLEX-8:
---------------------------------

I don't think anyone is talking about making Maven _THE_ way to build the Flex SDK. At the moment, Maven support isn't even complete, and people are already building it using Ant: https://svn.apache.org/repos/asf/incubator/flex/trunk/frameworks/README.txt. I don't think there's any reason to be concerned about getting locked into a Maven build environment.

And by the way, Oleg, since you think:
{quote}It is absolutely unusable for real-world projects. {quote}
My company is (and has been for years) deploying real-world multi-module AIR and Flex applications built 100% with Maven and FlexMojos for some of the biggest media companies in the US. We started with Flex 3.6 and are now building with 4.5.1. FlexMojos' biggest fault is the lack of thorough documentation and staffed support. I won't argue that it isn't difficult to figure out, but it _WILL_ build your app.

The reason we use Maven is because we have a Java backend. I've experienced the world of building a Java WAR using Ant, and it's a dependency management nightmare. It means tracking down 40-50 (no, I'm not exaggerating) of the correct versions of different JARs and storing them along with your project. Building Flex with Ant is relatively simple since you practically depend only on the SDK and maybe a few third-party component libs. For enterprise Java backend dependency management, Maven is a godsend. And for me, that's very much reason enough to figure out how to configure Maven to build my Flex UI.

Still, I'm not saying Maven is better than Gradle. I know nothing about Gradle. But with or without Apache Flex support, I have no compelling reason to spend time switching away from Maven, when it already works great -- and this is coming from a relatively small and agile company -- so Maven is where I will stay.

-- For those who know and love Ant, and are finding it difficult to do everything you want with Maven, try the Maven Ant plugin for a hybrid approach. http://maven.apache.org/plugins/maven-antrun-plugin/
                
> Make SDK build with Maven/Flexmojos and deploy release and snapshot artifacts to the Apache Maven repository
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-8
>                 URL: https://issues.apache.org/jira/browse/FLEX-8
>             Project: Apache Flex
>          Issue Type: Story
>            Reporter: Espen Skogen
>            Assignee: Espen Skogen
>          Time Spent: 2h
>  Remaining Estimate: 0h
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira