flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cosma Colanicchia <cosma...@gmail.com>
Subject Questions about current mavenizer status
Date Tue, 19 Nov 2013 17:25:38 GMT
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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message