#Jrebel remoting how to#
#Jrebel remoting update#
#Jrebel remoting upgrade#
#Jrebel remoting full#
#Jrebel remoting software#

#Jrebel remoting software#

There are a number of software requirements for using Alfresco SDK 4.1: Use these instructions to get started with using Alfresco SDK 4.1. Support for Alfresco 6.1.xĪlfresco SDK 4.1 provides support for Alfresco 6.1.x.

#Jrebel remoting full#

By doing so, the integration testĮnvironment can be more similar to a real one, including whatever other service is required for a full featured integration test execution. In this version, the integration tests are run against the dockerised environment defined using Docker and Docker compose. However, the inclusion of Docker and the utility scripts provides a different perspective about the environment on which the integration tests are executed. The integration tests and the mechanisms to execute them in an Alfresco Content Service instance remains the same as in the previous version of the SDK.

#Jrebel remoting how to#

How to work with AMPs, please visit Working with AMPs. The Alfresco Maven Plugin is only required in those cases in which it is required to package the customization project as an AMP. But, if any development team has a requirement or a development process that requires a customization in the project development lifecycle, it isĮasy to modify the utility scripts, the Docker files or the Docker compose descriptor to adapt the SDK projects to their needs. If a development team has straightforward requirements and doesn’t want to worry about the complexity of working with containers, it can use the utility scriptsĪs they are. That avoids the need of using the Alfresco Maven Plugin and eases the process to modify the lifecycle of the customization projects.

Alfresco Maven Plugin no longer neededĪlfresco SDK 4.0 manages the lifecycle of the generated projects making use of proper utility scripts That incredibly eases the management of the versions of the different Alfresco platform’s dependencies required in a customization project. It is still needed to define dependencies in the POM files, but the version can be omitted as it’s The inclusion of the BOM dependency in the dependencyManagement section of the pom.xml file of the projects generated using the archetypes imports allĪrtifacts in the selected Alfresco platform version. The configuration of the Maven dependency management has been greatly improved thanks to the addition of a bill of materials (BOM). The Apache Maven plugins included in the archetypes has been updated to avoid any issue with Java 11. Now use SDK 4.0 + JDK 11 to work on them.

This way, if you’re working as a developer in customizations for Alfresco 6.1 you must Support for this version of the Java platform.Īlfresco SDK 4.0 has been modified to add support for Java 11 as well. Java 11 is the next Long Term Support (LTS) version that provides support for 3 years. Working with Docker images gives the developers the opportunity to easily customize the deployment of the local environment to adapt it to their requirements.Īdding, removing and configuring services in the environment is as easy as modifying the Docker compose descriptor file. To offer a solution aligned with the architectural decisions made in Alfresco for version 6: moving towards microservices-oriented Specifically, the new SDK is highly based The main change included in SDK 4.0 is the addition of container technologies. This is a mayor release oriented to support Alfresco 6, so it is not compatible with previous versions of the SDK. What’s new?Īlfresco SDK 4.0 brings some changes oriented to assist the way the customizations are built, packaged, run and tested for Content Services 6 and

#Jrebel remoting upgrade#

If you have existing projects that you wish to upgrade to SDK 4.1.x, the recommended approach is to generate a new projectįrom our archetypes and move your code into place. This new release is not directly compatible with the previous releases of the SDK. The 4.0 release takes advantage of Semantic Versioning ( SEMVER), which means that

#Jrebel remoting update#

If your version is in Limited or Full Support and you need help, contact our Support team.Īlfresco SDK 4.1 is a minor update to the SDK and provides support for Alfresco 6.1.x. Please check the Alfresco SDK Support statusįor the version you’re using. This enables Rapid Application Development (RAD)Īlfresco SDK 4.1 is released under Apache License version 2.0Īnd supports Content Services both in Community Edition and Enterprise Edition. It is based on Apache MavenĪnd Docker and is compatible with major IDEs. The Alfresco Software Development Kit (Alfresco SDK) is a fundamental tool provided by Alfresco to developers to buildĬustomizations and extensions for the Alfresco Digital Business Platform. With this SDK you can develop, package, test, run, document and release your Alfresco extension project. Alfresco SDK 4.1 is a Maven based development kit that provides an easy to use approach to developing applications andĮxtensions for Alfresco.