https://github.com/unic/aem-maven-plugin

A maven plugin for working with local and remote Adobe AEM instances
https://github.com/unic/aem-maven-plugin

aem aem-maven-plugin maven maven-plugin

Last synced: about 2 months ago
JSON representation

A maven plugin for working with local and remote Adobe AEM instances

• Host: GitHub
• URL: https://github.com/unic/aem-maven-plugin
• Owner: unic
• License: apache-2.0
• Created: 2018-12-10T23:11:47.000Z (about 6 years ago)
• Default Branch: master
• Last Pushed: 2023-08-07T09:23:00.000Z (over 1 year ago)
• Last Synced: 2024-04-16T07:55:49.032Z (9 months ago)
• Topics: aem, aem-maven-plugin, maven, maven-plugin
• Language: Java
• Homepage: https://unic.github.io/aem-maven-plugin/
• Size: 481 KB
• Stars: 2
• Watchers: 3
• Forks: 1
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Unic Maven-AEM-plugin

A totally awesome plugin for working with local and remote Adobe AEM™ instances! This plugin allows installing, starting, stopping and killing AEM instances,

reliable deployment of CRX packages, validation of JCR content XML files and much more.

Please refer to [the project site](https://unic.github.io/aem-maven-plugin/) for the standard maven plugin goal documentation.

[![Maven Central](https://img.shields.io/maven-central/v/com.unic.maven.plugins/aem-maven-plugin.svg)](https://search.maven.org/search?q=a:aem-maven-plugin&g=com.unic.maven.plugins)

[![Travis](https://api.travis-ci.org/unic/aem-maven-plugin.svg?branch=master)](https://travis-ci.org/unic/aem-maven-plugin/) 

The plugins main design goals are:

* Speed: Both the AEM instance and the deployments are are configured for maximum performance, e.g. using generous auto save thresholds and memory settings

   or omitting the installation of sample content

* Stability: Starting, stopping and deploying AEM instances is not trivial and requires extensive handling

  of the various state transitions the system exhibits. The plugin attempts to handle all of these situations. 

* Non-verboseness: Only show meaningful and concise log messages to the user

* Simplicity: The plugin configuration shall be self-explanatory. Each configuration option must be documented, i.e. every @Parameter annotation

  is documented, as this description is included in the plugin metadata and displayed in the IDE or when executing the help MOJO.

## Usage

See [official plugin documentation](https://unic.github.io/aem-maven-plugin/).