Release 2.0.0

⭐ New Features

• Added the default Sling OSGi Installer as deployer implementation. This allows you to simply upload your packages or bundles to some */install location in your JCR repository and the OSGi Installer picks them automatically for installation. This mechanism can be a much more stable deployment approach for some applications or if you use Apache Sling only (not AEM). See #49
• Added support for cleaning up several repository paths after uninstallation. This is useful to make sure that all your paths are removed properly, see #51

↗️ Dependency Updates

• Several libraries have been updated: Kotlin, etc.

Release 2.0.0-rc.2

This release comes with a fixed retry handling and an improved console log output, which is less verbose and more focused, see #47

Release 2.0.0-rc.1

First release candidate for the new Sledge version.

The new major version comes with a fully rewrite of Sledge which focuses on providing a simple command-line tool to deploy CRX packages to an AEM instance.

Currently it only supports the deployment via the CRX Package Manager, therefore it can't be used for pure Apache Sling applications.

Use the "*-all.jar" binary to use the tool out of the box, no need to install any other dependencies.

v0.6.1

This release includes simply a small improvement for the Deployer module.

• e4c709e Improves the deployment stability by first uninstalling config packages and afterwards the app packages. This should prevent corrupt deployments which contain a Sling Rewriter config

v0.6.0

This release fixes issues with Sling 10 and AEM 6.3 and improves the overall code base.

This release supports now AEM 6.1+ and Sling 9+.

Improved

• Extend the deployer script such configuration packages can also be deployed via this mechanism and can be removed from the Sledge application package to have a better control over the installation order. Best practice should be that the Application package only contains needed bundles and content packages for the application itself. The configurations should be deployed separately depending on the environment. This allows more flexibility during deployment and depending on the requirements of the application.
• #28 / #38 Use new slingstart Maven plugin with Sling 10
• #39 Fix issues with AEM 6.3, refactor Application Package model

v0.5.3

Improved

• #36 Added the possibility to set the wait count and time for the package installation

v0.5.2

Improved

• #34 Changes the slf4j simple logger to System.out to not output log messages as errors in general

v0.5.1

Improved:

• The bundles check procedure will catch properly the JsonException (#33)

Sledge v0.5.0

Improved:

• The bundles check result can be ignored if it is not relevant for a current deployment (#32)
  • Just use the option ignoreBundlesCheckFail for the deploy script, default is true. If you want that the deploy script stops if the bundles check fails then set it to false

Sledge v0.4.1

Fixes:

• Fixed wrong package uninstallation handling (#30)