Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad ExtensionManifest version for CC 2015 #6

Open
vdeygas opened this issue Apr 4, 2016 · 2 comments
Open

Bad ExtensionManifest version for CC 2015 #6

vdeygas opened this issue Apr 4, 2016 · 2 comments

Comments

@vdeygas
Copy link

vdeygas commented Apr 4, 2016

Hi,

By relying on the Adobe-CEP resources, ExtensionManifest_v_5_0.xsd should be used for CC 2015 and v 6.0 for CC 2015.1

Thanks

@Jolg42
Copy link

Jolg42 commented Apr 4, 2016

Hi ;)

I'm interested of what developers are using for their manifest too…
Because I tried once to update my manifest version to 5.0 / 6.0 but the extension was not working on older versions of CC after that!
So in the end I'm stuck with 4.0 version to support all CC versions (From 17.0 to latest 19.2.1) because it seems that you can't provide multiple manifests with different versions in the packaged extension.
+ If you want to be compatible with all CC versions, I think staying on 4.0 is the best because I'm not gonna do a different build for each CC version 😱

What do you think about it here?

@vdeygas
Copy link
Author

vdeygas commented Apr 5, 2016

Hello,

I understand your compatibility constraint but, with manifest version fixed to 4.0, CEFCommandLine element isn't allowed. And with InDesign CC 2015, we need to pass "--enable-nodejs" param to use nodejs in an extension.

As my extension must support CC 2015 only (for now), I modify manifest.bundle.cc2015.xml to fix manifest version to 5.0.

Thanks for your reply

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants