Auto Install Package about aem-packager

[amclin]

That highly depends on how you are going from Maven to AEM, and makes sense when you're running the build on the same machine as the running AEM instance. Generally that's not a good practice (though I know a lot of teams do this). For example, for security purposes you don't need and shouldn't have NodeJS or any of your other dev dependencies installed on your running AEM app servers.

Handling the responsibility of when to install which package to which AEM App server is best delegated to an automation system designed to handle those kinds of operations:

• Jenkins
• Bamboo
• Travis
• Azure DevOps
  etc...

That way you have auditable logs, the ability to reconfigure or dynamically map which packages go to which servers in which order, status of deployments, blue/green/rolling deployments, etc.

[amclin]

Since installation management and pipelines is outside the scope of this project, I'm going to close this request.

I'm sure a maven wrapper can be written to go around the packages produced by this library, but it would be highly-specific to the environment, and not easily abstracted.

@VikashKotharyWork thank you for the suggestion!