I'm pleased to announce the availability of SDK 4.0 and 3.1.
The artifacts have been released to Maven Central. It might be a few days until the global archetype catalog updates, but read on for more details on how to get started today!
This release will enable developers to extend and customize Alfresco Content Services 6.0 and 6.1. In addition, the SDK 3.1 release brings a number of bug fixes as well as a few highly requested features.
SDK 4.0 is only compatible with ACS 6.0 and 6.1.
If you wish to extend and customize ACS 5.2 or older, please use SDK 3.1.
SDK 4.0 brings changes to the underlying logic for running and testing your customizations. This means that the SDK now leverage containers to launch the full suite of Alfresco Content Services. By leveraging Docker containers we make it easy to start additional services, such as Transform Service, Search Services and much more.
If you are already familiar with SDK 3.X you will feel right at home. We still offer the All-in-one archetype, as well as platform-jar and share-jar archetypes. The project structure changed slightly to accommodate for the Docker setup, and the pom.xml has changed.
Key changes and improvements:
Two new sub modules introduced for All-in-one: platform-docker and share-docker. These modules provides the required setup in order to extend the ACS Docker containers with your customizations
A new Docker folder contains a docker-compose.yml file. This file is filtered by Maven to easily enable switching between versions
SDK 4 no longer depends on the Alfresco Maven Plugin since all runner logic is moved to Docker
Full support for ACS 6.0 and 6.1, both Enterprise and Community
Submodules are now renamed to be prefixed with the project