A week or so ago Alfresco released version 3.0.0 of their Maven-based SDK. The release was pretty significant. There are a variety of places you can learn about the new SDK release:
- The official documentation discusses what’s new.
- Martin Bergljung wrote a guide here. (Why Google Docs? No idea. Maybe this is a draft?)
- The SDK project on Github
I recently revised all of the Alfresco Developer Series tutorials to be up-to-date with SDK 3.
Upgrading each project was mostly smooth. The biggest change with SDK 3.0.0 is that the folder structure has changed slightly. At a high level, stuff that used to go in src/main/amp now goes in src/main/resources. These changes are good–they make the project structure look like any other Maven-based project which helps other developers (and tools) understand what’s going on.
I did have some problems getting the repo to build with an out-of-the-box project which I fixed by using the SNAPSHOT rather than the released build.
Support for integration tests seems to have changed as well. I actually still need to work that one out.
Other than that, it was mostly re-organizing the existing source and updating the pom.xml.
A small complaint is that the number of sample files provided with the SDK has grown significantly, which means the stuff you have to delete every time you create a new project has increased.
I understand that those are there for people just getting started, but no one, not even beginners, needs those files more than once, so I’d rather not see them in the main archetype. Maybe Alfresco should have a separate archetype called “sample project” that would include those, and configure the normal archetype as a completely empty project. Just a thought.
The new SDK is supposed to work with any release back to 4.2 so you should be able to upgrade to the new version for all of your projects.