Most Projects don't rely on libs with licenses not allowing to publish. The Problem is that Flex relys on the FlashPlayer and Air runntime. This belongs to Adobe and Adobe doesn't give us the permission to publish the airglobal and playerglobal libs. Users would still have to manually download and deploy them which would probably cause quite a bit of Trouble with users new to Flex and Maven. Thats why we decided to pick up a complete FDK for which a user has allready accepted the Adobe licenses and to mavenize this in one step. I think the Installer Guys are currently working on integrating the Mavenizer into the installer, to make things even easier.
Chris ________________________________________ Von: Matt Hughes [[email protected]] Gesendet: Montag, 9. September 2013 13:11 An: [email protected] Betreff: Re: AW: 4.10.0 Maven Artifacts What is the reason for not publishing the artifacts to central or at least Apache's Maven repo? It's great that there is a tool, but most Apache projects publish their artifacts. On Sep 9, 2013, at 3:55 AM, "[email protected]" <[email protected]> wrote: > Yes, the mavenizer was built exactly for that. > > If you want to build your Flex application with Maven, you should use the > Version 6.0.1 of Flexmojos, which was modified to work with the new mavenized > FDKs. > > Chris > > ________________________________________ > Von: Matt Hughes [[email protected]] > Gesendet: Montag, 9. September 2013 03:25 > An: [email protected] > Betreff: 4.10.0 Maven Artifacts > > Are the 4.10 artifacts published to a Maven repository anywhere? The > latest artifacts on Maven Central at 4.5. > T r > I see the Mavenizer project in flex-utilities…Is the idea that everyone > generates their own Maven artifacts using that?
