flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cosma Colanicchia <cosma...@gmail.com>
Subject Re: Building SDK from sources and locales support
Date Wed, 18 Sep 2013 16:42:13 GMT
It's not very clear if the input of the mavenizer is an IDE SDK, or a plain
binary kit.

Until now I was trying with the IDE SDK (since I wasn't producing a binary
kit from sources), this may be the main cause of my problems: I think that
the mavenizer got confused by the extra SWCs files put in the Flex SDK
input folder, making it generate playerglobal-related and other artifacts
with the wrong groupId and for multiple FP (11.1 + 11.8).

So, I repeated the process with the following steps instead:
1) generated a binary package (ant main frameworks-rsls sample-themes
other.locales binary-package additional-packages -Dlocalized.jars=true) *
2) extracted the content of the package in the mavenizer input/flex/...
3) manually copied a playerglobal.swc 11.1 in the
/frameworks/lib/player/11.1 in the extracted folder
4) run the mavenizer SDKGenerator and SDKDeployer
5) run the ide script from the original source folder

This way, projects seems to compile correctly in FB and with Maven, thank
you for the help!

About the SNAPSHOT:
I like the idea of having these artifacts as snapshots in the m2 repo, but
encountered the following drawbacks:
 - I had to manually correct the name of the generated RSLs in
frameworks/rsl, and correct their rsl-url in the frameworks/air-config.xml
and frameworks/flex-config.xml (maybe updating the sdk description before
the build could have them generated with the correct name, but don't know
if it is supported)
 - The multiple deploy-file operations used by the mavenizer to deploy all
the artifacts seems to be messing up the timestamps of the single artifacts
(they get a different timestamp on each generated artifact snapshot),
causing problem to flexmojos that will complaint about discrepancies
between the compiler and framework artifact timestamp versions

So, in the end, I reverted to generating plain artifacts with the
4.10.0.YYYYMMDD version.

About the binary-release-noclean target:
 - it executed some checkin tests (isn't it mustella?), and failed
(probably due to crossdomain issues)
 - it skip the setup-binary-release target, that was also setting the
localized.jar variables.. maybe we could create a

2013/9/18 Frédéric THOMAS <webdoublefx@hotmail.com>

> I guess, what I would do more or less is:
> update-index --assume-unchanged flex-sdk-description.xml
> run the ant targets you mentioned or even a release
> change the build number in the flex-sdk-description.xml to 0
> run the sdk/ide batch I need
> run the Maven converter (because you set the build number to 0, it will
> generate a 4.11-SNAPSHOT)
> then, deploy it
> -Fred
> -----Message d'origine-----
> De : Cosma Colanicchia [mailto:cosmacol@gmail.com]
> Envoyé : mercredi 18 septembre 2013 10:02
> À : dev@flex.apache.org
> Objet : Re: Building SDK from sources and locales support
> >
> >
> > >  running checkin tests (and I think that my mustella is not set up
> > properly, never tried running it yet), Running the checkin tests is
> > separate from running mustella.
> Thank for the tip, I'll try to run it later to see what happens (but I
> have no modified sources currently).
> p.s. the actual command line was:
> ant main frameworks-rsls sample-themes other.locales additional-packages
> -Dlocalized.jars=true
> (frameworks-rsls, not framework-rsls)

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