directory env contains only environment specific files
As a result, sub-projects underapp responsibilities are only wired with building artifacts.
Environment sub-project sets up AEM local instances (author & publish) and could set up other services based on Docker (e.g AEM dispatcher on CentOS).
These 2 directories could be used separately. After generating project, app or env directories could be deleted or extracted to separate Git repositories.
As of contents of app directory was generated from Maven archetype, corresponding pom.xml files could be recovered. In that way, the project could support dual-build (Gradle & Maven).
Maven supported in case of Adobe Cloud Manager compatibility and Gradle in case of quick powerful build and capability of setting automatically local AEM environments.
Changes:
appcontains structure generated from https://github.com/adobe/aem-project-archetypeenvcontains only environment specific filesAs a result, sub-projects under
appresponsibilities are only wired with building artifacts. Environment sub-project sets up AEM local instances (author & publish) and could set up other services based on Docker (e.g AEM dispatcher on CentOS).These 2 directories could be used separately. After generating project,
apporenvdirectories could be deleted or extracted to separate Git repositories.As of contents of
appdirectory was generated from Maven archetype, correspondingpom.xmlfiles could be recovered. In that way, the project could support dual-build (Gradle & Maven). Maven supported in case of Adobe Cloud Manager compatibility and Gradle in case of quick powerful build and capability of setting automatically local AEM environments.