You can use the Adobe Extension Packager to package your own extensions before submitting them to Adobe for distribution on the Adobe Exchange website. You can download Adobe Exchange Packager by signing in Adobe Exchange producer portal with your Adobe ID. After packaging an extension, test it by using the Extension Manager to install it locally. Guidelines for writing and testing your extensions can be found in Exchange Help on the Adobe Exchange website (www.adobe.com/go/exchange). After you have written and tested your extension, you can package and submit it.
The Extension Manager supports the following types of extensions and file formats. For details about creating extension installation files, see the Extension Manager CS Configuration Reference, which you can download from the Adobe website at www.adobe.com/go/em_file_format.
Any extension that is not a Creative Cloud extension. You can package ordinary extensions using the ZXP format.
Creative Cloud extension
A web service that you access directly from a Creative Cloud application -- for example, from a panel in the Extension menu. Both Adobe and non-Adobe developers can create these extensions. Creative Cloud extensions must include a certified signature from the publisher. For example, CSXS_Adobe.zxp is a zip-based Creative Cloud extension signed by Adobe.
Combines the action panels of Creative Cloud extensions with tight integration in the product. For example, the floating panel in Dreamweaver lets you preview pages in web browsers. Hybrid extensions include both ordinary extensions and Creative Cloud extensions.
An XML file that specifies attributes of the extension, including the extension name, a description of the extension, version number, and type. The file also specifies each file included in the extension, including any custom icon you want to use. To specify a description of your extension, you can use HTML in your text or link to a local HTML file. You can also link to a remote HTML page when the user has an Internet connection.
A zip-based package format that can include a digital signature that identifies the extension’s publisher.
The traditional package format for extensions that Extension Manager supported. This format is deprecated in CS6 and no longer supported in CC. You can convert legacy MXP packages to ZXP by selecting Tools > Convert MXP extension to ZXP in Extension Manager CS6.
Follow these steps to package an ordinary or hybrid extension.
Extension Manager doesn’t support packaging Creative Suite extensions. These extensions can be created with the Creative Suite SDK.
If you don’t provide your own icon, the default icon is used.
The files can be at different levels of the folder hierarchy. Specify a path to each file relative to the installation file using the <file> tag in the extension installation file (MXI file—see the next step). However, it’s easier to track all the files if you don’t try to package them directly from their installed locations in the Configuration folder.
In the Extension Manager, select File > Package ZXP Extension.
In the file-selection dialog box that appears, select your MXI file, and then click Open.
Select a location for the package file, give it a name ending in .zxp, and click Save.
The extension package filename must not contain spaces. It must also be valid on both Windows and Mac OS platforms.
The Extension Manager creates a package file containing compressed versions of all the files used by the extension, including the MXI file.
Install and test the extension to make sure that everything works as intended.
The Adobe Exchange submission page opens in your browser.