SOLVED
AEM Project Build & Deploy MVN Command Difference
1 Accepted Solution
Correct answer by
Hi
Overall, the maven profile just wrap configurations, so the best way to understand them is to look at the pom and check what configurations are available by each profile. Let me try to answer your question super quick.
-
"mvn clean install -Padobe-public". This command runs the clean and install phases using the profile 'Adobe Public', which behind the scenes utilizes the Adobe public repository to download Maven dependencies regardless of the repositories you may have declared in your .m2 file.
-
When you run 'mvn clean install', Maven will execute the configurations present in the POM file located at the same level where the command is executed. Therefore, it's important to note that the 'autoInstallSinglePackage' profile only exists under the 'all/pom.xml'. Essentially, both commands achieve the same result, so they can be used interchangeably.
-
Yes, this is the traditional command to deploy the code: 'mvn clean install -PautoInstallPackage'. Since this command is triggered from the 'root' POM, it will execute the pom from their children as well. This particular profile is used to indicate to the 'content-package-maven-plugin' where (i.e., which server) to install the packages generated during the build process.
This is a brief explanation. If you want to dive deeper, you can check the links below:
https://maven.apache.org/guides/introduction/introduction-to-profiles.html
Hope this helps
Esteban Bustamante
Correct answer by
Hi
Overall, the maven profile just wrap configurations, so the best way to understand them is to look at the pom and check what configurations are available by each profile. Let me try to answer your question super quick.
-
"mvn clean install -Padobe-public". This command runs the clean and install phases using the profile 'Adobe Public', which behind the scenes utilizes the Adobe public repository to download Maven dependencies regardless of the repositories you may have declared in your .m2 file.
-
When you run 'mvn clean install', Maven will execute the configurations present in the POM file located at the same level where the command is executed. Therefore, it's important to note that the 'autoInstallSinglePackage' profile only exists under the 'all/pom.xml'. Essentially, both commands achieve the same result, so they can be used interchangeably.
-
Yes, this is the traditional command to deploy the code: 'mvn clean install -PautoInstallPackage'. Since this command is triggered from the 'root' POM, it will execute the pom from their children as well. This particular profile is used to indicate to the 'content-package-maven-plugin' where (i.e., which server) to install the packages generated during the build process.
This is a brief explanation. If you want to dive deeper, you can check the links below:
https://maven.apache.org/guides/introduction/introduction-to-profiles.html
Hope this helps
Esteban Bustamante
