aem-project-archetype Bundle 'core' provided to instance only by 'all' package

Bundle 'core' provided to instance only by 'all' package

Open pun-ky opened this issue 3 years ago • 2 comments

Expected Behaviour

Sequential deployment of packages "ui.config", "ui.apps", "ui.content" installs "core" bundle. Recovering behavior that was available in Archetype 24.

The problematic change found: https://github.com/adobe/aem-project-archetype/pull/476/files#diff-25625d5eb7f3c9dc5d84ccc50050962e50bdee02a9645e98d51751dd11c7b2abL69 So that I am not sure if it was intended, I mean the consequences :)

Actual Behaviour

Behavior not present in the actual archetype. To provide "core" bundle is needed to use "all" package. Previously - in archetype 24 there were available both options. Deploying packages separately or by "all" package.

Reproduce Scenario (including but not limited to)

Build and deploy packages "ui.config", "ui.apps", "ui.content" one after another. See that application is not working because OSGi bundle core is missing.

Background

Gradle AEM Plugin offers to build users the incremental AEM build (based on partial Maven build execution combined with Gradle caching) and increment AEM deployment (based on comparison of local build checksum with checksum stored on AEM instance) which effectively improves development experience. Such capability could be added to the AEM build by using so-called GAP launcher. However, it was working nicely till archetype 24. Since archetype 25, that build improvements stopped working and moreover does not longer make sense because deploying AEM application using separate packages to the AEM is not reflecting the deployment when "all" assembly is used. AEM deployment ends in a different state - AEM application is not working.