using an MXP to install the components

[GoogleCodeExporter]

same as *.SWC can provide an easy use for the users
we could also distribute an *.MXP to install with
the Adobe Extension Manager
http://www.adobe.com/exchange/em_download/

also we could upload the MXP to "Adobe Exchange"
http://www.adobe.com/cfusion/exchange/

concerns:

- maybe we would need to produce 2 MXP
  one for the category "Flash"
  another for the category "Flex"

- maybe this would add another "by hand" step
  as I'm not sure how the process can be automated on the command line
  to generate an *.mxp from *.mxi

- also we would need to create an adobe account to
  be able to upload on the Adobe Exchange,
  this account should be shared by the team (and not be a personnal account)

- the upload process could also create another "by hand" step

- the *.MXI file can be auto-generated by using templates (as the readme.txt)
  see: http://www.macromedia.com/go/em_file_format/

Original issue reported on code.google.com by zwetan on 13 Dec 2008 at 1:14

[GoogleCodeExporter]

doc for packaging MXP from CS3
http://help.adobe.com/en_US/ExtensionManager/1.8/

doc for packagin MXP from CS4
http://help.adobe.com/en_US/ExtensionManager/2.0/

with CS4 we can automate the process on the command-line

Original comment by zwetan on 13 Dec 2008 at 1:26

[GoogleCodeExporter]

need to package 2 different MXP, one for CS3 and one for CS4

the MXP creation can be integrated in the Ant build, but only with Extension 
Manager 2.0+

Original comment by zwetan on 18 Nov 2009 at 10:13

• Changed state: Accepted
• Added labels: Milestone-Release1.1

[GoogleCodeExporter]

to keep things simple and the logic one distribution is one file, we will not 
provide an MXP

Original comment by zwetan on 30 Apr 2012 at 10:00

• Changed state: WontFix