AD0-E136 · Question #99
Which tool is commonly used for managing dependencies and building projects when setting up local SDKs for AEM Cloud?
The correct answer is C. Maven. Maven is the standard build and dependency management tool for AEM (Adobe Experience Manager) Cloud projects because AEM is a Java-based platform built on the OSGi framework, and Maven's POM-based project structure aligns directly with how AEM archetypes, bundles, and packages…
Question
Which tool is commonly used for managing dependencies and building projects when setting up local SDKs for AEM Cloud?
Options
- Anpm
- BGrunt
- CMaven
- DGulp
How the community answered
(29 responses)- B3% (1)
- C90% (26)
- D7% (2)
Explanation
Maven is the standard build and dependency management tool for AEM (Adobe Experience Manager) Cloud projects because AEM is a Java-based platform built on the OSGi framework, and Maven's POM-based project structure aligns directly with how AEM archetypes, bundles, and packages are structured and deployed.
- npm (A) is a JavaScript/Node.js package manager - while it may appear in AEM frontend builds, it does not manage the core Java/OSGi dependencies that AEM SDK setup requires.
- Grunt (B) is a JavaScript task runner, used occasionally for frontend automation but irrelevant to Java dependency management or AEM SDK provisioning.
- Gulp (D) is another JavaScript task runner/build tool - same category as Grunt, not applicable to Java/OSGi project dependencies.
Memory tip: Think "AEM = Adobe Enterprise Maven" - enterprise Java platforms standardize on Maven, and AEM's own documentation and project archetypes (aem-project-archetype) are Maven-first by design.
Topics
Community Discussion
No community discussion yet for this question.