New Tutorial: Getting Started with the Alfresco Maven SDK

I’ve written a new tutorial about Getting Started with the Alfresco Maven SDK. I hope it helps newcomers to Alfresco get started writing customizations quickly. And if you are an experienced Alfresco developer who still uses Ant-based builds, I hope it motivates you to make the switch to Apache Maven.

The Alfresco Maven SDK is the preferred way to bootstrap, manage, and build your Alfresco modules. The cool thing is that you don’t need anything to get started–if you already have a JDK and Apache Maven installed, you are ready to write custom Alfresco modules for the Alfresco repository and Alfresco Share, whether you are using Community Edition or Enterprise Edition.

The tutorial itself is an HTML page on this site, but I wrote it using Markdown. It lives in a GitHub repository, along with my older tutorials on custom content types, actions, behaviors, web scripts, and advanced workflows. Those tutorials have also recently been converted to Markdown and the accompanying source code has been refactored to use the Alfresco Maven SDK and AMPs, but I am still busy revising the tutorial text to match the refactored code.

I hope that by writing these tutorials in Markdown and storing them in GitHub the Alfresco community will be more likely to help me maintain them over time by forking the repository and sending me pull requests.

22 comments

  1. Ed says:

    Great tutorial, thanks!

    Note: I think Alfresco Maven SDK uses Jetty as embedded servlet container, not Tomcat.

  3. Steve G says:

    When I execute integration-test/amp-to-war I was expecting to see the log messages generated by the DemoComponent class when the module is first executed (e.g., “Test debug logging. Congratulation your AMP is working”). I cannot find where those message are captured. The Demo class msg appears in the console just fine. I set executeOnceOnly=”false” in the context file. I also tried to install the demo AMP in Tomcat and I had the same result, Demo class msg appears, but not the DemoComponent messages. Any ideas? Thanks

  4. Steve G says:

    The DemoComponent class is not executing because the appliesFrom and since version are set to 2.0 in the sample, but Maven generates a 1.x as the module.version in the module.properties. I changed the versions in service-context.xml to 1.0 and the message started to appear in the log.

Comments are closed.