adobe-ccp-recipes
adobe-ccp-recipes copied to clipboard
autopkg
Autopkg recipes for Creative Cloud Packager workflows
Which is already available in self.env['version']
_From @timsutton on July 28, 2017 16:18_ Adobe's officially-documented way to build a package containing only the CCDA is to build a package with nothing selected in the UI. It...
Because of this: https://feedback.photoshop.com/photoshop_family/topics/lightroom-version-numbers-cfshortbundleversionstring LightroomCC ends up with a useless %version% output from CreativeCloudVersioner.py (eg: `Adobe Lightroom CC [20180608-0705-e1ba7c8]`). Would you be interested in special-casing it in the versioner so...
Lightroom and Lightroom Classic contain a string of the following form in CFBundleShortVersionString: `Adobe Lightroom CC [20180608-0705-e1ba7c8]` this isn't useful for packaging purposes, though arguably the bit in square brackets...
_From @timsutton on May 23, 2017 20:8_ Not yet sure how much in demand this would be: an option for not "installing" the CCDA, at least for serialized or device...
As in Issue #16 described, the variable elf.env["package_info_text"] gets the wrong encoding. This change checks the encoding and decode it to UTF8 if necessary.
Hi, I'm stuck. If I try to get the German (de_DE) version I'll get following errormessage. ``` CreativeCloudApp_OR.jss.recipe Error in local.jss.CreativeCloudApp_OR: Processor: CreativeCloudPackager: Error: 'ascii' codec can't decode byte 0xc3...
_From @cwhits on June 15, 2017 17:39_ I have most recipes requesting release notes and the recipe will fail when they're not available. Since it's just release notes, it should...
Allow the user to provide a display_name string that prevents CreativeCloudVersioner from overriding it #10
Recipes fail to build with a version that's not the `BaseVersion`. It looks like the only way around this now is to build packages for the base version and set...
