Mailing-List: contact issues-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Date: Thu, 13 Mar 2014 01:28:45 +0000 (UTC)
From: "Justin Mclean (JIRA)" <jira@apache.org>
To: issues@flex.apache.org
Message-ID: <JIRA.12700993.1394639389656.56713.1394674125873@arcas>
In-Reply-To: <JIRA.12700993.1394639389656@arcas>
References: <JIRA.12700993.1394639389656@arcas>
Subject: [jira] [Commented] (FLEX-34138) Divide Flex into several modules so
 that it can be used more widely
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Justin Mclean commented on FLEX-34138:
--------------------------------------

Maven integration is a separate project in flex-utilities and not part of the flex-sdk
https://github.com/apache/flex-utilities/tree/master/mavenizer
https://github.com/apache/flex-utilities/tree/master/maven-flex-plugin

> Divide Flex into several modules so that it can be used more widely
> -------------------------------------------------------------------
>
>                 Key: FLEX-34138
>                 URL: https://issues.apache.org/jira/browse/FLEX-34138
>             Project: Apache Flex
>          Issue Type: Wish
>            Reporter: Gary Yang
>
>  Just some thoughts, might be worth discussing more:
> Flex divided into multiple modules:
> Flex tools: 1) Mxml to AS;2)Meta process;3)Other code generation and automation; 4) Maven integration;
> Flex Data: 1) Binding and List Synchronizing; 2) 0 UI component; 3) Pure model reacting repeatable model; 
> Flex UI: 1) UI components and skinning; 2) States; 
> Serverside ---- bridge between server domain and presentation domain 1) DTO; 2) Model synchronizing;


--
This message was sent by Atlassian JIRA
(v6.2#6252)