search

wcm-io / io.wcm.maven.aem-global-parent

Global parent for Maven artifact hierarchy for AEM projects.
Apache License 2.0
0 stars 0 forks source link

Download goal: No renditions are included, but AEM publish does not trigger update_asset workflow to create them #13

Closed henrykuijpers closed 6 months ago

henrykuijpers commented 1 year ago

https://github.com/wcm-io/io.wcm.maven.aem-global-parent/blob/4b08ec3a5fbcb047f24381f288575cdcc3dea7ac/pom.xml#L418

This makes sure to not include renditions in the SCM, which is of course very nice to have. When installing the package on the author environment, the renditions are automatically created because of the update_asset workflow launcher.

However, this launcher is only active on author (runmodes=author), due to which the assets will not have any renditions on the publish environment.

When activating assets from the author environment to the publish, the asset including all metadata & renditions will be activated to the publish environment.

In the end, it causes the assets to be available in the author environment with renditions, and available without renditions in the publish.

@stefanseifert How are you handling this "feature" in your projects? How do you make the renditions available in your publish environment as well?

henrykuijpers commented 1 year ago

Any thoughts on this?

stefanseifert commented 1 year ago

the mentioned line excludes only some of the auto-generated renditions, namly all the cq5dam.thumbnail in the name. this should by only those generated for usage in the author UI itself, usually those should not be used on live website? if you are actively using those on publish, you should probably remove that exclude and overwrite the "excludeFiles" section.