We originally started creating InDesign extensions "manually" several years ago, as we did not yet want to pay for the original Extenson Builer 1.0. We produced our ZXP files from the contents of the bin-debug folder using Fabien Bizot's Java-based "ZXPPackager" utililty (http://www.lafabrick.com/),
When we finally installed Extension Builder 1.5, we had some problems creating ZXP with the built-in exporter for Abode Application Extension. Since the compiler put all the files into the bin-debug folder still, I could still use ZXPPackager.
We just upgraded to Extension Builder 2.1. For any legacy project, whether it was still "manually created" (i.e., without even Extenson Builder 1.5) and I copied the sources into a new Extension Builder project, or created in Extenson Builder 1.5 and converted to Extension Bulder 2.1, the Export to ZXP does not work. I see the compiler is creating a bin-release folder, then it disappears, and no ZXP is to be found. Since bin-debug no longer has all files in it like it used to, the ZXPPackager can't find what it's looking for and can't make a ZXP - so I am stuck.
Please - help!
I have an update, and would greatly appreciate anyone's help:
Upon further investigation, the issue is not the Extension itself (regardless of whether it was created newly in EB2.1, in EB1.5, or created "manually" by building my own manifest, etc.).
The issue is that there are two library projects whose inclusion as project referennce in any Extension Builder project (regardless of whem/how it was created) causes the EB project not to produce a ZXP file using the Export wizard.
I tried deleting the 2 library projects, creating them anew empty - and they could be referenced successfully. I added back all the source files and this solved the problem, as of yesterday. Today, I tried building the ZXPs again, and it stopped working. I should mention that it appears that when the Export did work, it seemed to be changing the referenced project somehow. I noticed that they were given .mxi files, which I thought should not be created for a non EB project.
I should add (i'm about to post a seperate discussion) the Flash Builder error log is giving me a ton of Eclipse errors for many actions. Is this "normal"? By that, I mean is everyone getting those warnings and errors?
All help greatly appreciated.
And the plot thickens: An attrociusly ugly workaround -
If I remove the problematic projects from the workspace, move them to another workspace, and then have the EB Projects from the first workplace access those problematic projects' SWC, then the Export Wizard works.
Anyone have a better idea? Could this be because we're still in the trial period?
I'd appreciate hearing from Adobe staff.