incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <>
Subject Re: AW: AW: AW: AW: Library Versions used in Flex SDK
Date Thu, 24 May 2012 11:41:32 GMT
Hi Alex,

I'm with you that flexmojos was forced to make things dificult mainly
because the Adobe SDK was configured in a particular way. As SDK evolve ,
flexmojos was breaking all the way. Another point was Adobe making its own
forked-versions of wellknown libraries (i.e.: apache commons,...), that
complicated things all the way for third party projects like this. That was
one of the points that make Marvin pass the torch.

We don't have to miss the main point: get Apache Flex coexist with other
technologies in advanced build management systems (like maven or gradle)
and CI servers. This is crucial for the future of Flex.

Flexmojos is not really a must. Historicaly was the project that make all
the above possible, but with a high cost in human resources and hours for
IT teams that follow that path. Nowadays there's more options (Gradle +
GradleFX?), but I still didn't have the time to invest in order to see if
that kind of solutions are a valid replacement.

What is real is that refactoring Apache Flex SDK to take into account this
kind of build management system will help a lot in this necesity.

For example, the Adobe Flex SDK structure was one of the main problems that
make Marvin desist in create mavenized SDK versions (latest is,
and that is the version that the majority of IT departments are usign
today). Changing structure to take into account maven or gradle will be
something really cool since it will make avoid that step and make things
far easy to deploy for that kind of build management systems.

2012/5/23 Alex Harui <>

> On 5/23/12 1:15 PM, "Carlos Rovira" <> wrote:
> > Hi Alex and Chris,
> >
> > I asked in the flexmojos list, but I'll do it here since is related to
> > Apache Flex as well. With the new announcements in the flexmojos list
> > (Marvin hasleft the project in Chris hands) it make me think the
> > following: Apache owns Maven and Flex...could have sense to bring
> flexmojos
> > to Apache as well? (Apache FlexMojos)?
> >
> > I think it'd be very natural and convenient if all projects will be under
> > the same umbrella and will evolve based on the same criteria. What do you
> > think about it? Could it have sense?
> >
> If the owners of FlexMojos want to contribute it to Apache, we would
> probably accept it.  My main concern is whether FlexMojos has to contain
> all
> that it contains.  Maybe there is a simpler extension for Maven given that
> we can do pretty much whatever we want to the SDK.  FlexMojos is the way it
> is in part because the Flex SDK was packaged the way it was and the
> compiler
> worked the way it does.
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.

Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 35 57 77
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message