Using with Maven
If you’re using the Content Package Maven plugin, take these two easy steps:
Step 1: Add ACS AEM Commons as a Dependency
<dependencies> section of your content project’s pom.xml file, add this:
For 6.2 and 6.3
For 6.0 and 6.1
ACS AEM Commons has two distributions:
- The ‘‘full’’ package which includes all functionality.
- The ‘‘min’’ package which excludes functionality requiring 3rd party dependencies.
Currently, the only feature excluded from the ‘‘min’’ package is the Twitter integration.
To include the ‘‘min’’ package, add
To include the ‘‘full’’ package, don’t provide any
<classifier> element inside the
Step 2: Add ACS AEM Commons as a Sub Package
Then, (while still in the content project’s pom.xml) within the configuration of the
content-package-maven-plugin, add a
Step 3: Add ACS AEM Commons Bundle as a Dependency (Optional)
<dependencies> section of the pom.xml any maven projects that use ACS AEM Commons APIs (Java utils, TagLibs, etc.), add the dependency for the
acs-aem-commons-bundle project. The
acs-aem-commons-bundle will deployed as part of the
acs-aem-commons-content package (above), however the dependency is required to compile your project when it uses ACS AEM Commons Java APIs.