Updated the pom.xml, done !
-----Message d'origine-----
De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com]
Envoyé : lundi 23 septembre 2013 19:54
À : dev@flex.apache.org
Objet : RE: Building an AIR library with Maven
Hi,
I assumed you meant FU 4.1, what you can do as well is set the ADT
${air.version} dep in the FM deps, you can have a look at my repo for a
complete air mavenized app (I will update the pom.xml in few hours to
reflect the last changes introduced by the new artifact versions):
https://github.com/apacheflex/whiteboard_fthomas_developerToolSuite
HIH and thanks for sharing, I didn't know the link to
mavenizing-flex-sdk-missing either, nice !
-Fred
-----Message d'origine-----
De : alebianco [mailto:i...@alessandrobianco.eu] Envoyé : lundi 23 septembre
2013 15:48 À : dev@flex.apache.org Objet : Building an AIR library with
Maven
This weekend I decided to convert the the build process of some of my
pet-projects from Ant to Maven ... madness followed shortly.
One of the requirements was to keep using the latest Apache Flex and AIR
builds, respectively 4.10.0 and 3.8. The other was to be able to run the
test suite as part of the build process.
/note: i'll post a pom example at the end, so you can skip all the babble
and go straight to the sources/
Soon I realised that Flexmojos 6.0.x was the only option and Flexunit 4.0.1
would work best with it. from there it was just a matter of figuring out
that they're being deployed under different groupIDs than they were before.
Then I had to deal with the Apache Flex framework not being deployed
anywhere. So I followed the (poorly documented) mavenization process. I
failed. A couple of times.
Then I found this guide
<http://anthonywhitford.blogspot.co.uk/2013/09/mavenizing-flex-sdk-missing.h
tml>
and everything made sense and worked flawlessly.
Now the project was able to build, but the test suite failed to run,
returning a "Initial window content is invalid" error.
After a (long) while I realised that in the TestRunner.xml descriptor, the
namespace for the application was for AIR 3.1 and it was preventing the swf,
compiled with AIR 3.8, to be loaded.
After going through the Flexmojos code I figured out that it "guesses" the
AIR version depending on the Flex version, but the list only included Adobe
versions of the framework and their "originally shipped" version of AIR.
Luckily there's a property to override the AIR version: ${flex.airVersion}
So I just had to include that in my pom to have the descriptor to be
generated correctly and the test suite to run happily.
I'm not very happy yet about the pom and probably some dragons are still
hidden behind corners but it kind of work, so I thought I was worth sharing.
I'll have another look at the Flexmojos sources and hopefully I'll find a
way to specify the Flex version without having to override the compiler
dependency of the plugin.
*As promised, here's a pom example to check
https://gist.github.com/alebianco/6670561*
PS: I'm no Maven expert, not by a long shot, so if I made some gross mistake
in the post or the pom, please let me know ...
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/Building-an-AIR-library
-with-Maven-tp29883.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
