gmail.com]
> Gesendet: Dienstag, 19. November 2013 21:47
> An: Apache Flex Developers ML
> Betreff: Re: Questions about current mavenizer status
>
> Yes, it worked as described in the README. What was your problem exactly?
> I set the use-apache-gid parameter to false, because all
Well, my problem was several months ago when I tried to use the package
"org.apache.flex" instead of "com.adobe.flex", but it was because Flexmojos
6 was still being developed. This time I only remember I had to change the
property in the parent pom of Flexmojos to use "org.apache.flex" and it
work
Yes, it worked as described in the README. What was your problem exactly? I
set the use-apache-gid parameter to false, because all of my project are
still using the old flexmojos versions
Noticed now that the README.txt does not describe the use-apache-god
parameter, that is correctly reported in
Did the param "fdktarget" work for you, Cosma? I remember I tried to
configure that quite time ago but it didn't worked forme. I also remember
that Christofer recomended me not to use "org.apache.flex" package
(Flexmojos 6 was still in development). This last time I tried it, I just
changed the pro
@Christofer
Thanks for the info, just some questions: when you say “win” directory, are
you referring to the subfolders in runtimes/air and runtimes/air-captive?
The SDK produced by the installer correctly contains the “mac” runtimes, if
I understand correctly I should be able to add the correspon
On Tue, Nov 19, 2013 at 11:47 AM, christofer.d...@c-ware.de <
christofer.d...@c-ware.de> wrote:
> Hi Cosma,
>
> as Toni already confirmed, the mavenizer is currently the easiest way to
> create maven artifacts from a Flex SDK you downloaded using the Downloader.
> The Mavenizer doesn't actually re
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
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 bet
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 ext
