Thank you very much Toni, I’ve just successfully (?) created the artifacts locally, very straightforward so far, no need to provide a separate AIR SDK to the mavenizer. Tomorrow I’ll try to deploy them to the m2 repo and I will report back.
The artifact names are determined by the mavenizer itself, based on the build number, I’m not sure that it can be easily changed (without side effects) in the SDK descriptors in order to create mac/win arficats, but I hope it won’t be required (otherwise each developer should locally adjust the project’s pom.xml files to reflect the local environment). 2013/11/19 Toni Vega <toniveg...@gmail.com> > Sorry, I forgot that I was using adt-maven.plugin by yelbota and probably > was the plugin who required the zipped version of the SDK. Just try it and > let me know. In that case, maybe you should deploy SDKs versions like > 3.9.win and 3.9.mac and use different profiles to build. Maybe someone has > a better approach. > > Regards > > > 2013/11/19 Toni Vega <toniveg...@gmail.com> > > > Hi Cosma, recentlly i was able to mavenize a mobile air application using > > FDK 4.11 and AIR 3.9. I'll try to answer you. I hope to have understood > > your questions and doubts. > > > > Q1.: Yes, that is the way, although i had to do some tricks with package > > names in flexmojos > > Q2.: The mavenizer is able to extract the AIR SDK inside the Flex FDK, > you > > must provide a separated one in case you want another version. > > Q3.: I can remember I had to provide an artifact that was the complete > AIR > > SDK zipped. I had to install it because it seemed to be by default in 3.5 > > but not in 3.9. The artifact was com.adobe.air:air-sdk-3.9-windows.zip. > I > > supose adt will ask you for the mac version of this artifact. > > > > I hope this was helpful. > > > > Regards > > > > > > 2013/11/19 Cosma Colanicchia <cosma...@gmail.com> > > > >> Hi there, > >> > >> I’m in the process of trying of rolling out Apache Flex 4.11 internally > >> for > >> the other employees of my company, and I need to deploy the related > >> artifacts to the company Maven repo. > >> > >> AFAIK, the only way to do this for 4.11 is by mavenizing/deploying a > >> downloaded FDK, is this right? I was following the other thread about > >> storing ready-to-use artifacts in some public repository, but this path > >> doesn’t seem ready yet (BTW, is there something I could do to help in > this > >> effort?) > >> > >> I managed to successfully build and mavenize the FDK from develop branch > >> in > >> some months ago, but I still have some questions: > >> > >> Q1 - I’m going to try running the mavenizer/deployer tools on the output > >> of > >> the Apache Flex Installer in order to mavenize the released 4.11 FDK, is > >> this the intended way of using it? > >> > >> Q2 - the mavenizer requires the AIR runtime in a separate directory... > but > >> the installer output should already have integrated it in the FDK, > should > >> provide it separately anyway? > >> > >> Q3 - is the FDK produced by the installer cross-platform? This time I’m > >> using a Mac to run the installer, so it has probably downloaded the Mac > >> version of the AIR SDK.. does this mean that, when mavenizing this SDK, > >> the > >> Windows binaries (e.g. adt command line tool) won’t be included in the > SDK > >> artifacts and the SDK won’t be fully compatible with developers on > Windows > >> machines? > >> > >> > >> Thank you for any help > >> Cosma > >> > > > > >
