Even if I'm currently the project lead of Flexmojos, I would strongly suggest not to go that road. There is far too much legacy stuff to carry with Flexmojos and I have to admit that the rather restricive communication policy of Velo is rather discouraging.
I think IF WE WERE TO GO THAT ROAD, developing an Apache Flex plugin first and using that to compile the Framework libs sounds like a far better solution. This way we would have controll over the entire stack needed to build Flex. Chris -----Ursprüngliche Nachricht----- Von: omup...@gmail.com [mailto:omup...@gmail.com] Im Auftrag von Om Gesendet: Dienstag, 27. November 2012 20:41 An: flex-dev@incubator.apache.org; jef...@dot-com-it.com Betreff: Re: [Discuss] Maven and Apache Flex I have initiated a thread with my UI architecture team. Will send out the poll responses soon. In the meantime, here is a gauge of the popularity of this feature. This is the most voted-on issue in our JIRA base. https://issues.apache.org/jira/browse/FLEX-33086 https://issues.apache.org/jira/secure/ViewVoters!default.jspa?id=12538816 Thanks, Om On Tue, Nov 27, 2012 at 11:28 AM, Jeffry Houser <jef...@dot-com-it.com>wrote: > > As I understand it, Maven is an automated build tool. Kind of like > ANT on steroids. > > > On 11/27/2012 2:20 PM, Harbs wrote: > >> 0. I have never quite figured out what Maven is or why I'd want to >> use it. (and I do speak yiddish.) ;-) >> >> If someone could enlighten me, I could change my mind. >> >> Harbs >> >> On Nov 27, 2012, at 8:46 PM, Alex Harui wrote: >> >> 1. Number of people who will use Maven to develop Flex apps at your >>> company >>> (0 if you have no interest in using Maven). >>> >> >> >
