flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <carlos.rov...@codeoscopic.com>
Subject Re: BlazeDS
Date Fri, 06 Jan 2012 23:06:39 GMT
Separate projects IMO.

One project can have dependencies on other projects and this should not be
a problem. More over if we finaly get maven artifacts ; )

We have to take into account that the Flex ecosystem is huge and should be
in the end many projects with subartifacts in each project (modularity is a
big necesity here), since we need to manage the growing of the project in
the long time, so I would prefer to start separating things that we see
right now that could live in diferent projects and have different timelines
and releases.

2012/1/6 Greg Reddin <gredbug@gmail.com>

> On Fri, Jan 6, 2012 at 4:39 PM, Alex Harui <aharui@adobe.com> wrote:
> > Mentors, what criteria would you use to determine if Blaze should be its
> own project?
> I would say it would be its own project if it has its own distinct
> community. The two communities can certainly overlap, but if there's a
> significant number of folks in one community, but not the other, it
> would become its own project.
> It's really no problem to start together, then separate at a later
> time. I suggest we cross that bridge when we come to it.
> Greg

Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 35 57 77

CODEOSCOPIC S.A. <http://www.codeoscopic.com>
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid

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