Hi,
I also like to integrate Flex/Air parts of my project (JEE + Flex + Air) to
maven.
While i was investigating for a solution i found
https://github.com/yelbota/adt-maven-plugin but unfortunately it doesn't
fit my needs as i want to package a native extension.
So i decided to extend FM 6.x
Sounds good that you got that AIR stuff working. If you would be willing to
contribute it back (Including test-projects for the testsuite) I would be
glad to add that to FM.
But I have to clarify: I can't donate FM to Apache, because the code is not
mine. I've taken over maintaining FM, but the
Well of course you could replace the Air SDK, but I still call this tightly
coupled. In contrast to the Flash Player you can't simply select the
runtime you want to use. Let me rephrase my statement: The Flex SDK is
tightly coupled to only one Air SDK at a time :-)
Acutally Air, Flash and Flex
@Piergiorgio Niero
Thank you man! Are you compiling with AIR? If yes, any chance you could
share an example pom.xml or zipped project example?
Kind regards, adq
On Monday, January 14, 2013 10:05:46 AM UTC-5, Piergiorgio Niero wrote:
Ok, I created a skinny recap of my experience so far with
The problem is that usually the Air Version is tightly coupled with the
flex version. So as far as I know it's usually not possible to build Air
applications with other versions than the one shipped with the FDK. The
mavenizer now did a first step to decouple this. Unfortunately I never
built any
Factually, I'm not certain of this:
The problem is that usually the Air Version is tightly coupled with the
flex version.
...as we could customize the Flex sdk by overwriting the AIR files
distributed within the Flex framework with the AIR sdk of your choice, etc.
Moreover, Adobe has
Ok, I created a skinny recap of my experience so far with flexmojos 6.x and
mavenizer.
I'll continue keeping up to date for myself, if there's any official doc
spawning somewhere please let me know so I can unpublish my doc (for
documentation coherence)
here's the
link
Yep ... that's the sequence.
And don't forgett to skip the big testsuite or you would have do deploy
allmost every FDK.
To admit ... I think the future will be at Apache ... at least that's where
I'm currently sticking all my free time.
They are allways looking for guys willing to get their hands
Ok, so, get the mavenizer first, build and deploy Flex 4.6.0.23201. Then,
I can compile flexmojos 6 from source?
If that the sequence of events?
Man, thanks for your time.
Is there anyway some of us can get involved to ensure flexmojos has a
future?
Although it's probable the flex is dead,
FM6 only works with FDKs that were created by the Mavenizer tool. It
doesn't work with the FDKs deployed by Velo. If you want to build the
entire Testsuite you will have to build all of the FDKs, which might not be
what you want. So I suggest to create a mavenized version of 4.6.0.23201
and skip
Comming back to the original question :-)
The lack of available FDKs was the reason I created my Mavenizer tool ...
It's hosted at Apache Flex (Cause I thought it belonged there).
http://incubator.apache.org/flex/utilities.html
The code is at the flex utils svn repo:
Perfect, thanks,
But, hmm, when trying to compile from your Flexmojos 6 source, I get the
following failure:
Non-resolvable import POM: Failure to find
com.adobe.flex:framework:pom:4.6.0.23201 in
http://repository.sonatype.org/content/groups/flexgroup/ was cached in the
local repository,
Open Source is a labor of love.
Michael
On Dec 16, 2012, at 6:47 AM, Marvin Froeder velo...@gmail.com wrote:
On Dec 14, 12:41 pm, rpm r...@ecosystems.us wrote:
I have the impression the FM Enterprise is no longer in development due to
Velo's lack of interest in Flex. What is the status
13 matches
Mail list logo
