Please use the tool "Adobe Exchange Packager" to package extensions.
where should I download "Adobe Exchange Packager"? Please Login "https://www.adobeexchange.com/", click"go to the producer portal" and signIn, choose "Resources" and download the "Adobe Exchange Packager".
According to the documentation:
“If you have created your product using earlier versions of these tools, or the free Creative Suite SDK, or if it is a script or C++ plug-in, or some combination of these things, you can manually create a manifest MXI file and package your delivery files into a ZXP, using the command-line utility in the Packaging and Signing Toolkit. See the section Packaging Manually”
(The link points to the section which indicates that the UCF command line tool should be used to create the package.)
Is this documentation wrong?
The Packager utility indicates that it supports the following types of content for Photoshop:
- Actions (ATN)
- Brushes (ABR)
- Gradients (GRD)
- Patterns (PAT)
- Scripts (JSX)
- Swatches (ACO, ASE)
That does not include filter plug-ins (.8bf on Windows, .plugin on Mac), and so it does not apply to my use case.
(Furthermore, it does not appear to be possible to run the packager tool from the command line, meaning that it is not useful to me since it would be very difficult to integrate it with our build system. Is it possible to run the Packager from the command line?)
Adobe Exchange Packager is a new tool. It doesn't support command line. "Using Adobe Exchange Packager" section hasn't been updated to reflect the latest version. Now you can create a mxi file manually and place it as well as all content files in a folder then package it with Exchange Packager. You can use .8bf or other file types.
Since Adobe Exchange Packager cannot be driven from the command line, it is not useful to me, so I will continue to use ucf.jar.
I see that the spaces-in-filenames problem is fixed with the version available through the prerelease programme, which is dated December 2012. Perhaps it's time to replace the publicly available version with the one currently in prerelease, and to update the currently misleading documentation of Adobe Exchange Packager to reflect the current state of affairs!
So, finally, to answer my own question:
The version of ucf.jar dated December 2012 does support spaces in filename. At the time of writing this version is only available through the prerelease programme. The publically released version, dated October 2012, does not support spaces in filenames. There is no known other tool provided by Adobe which may be driven from the command line to create .zxp packages for Extension Manager.
There is no known other tool provided by Adobe which may be driven from the command line to create .zxp packages for Extension Manager.
As of now, there is at least one other tool. As explained in this article ZXPSignCmd can be used to create zxp packages.