e.com]
Gesendet: Mittwoch, 23. Mai 2012 23:50
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: Library Versions used in Flex SDK
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 rela
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,...), tha
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: Ap
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 flexmoj
On 5/23/12 9:09 AM, "christofer.d...@c-ware.de"
wrote:
> Hi,
>
> Well to the issues: I don't know all of them, I just know that Velo keept on
> complaining about Adobe breaking stuff. The only thing that I currently have
> on my radar is that the ASDoc in the latest SDK version was totally br
Hi,
Well to the issues: I don't know all of them, I just know that Velo keept on
complaining about Adobe breaking stuff. The only thing that I currently have on
my radar is that the ASDoc in the latest SDK version was totally broken. Having
a look at the code showed my that this module would ha
