Assuming the project was generated using the AEM Maven archetype, which Maven command triggers the build and deployment of a content-package to a publish instance?

Assuming the project was generated using the AEM Maven archetype, which Maven command triggers the build and deployment of a content-package to a publish instance?

• A. mvn install -PautolnstallPackage
• B. mvn install -PautolnstallBundle
• C. mvn install -PautolnstallPackagePublish
• D. mvn install deploy -Pmode=autolnstallPackage

Answer: (C)

Building and deploying a content-package to a publish instance with the AEM Maven archetype is controlled by a Maven profile that tells the plugin to package the content and push it through the AEM Package Manager to the target environment. When you run the install phase with the profile that includes Publish in its name, Maven creates the content-package and immediately deploys it to the publish instance, automating the end-to-end flow in one step. This is why using the profile that signals “auto-install package to publish” is the correct way to trigger both the build and the deployment to publish. Other options wouldn’t perform the same end-to-end action. A profile without the Publish part would typically target installation on another environment or just prepare the package without deploying to publish. A profile aimed at bundles deals with OSGi bundles rather than content-packages. And using the deploy lifecycle instead of install aligns with Maven’s normal artifact deployment to a remote repository, not with deploying an AEM content-package through the Package Manager.

Building and deploying a content-package to a publish instance with the AEM Maven archetype is controlled by a Maven profile that tells the plugin to package the content and push it through the AEM Package Manager to the target environment. When you run the install phase with the profile that includes Publish in its name, Maven creates the content-package and immediately deploys it to the publish instance, automating the end-to-end flow in one step. This is why using the profile that signals “auto-install package to publish” is the correct way to trigger both the build and the deployment to publish.

Other options wouldn’t perform the same end-to-end action. A profile without the Publish part would typically target installation on another environment or just prepare the package without deploying to publish. A profile aimed at bundles deals with OSGi bundles rather than content-packages. And using the deploy lifecycle instead of install aligns with Maven’s normal artifact deployment to a remote repository, not with deploying an AEM content-package through the Package Manager.