Ok so I learnt a lot this past week. Here are my notes, I hope they can help someone else just starting out.
* Reference the quick start heavily, diverting from this structure is bad.
The app is split into multiple sections, I will refer to as:
* web app
* libs ( multiple )
Each section will have it's own .pom file.
* the project .pom will be quite simple, mostly just referencing other modules. from the quickstart:
* it's packaging must be pom
* no dependancies or plugins here.
* The web app pom has a little more information, but still quite light:
* it's packaging must be war
* include jangaroo-maven-plugin and maven-war-plugin
* dependancies would be jangaroo-browser and your custom libs, both of type jangaroo
* The app needs a main constructor class, with a static constructor. This is very important. I wasted a lot of time here because my main class' constructor was public, not static.
* in the web app's .html file, reference your main class. Note that the 2nd param is an array of arguments, which I do not require for my example. Quick start will look different. :
* The most complicated .pom file
* it's packaging must be jangaroo
* This file may include repositories
* do not need to include maven-war-plugin, but do need jangaroo-maven-plugin
* dependancies include all extended libs, for me this was: jangaroo-runtime, jooflash, jooflexframework, playerglobal (swc)
* I found it best to stick to version 0.9.7 for all things Jangaroo ( runtime, plugin, dependencies )
* when running maven commands, you will need to install each individual lib. From there you can clean / compile / install from the root ( the pom file with just the modules )
* you never need to extract a jar or copy and dependancy files.
( if anyone has anything to add to my notes, please share. Jangaroo is my first exposure to maven )