I would think it is related but I'm at a loss as to explaining what is
actually going on.
Sam
On Sunday, 16 December 2012 04:09:50 UTC, remiP wrote:
Hi Sam,
Could this be related to the workaround I found for
FLEXMOJOS-483https://flexmojos.atlassian.net/browse/FLEXMOJOS-483(cf. the
last
Air and Flashplayer were historically bundled with each FDK. While the
Flashplayer only was a few files the complete AIR SDK directory way mixed
into the FDK directories. The Mavenizer knows which artifacts are Flex, Air
and Flash and separates them.
Flex: com.adobe.flex / org.apache.flex
Flash:
I am still wrestling with this issue and don't have a resolution. Can
someone please assist? Thanks!!!
On Tuesday, 11 December 2012 11:23:07 UTC, Murray Furtado wrote:
I have a working maven pom which builds my AIR app and I am trying to
migrate it to use the new AIR 3.5 SDK. According to
I think the problem is that your Maven doesnt have access to the latest
Flexunit releases.
The artifacts should be there, as I released them there myself. So I guess
you were simply missing a repo in your maven config.
The problem with the AsVmLauncher, is that you have to have a file called
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
Strange ... If you guys tried the most recent mavenizer, then the Empty-Zip
problem should be solved.
I am assuming the post got stuck here and was released over Christmas ...
I really hate that :-(
Regarding the full build of Flexmojos: If you build FM6 with all tests
running, you will need
