Thanks for taking the time to respond, Scott! Velo, could a kludge suffice until Adobe publish?
Idea 1: Publish with an interim version number after 17689 to allow Maven to separate it. Problem: I guess that'd screw the generated RSL paths though (if one's using the version info)? Idea 2: Re-publish. Problem: Am I correct in thinking re-publishing with the fix isn't advisable in a public repo? (hence your question to Scott) Last clarifying question: we're OK doing it in our private repos though if we accept the [minimal] risk, right? (not sure I know what risks might be but...!) Idea n? Sorry [as always] for the dumb questions. Just looking to move things forwards (publicly and internally) Thanks, R. On 08/11/2010 19:18, Scott Castle wrote: > Hi Flex Mojos list, > The AIR team is in the process of fixing the issue with Maven and ADT > now. We will be updating the AIR 2.5 SDK with a repackaged adt.jar > that no longer includes the unnecessary jar files from smali/ > backsmali. We currently plan to publish this update to the web on > 11/18/2010. > > Flex SDK users should be able to update their existing Flex SDK by > overlaying the new AIR 2.5.2 SDK over the shipping version. > > Regards, > - Scott Castle > > On Nov 7, 6:53 pm, Marvin Froeder <[email protected]> wrote: >> I honestly don't expected changes any time soon. Since this is a released >> product, but who knows..... >> >> I hope to be proven wrong, but one week later I still right.... >> >> >> >> On Mon, Nov 8, 2010 at 12:33 AM, Rupert Key <[email protected]> wrote: >>> Hi, Scott >>> May I echo Muji's public thanks for your and Adobe's attention to this (and >>> to >>> Joseph for fixing the integrated JAR quickly, too!). May I ask whether >>> there's >>> any newer update than that posted in the bug, please? Especially with >>> Android >>> capabilities! >>> Thanks, Rupert. >>> On 31/10/2010 18:12, Scott Castle wrote: >>>> Hi folks, >>>> I am a product manager with the AIR team at Adobe. This issue has >>>> been brought to our attention, and our understanding is that it's >>>> caused by the inadvertent inclusion of the jflex-maven-plugin jars in >>>> smali/backsmali. We're taking steps to correct this ASAP in the AIR >>>> SDK, which should resolve the issue identified with the Flex SDK. >>>> Regards, >>>> - Scott >>>> On Oct 25, 6:35 pm, Marvin Froeder <[email protected]> wrote: >>>>> Before anyone asks, flexmojos do not work with this SDK release. >>>>> For some reason adobe decided to embed lots of GPL bytecode into >>> ADT.jar, >>>>> which does break maven classloading. >>>>> When adobe fixes that people can hope to get flexmojos working with this >>> new >>>>> flex SDK. >>>>> Sorry folks, completely out of my hand. >>>>> VELO >>> -- >>> 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]<flex-mojos%2bunsubscr...@googlegrou >>> ps.com> >>> For more options, visit this group at >>> http://groups.google.com/group/flex-mojos >>> http://flexmojos.sonatype.org/ -- 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/
