flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carol Frampton <cfram...@adobe.com>
Subject Re: Apache Flex structure to be BMS compliant (was Re: Library Versions used in Flex SDK)
Date Thu, 24 May 2012 14:07:21 GMT
Just be aware that if you are talking about moving directories around will
quite likely break Apache Flex working with Flash Builder and/or IntelliJ.


On 5/24/12 10 :01AM, "Carlos Rovira" <carlos.rovira@codeoscopic.com> wrote:

>>  be a good thing for the people maintaining Flex to also maintain its
>So putting the metadata into the Apache Flex SVN repo would be a good
>I understand that Marvin gave you the built instructions and xml files to
>create a mavenized Flex SDK or that you can talk with him to get it from
>first hand. Moreover, if you was working with all SDKs as you report, you
>already know all about this process.
>That process could give us the keys to rethink all Apache Flex SDK
>structure to be BMS (Build Management System) compliant. (Regarding the
>instructions, if you can't get it I can provide you with the files I used
>in my company and some instructions, although there's some places out
>where you can find it.)
>I think that we need to create the needed pom(s) (in the maven case, I
>don't know yet how gradle works) for the new refactorized flex sdks in
>order to create the artifacts. The last point to take into account would
>to talk with apache maven project to publish in maven central repository
>the flex sdk artifacts. (Maybe I'm wrong in some step since I never do
>something like this... thiese are theoreticaly the steps to follow).
>In this way we could have all artifacts directly available when a new flex
>sdk was released in a maven central repository.

View raw message