We will continue to add new functionality and extra configuration options, but in a backwards compatible way. This means that no breaking changes within a major version. SDK 3.0 strives to follow SEMVER closely. *A small one line change is required in module.properties for 4.2.x support. See Switching Alfresco Content Services and Share versions for more. To change the version you want to test your customization against, change and along with. This provides much more flexibility in the supported versions.Īlfresco Content Services SDK 3 is compatible with Alfresco One 4.2.7*, 5.0.4, 5.1.2, 5.1.3, and Alfresco Content Services 5.2.x. One of the main motivators behind the improved Alfresco Content Services SDK 3 was to centralize run and integration testing logic in a plugin. This gives developers much more control over packaging and simple modules can easily be deployed as JARs. In SDK 3 everything is now packaged as a JAR by default, while the AMPs are still available as an optional assembly. Since the early days of the SDK, AMPs have been the way customizations were packaged. We will have a look at how you can add more custom modules to an All-in-One project, and more. This information provides more advanced topics that you might come in contact with when you have been working with an SDK project for a while. The Maven Alfresco SDK is designed to work well with Eclipse and IntelliJ IDEA.
0 Comments
Leave a Reply. |