Comments on: Practicing Continuous Integration on Flash Projects : What Is CI?

By: Flash, Flex et intégration continue: Le guide complet (SVN, Maven, Hudson & co) - Adobe Flex Tutorial - Tutoriaux Flex Builder, MXML, ActionScript, AS3

Fri, 17 Sep 2010 09:52:04 +0000

[...] Practicing Continuous Integration on Flash Projects : What Is CI? [...]

By: Matt

Matt — Tue, 20 Jul 2010 20:39:29 +0000

Thanks Tehsin. Unfortunately I don’t have any experience with LiveCycle and BlazeDS. Nor do I have experience with GraniteDS. But what you’re describing sounds like something I’d write a custom Ant task that could be used in the build process.

By: Nate Beck

Nate Beck — Tue, 20 Jul 2010 20:22:20 +0000

Hey Matt!

Excellent series, keep up the great work!

Cheers,
Nate

By: Tehsin Bhayani

Tehsin Bhayani — Tue, 20 Jul 2010 15:56:47 +0000

Nice article

Any thoughts on how to automate the generation of (mapped) actionscript classes based on daily changes from the backend?

One of the main challenges for me in a CI based environment is the ability for Flash/Flex to be in line with the backend (e.g. Java) side of things.

Using the Gas3 generator running on Granite, (with builds done by Maven/FlexMojo) seems to be a (relatively) smooth way of automating the process of generating mapped actionscript classes based on changes from the backend, but would love to hear of any BlazeDS/LiveCycle based solutions that provide this sort of automation, or any other practical solutions for automating the generation process…

Thanks,

Tehsin