NEBA is available in two distributions, the flyweight core distribution, featuring all of NEBA's resource-to-object mapping and tooling, and
the spring distribution which contains the core distribution and the optional spring integration along with all spring bundles.
If you are getting started and do not plan to use Spring MVC, we recommend using the core distribution.
Both distributions are available via maven central.
The following ZIP file is a CRX package containing the NEBA core and API bundles.Download the AEM™ package for NEBA core 5.0.4
The following JAR file is an OSGi bundle installing the NEBA core and API bundles. Installing and activating this bundle installs these bundles. Uninstalling the delivery bundle uninstalls NEBA as well.Download the Sling delivery bundle for NEBA core 5.0.4
The following ZIP file is a CRX package containing both NEBA core, NEBA Spring and the runtime dependencies not provided by Sling, e.g. Spring and Gemini Blueprint.Download the AEM™ package for NEBA Spring 5.0.4
The following JAR file is an OSGi bundle installing both NEBA core, NEBA spring and the runtime dependencies not provided by Sling, e.g. Spring and Gemini Blueprint. Installing and activating this bundle installs NEBA and its runtime dependencies. Uninstalling the delivery bundle uninstalls NEBA as well.Download the Sling delivery bundle for NEBA Spring 5.0.4
NEBA is built using Maven. Core, API and delivery packages containing NEBA and it's runtime dependencies are available from maven central. For developing with NEBA, including the API in your project is all you need to do:
The CRX deployment package for Adobe AEM™ can be referenced like so:
Or the Sling deployment bundle like so:
To reference the NEBA Spring artifacts, simply add the "spring" classifier to the respective dependency, e.g.:or for Apache Sling:
In order to use Gemini Blueprint's annotation-based service injection available since NEBA 4.2.0, add the gemini-blueprint-extensions bundle to your dependencies:
Finally, in order to install NEBA using the Content Package Maven Plugin you may do: