Custom component development in Adobe Experience Manager Forms requires a correctly configured development environment and a project structure compatible with the target AEM deployment.
Adobe recommends using an AEM Maven Archetype project as the foundation for developing and deploying custom components. The archetype provides the required project modules, dependency management, repository structure, and build configuration.
Before component implementation and testing, developers should have a functioning local AEM instance with the appropriate Forms capabilities installed and their project successfully deployed.
Maven supports compilation, packaging, dependency resolution, and installation of project artifacts into the local AEM environment.
For example, Adobe documents the following deployment command for suitable archetype-based projects:
mvn -PautoInstallPackage clean install
This establishes a development environment in which custom components can subsequently be implemented, registered, deployed, and validated.
Option B references Package Manager, which is useful for inspecting and installing packages, but it does not replace the initial Maven-based development setup.
Option C incorrectly combines component preparation with page publishing. Option D treats the Felix Console as the primary project-deployment mechanism, which is not the recommended workflow.
Therefore, option A best represents the prerequisite deployment process for custom component development.
Official Adobe references:
Customize Adaptive Forms Core Components; AEM Maven Archetype Project Deployment
Submit