Hi 4xy (Strange name by the way ;-) )

I removed the generation of adobe artifacts, as this code sort of had to be 
pulled though the entire application, making it more complicated than it needed 
to. 

And on the other side I was expecting having to support some features in 
Flexmojos 6.x and 7.x, which I wanted to avoid.

You can still mavenize older FDKs, but the generated artifacts would have the 
apache namespace and would have to be compiled by Flexmojos 7.x.

If you need adobe groupIds, stick to the old mavenizer and use Flexmojos 6, but 
I will not be maintaining 6.x and 7.x the same way. So if you need the good new 
stuff, migrate to Flexmojos 7 and Apache GroupIds ;-)

Chris

________________________________________
Von: 4xy <[email protected]>
Gesendet: Donnerstag, 6. November 2014 14:24
An: [email protected]
Betreff: Re: AW: AW: Mavenize Apache Flex SDK 4.13 in couple with Air 15

Hi Chris,

One more question.
Is it possible to generate sdk in old manner using com.adobe namespace?





--
View this message in context: 
http://apache-flex-users.2333346.n4.nabble.com/Mavenize-Apache-Flex-SDK-4-13-in-couple-with-Air-15-tp8549p8598.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Reply via email to