You are here

What's new?

New features in the Alfresco SDK.

What's new in Alfresco SDK 3.0

  • Support for Alfresco 5.2
  • JAR packaging
  • AMP packaging as an assembly
  • Improved compatibility - compatible with Alfresco One 4.2.7, 5.0.4, 5.1.2, 5.1.3, and Alfresco Content Services 5.2.x.
  • Easy upgrades - simply change the alfresco-maven-plugin version to upgrade the SDK
  • No forced parent POM
  • All run and integration testing logic moved to the Alfresco Maven Plugin
  • Integration testing directly on running repositories
  • Simplified archetypes
  • Hot reloading via HotSwapAgent or JRebel

What's new in Alfresco SDK 2.2.0

  • Support for Alfresco 5.1
  • Alfresco REST API Explorer is now available with the run profile (http://localhost:8080/api-explorer)
  • All-In-One AMP module names and ID now includes AIO name to make them unique
  • Aligned Module version with Artifact version - 5.0 and 5.1 supports SNAPSHOT versions in module.properties
  • Numerous bug fixes. See the release notes for details.
  • Issues: you will have to run without Spring Loaded with AIO and Repo AMP, only works with Share AMP at the moment.

What's new in Alfresco SDK 2.1.1

  • Reintroduce support for Java 7
  • Numerous bug fixes. See the release notes for details.

What's new in Alfresco SDK 2.1

  • Support for Solr 4
  • Regression testing Share Webapp with Alfresco Share Page Object (PO) tests
  • Functional testing of Custom Pages with Alfresco Share PO
  • Rapid Application Development (RAD) improvements:
    • New alfresco:refresh-repo goal for alfresco-maven-plugin for automatic refresh of repository (alfresco.war)
    • New alfresco:refresh-share goal for alfresco-maven-plugin for automatic refresh of Share (share.war)
  • Automatic JavaScript compression
  • Custom package name can be used when generating projects
  • Records Management profile 'rm' removed, now included as other AMPs in the repository and Share WAR POMs
  • Run script for Windows now available (run.bat)
  • Upgraded to Alfresco Community Edition 5.0.d and Enterprise 5.0.1 (JDK8)
  • Fixed DB initialization error (dbObject cannot be null)
  • Fixed blank Admin Console bug

What's new in Alfresco SDK 2.0

  • Support for Alfresco 5.0
  • Name changed from Maven Alfresco SDK to Alfresco SDK.
  • New Share AMP archetype.
  • RAD in Eclipse and IntelliJ.
  • Now requires Maven 3.2.2
  • RAD with Spring Loaded.
  • Support for JRebel has been deprecated.
  • Introduction of enterprise profile option -Penterprise.

What was new in Alfresco SDK 1.1.1

  • Bug fixes.

What was new in Alfresco SDK 1.1.0

  • Runs in Tomcat7 (replaces Jetty)
  • Remote running of JUnit
  • JRebel integration
  • Improved IDE integration

What was in Alfresco SDK 1.0.x

  • Use of Alfresco POMs
  • Relied on a number of components:
    • The SDK parent POM providing full Alfresco project lifecycle feature, to be added as a <parent> in your projects
    • Archetypes like the AMP or all-in-one providing sample project to kickstart your Alfresco development and boost it with best practices
    • The Alfresco Maven Plugin to manage AMP packaging and dependencies
    • Alfresco Platform Distribution POM can (optionally) be used to provide centralized <dependencyManagement> on a particular Alfresco version / edition (Community Edition / Enterprise)
    • The Alfresco Artifacts Repository provides backing for this SDK. Check the Alfresco Wiki for Community Edition / Alfresco One access information
  • Embedded Jetty server and H2 database

What was in Maven Alfresco Lifecycle

  • First implementation of Alfresco Maven SDK (Now deprecated)
  • No use of Alfresco POMs
  • Available archetypes and plugins:
    • maven-alfresco-extension-archetype to create WAR packaged webapps that can provide all Maven lifecycle and features
    • maven-alfresco-share-archetype to create and manage Alfresco Share customization webapps
    • maven-alfresco-share-module-archetype to create and manage Alfresco Share custom dashlets, pages as JARs
    • maven-alfresco-amp-archetype to create maven-amp-plugin managed web apps, which can provide all Maven lifecycle and features to Alfresco modules. The maven-amp-plugin is also used as a replacement to MMT to unpack AMPs into WARs builds, using the Maven dependency mechanism provided by the maven-amp-plugin
  • Embedded Jetty server and H2 database to run Alfresco or Share
  • Possible to use Maven standard dependency management to pull in AMPs in your build
  • Further information