Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Date: Mon, 27 Feb 2012 22:29:49 +0000 (UTC)
From: "Jeff Fairley (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: flex-dev@incubator.apache.org
Message-ID: 
 <503804451.25174.1330381789041.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <801328109.52828.1326900520179.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (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=13217639#comment-13217639 ] 

Jeff Fairley edited comment on FLEX-8 at 2/27/12 10:28 PM:
-----------------------------------------------------------

I know nothing about Gradle, so this is in no way an argument against supporting it. That said, I've been using Maven for Java projects for many years and have been building all of my company's Flex projects using Maven / FlexMojos for more than a year now. In general, the larger the company, the slower they are to move on to new technologies, especially when that technology is so fundamental as a build tool. Supporting something like Gradle before supporting Maven sounds like a move that would alienate many existing users who already have a handle on Maven and aren't interested in moving or don't have time to move to Gradle or some similar alternative. Whether or not Gradle support comes eventually, official Maven support within Apache Flex is a good move for the future of the project overall in that it will make things easier for a large set of existing users.

Personally, official Maven support is the one thing I'm most looking forward to with the transition to Apache. Velo has done a great job with FlexMojos, but it's way more than one man can handle. I would love to see that code adopted, maintained, and improved by the growing Apache Flex community.
                
      was (Author: jfairley):
    I know nothing about Gradle, this is in no way an argument against supporting it. That said, I've been using Maven for Java projects for many years and have been building all of my company's Flex projects using Maven / FlexMojos for more than a year now. In general, the larger the company, the slower they are to move on to new technologies, especially when that technology is so fundamental as a build tool. Supporting something like Gradle before supporting Maven sounds like a move that would alienate many existing users who already have a handle on Maven and aren't interested in moving or don't have time to move to Gradle or some similar alternative. Whether or not Gradle support comes eventually, official Maven support within Apache Flex is a good move for the future of the project overall in that it will make things easier for a large set of existing users.

Personally, official Maven support is the one thing I'm most looking forward to with the transition to Apache. Velo has done a great job with FlexMojos, but it's way more than one man can handle. I would love to see that code adopted, maintained, and improved by the growing Apache Flex community.
                  
> 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