On Thu, Oct 28, 2010 at 10:39 AM, Marvin Froeder <[email protected]> wrote: > http://screencast.com/t/SqgZK2je > > For some crazy reason adobe includes all maven artifacts inside it.... if no > conflict happen between your current maven and the included version (maven > 2.0.4) you are safe, but guess what, conflicts can happens in some > cases/some maven versions.... > > Also, adobe is embedding JFLex, a GPL software, I honestly don't wanna work > at Adobe's legal department if someone decides to pursuits this. > > Why don't the at least do like on Flex SDK, isolated jars.... or relocate > the packages..... > > I hope you can get they fixing this sh**, but I doubt, they just don't seem > to care if flex lost maven support.... > > > VELO
I wonder if it's different because they bundled in their crap for the I see the jf and baksmali stuff in there (funny to me how they are using smali / baksmalli to generate their air-for-android wrappers, I'm friends that developer) I bet Smali is the culprit - it's built with maven I believe and I bet they didn't bother figuring out wtf all those maven packages were doing so they just threw them all in the big jar and said "there." This is the first public beta release that includes all of the air for android stuff so that's probably what is different. Ryan -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
