Thank you Alfresco, a 2015 to remember. Welcome Symphony, for an unforgettable 2016

2015 has been full of changes. I love those years where life take major turns and it’s those years that, albeit overwhelming in nature, make life worth living.

Not only I married my wonderful wife Christine, in a dreamy location in my home country in Italy, not only I now have a dog, the first pet in my life (yes a pet picture on this blog!),  but as most of you should know by now, I left Alfresco at the beginning of December 2015.

As you might imagine, it’s been a bittersweet choice, after almost 9 years working on the product, as Partner, SE, Principal Consultant, Global Manager and finally Senior Product Manager for the part of the product I cared the most about, the Developer Platform.
I can’t wait to see 5.1 out in the wild, as a culmination of all the efforts and investments that I & we (people like Ole, Maurizio, Samuel, Martin, Bindu and so many others in the Alfresco ecosystem) have put in the fidelity of the APIs and the general simplification of the developer experience.

There would be too many people to thank for these 9 years, and I’ll probably dedicate a separate post for that. Nevertheless you know who you are, and I deeply thank you for the trust, patience and opportunities you gave me. It’s been an honor. I will continue to be part of the Alfresco Community, in quality of Founder of the Alfresco SDK and continue to cheer for the team, as I think Alfresco is going to continue disrupting the market of ECM and BPM.  Go team Alfresco, I’ll be cheering from the sidelines!

As 2015 and Alfresco are now things of the past, I am proud and honored to announce that I have accepted the position of Executive Director for the Symphony Software Foundation. I will be soon relocating to Palo Alto, California to build a strong and open source ecosystem around the Symphony communications software.

The challenge is big, and equally worthy and exciting: create an open source ecosystem & open API strategy, where major financial services in the world can collaborate and contribute in a standard way, fostering fast innovation, so much needed in the FinTech world.  Some background herehere and here.

All of this, under the laws of open source governance, proven to be successful by examples like OpenStack, CloudFoundry and Open Daylight.

I am digging in this new challenge and I’ll be talking to many peers in the industry and from my open source network over the next months. I will need everyone’s suggestions and advise, so please reach out to me at gabriele at apache org or gab at symphony dot foundation. Also, getting a free account on Symphony and check often are great first steps to follow closely and provide input on the community we’re building.

Thanks everyone for the support and love you showed in 2015. Now onto a memorable 2016, to step even further out of our comfort zones! 🙂


How Alfresco is powering the ECM industry transformation and move to a cloud powered digital Enterprise – Introducing the Alfresco SPK
ECM in the Cloud

The move to cloud is happening, and to be fair ECM has been one of the most lagging businesses to finally take the leap and seriously look into the new delivery models (XaaS) the cloud opens up.

Metrics are off the roof, all the indicators part of the global intel we gather from customers, partners and prospects point in one direction: the future of ECM, like any other enterprise information system, is rapidly moving to cloud, and AWS is driving the space.

SaaS, PaaS, IaaS and company are growingly looked at as major IT optimization factors and concerns over data security are being fast overcome. And this is happening much more rapidly that you’d think and that was predicted just 12/24 months ago. Even in large organization, typically in “closed” vertical, often lagging from technology advancement standpoint.

At Alfresco, we are heavily investing in providing a seamless unified content platform which will ubiquitously enable the deployment of your ECM solutions on premise or on cloud (private, public, hybrid), leveraging natively cloud scale and availability features to power mission critical massive content repositories.

But what’s driving this transformation? In other words, from a customer standpoint, what the key drivers that are increasingly driving customers to choose cloud as a primary ECM deployment vehicle?

Scale (and elasticity) is definitely a key driver. You might have recently read about our joint effort with Amazon that ingested, processed and served 1B documents on an Alfresco instance running on AWS (EC2 + Aurora). As you can appreciate in the technical details of this benchmark, Aurora as a super-scalable database and the flexibility of growing up to 20 Solr shards + 10 Alfresco instances were the key winning factors, validating the choice of basing this benchmark on a flexible and scalable infrastructure like AWS and be able to leverage native features like availability and auto-scaling.

But the most compelling reason remains optimization of the IT processes and the mirage of handing off  maintenance of thicker and thicker layers of the stack to 3rd party providers. While this is not exactly big news (see this post from 2 years ago), especially with the flourishing plethora of DevOps tools to automate provisioning (Chef, Puppet, Ansible, Salt, etc.), orchestration (Kubernetes, Terraform, etc) and more in general the whole Dev -> Ops workflow with immutable containers (Docker, Unikernels, etc), organizations are quickly realizing the end to end benefits of a cloud strategy that starts from the bottom layers of the stacks to rapidly become pervasive and drive to the outsourcing of shared services, application layer, even application development itself and some of the back office processes.

At Alfresco, we are very aware of this movement and real life customer requirements springing off the DevOps movement, and so we have focused our efforts to provide an answer to our customers, partners and community members trying to deploying even growing and arbitrarily complex architectures seamlessly in Cloud and On premise, with native support for virtualized environments and containers.

As an initial deliverable and project to follow, less than 2 weeks ago at the Alfresco Day Roma, we have launched a community preview of the Alfresco SPK (Software Provisioning Kit), a toolbelt for the Alfresco admins and DevOps (much like the alfresco-sdk for Developers), which constitutes a common layer to easily provision Alfresco instances and stacks, either from scratch or starting from pre-existing images, based on pre-existing and commonly used DevOps technology like chef, Vagrant, Packer and virtual image formats (AMIs and Docker to start with). I want to give kudos to our DevOps department and especially Maurizio to have patiently worked with me to convey our internal DevOps experience into a customer facing tool. The SPK is hosted on Github and it’s a 100% community open source effort, so we welcome your feedback!

The SPK constitutes the first key building block to enable a set of very real customer use cases:

  1. First and foremost, provide a modern way of consuming Alfresco software, in the form of immutable pre-baked instance templates (see OOTB) which can be configured by the customer and composed in arbitrarily complex stacks (OOTB or customer define) that can then be ran in your favorite cloud and orchestration system (currently AWS and Cloud formation)
  2. Allow more advanced customer DevOps departments to consume Alfresco software and build images from scratch, to produce stacks that can be then packaged in the virtual format of choice (AMI to start with, Docker later)
  3. Enable the immutable container driven (e.g. via Docker) extended Developer workflow, to allow building of reliable and repeatable stacks locally and remotely, and enable Alfresco to take part to modern processes of continuous delivery and leverage cloud scalability / failover capabilities natively

Maurizio has put together a thorough presentation for the Alfresco Day which describes all the features and current state of the SDK.  You can find it below and we welcome your feedback.

NOTE: While it can work with Alfresco Enterprise, the Alfresco SPK is currently in Community Preview, which means it is NOT supported by Alfresco.

So currently we are looking for feedback and validation, rather recommending than leveraging this tool in production (use at your own risk!).

We are working on a more solid timeline for an EA (Early Adopter) and the GA (General Availability), so stay tuned!

Take your Alfresco productivity to the next level with the Alfresco SDK 2.1.0

As a first tangible result (first relase out!) in my new role in Alfresco Product Management and of the renewed investment Alfresco is putting in the developer platform, developer services and communications, no more than 5 months later than the 2.0.0 release, I am pleased to announce that the Alfresco SDK 2.1.0 is now released and available in Maven Central.

Many thanks go to Martin, for bringing new life to the Alfresco Developer Platform team and to Ole for stepping above and beyond his Developer Evangelist role and help tie up the release. Kudos also to Community members like Bindu who helped with testing and feedback.

This release works for Community and Enterprise (fully supported by Alfresco) and it shows strong signs of our cross-department (Dev, Product, Docs, Support) effort on a much more seamless and productive developer experience for our beloved ecosystem out there.

Here are the full release notes, but let me give you a couple of highlights:

  1. First off, building on the SDK 2.0.0 Spring Loaded approach, we have completed the effort for a full hot reloading experience, both for Alfresco and Share. Until more fixes go in product, we have introduced for this purpose a couple of plugin goals in the alfresco-maven-plugin, which are automatically invoked (or you can manually do that) to refresh webscripts on Alfresco and Share. If you are using your Eclipse, this should happen automatically on save, for IDEA you might night a bit of manual configuration. See RAD (Rapid Application Development) documentation for details.
  2. The SDK now supports Solr4 in the All-in-One archetype: this was the top-most requested issue in 2.0.0, so I am glad we got that out!
  3. In an effort to deliver higher and higher quality extension, we have introduced support for functional and regression testing, leveraging the Selenium based share-po library, which we use internally at Alfresco to perform black box testing. For details, here’s the issue and command details on how to regression test your customizations.
  4. Thanks to Martin and the Docs team  have fully re-written and improved documentation for the SDK 2.1.0  and we also started properly versioning docs for all SDK supported versions (e.g. see 2.0.0 docs)
  5. The SDK is an officially supported Alfresco product as of 1.1.1, but the SDK 2.1.0 marks an important step towards a much more predictable, supported, sustainable development support on the SDK. From now on, you can check the Product Support Status to verify the support status of the SDK and also, if you are an Enterprise customer, engage with Developer Support to get Dev savvy engineering help you on Development matters

I do hope you guys enjoy the new SDK and I am eager to collect feedback, via comments to this post, forums or you can reach out to me or Ole, as well as raise issues in the SDK project.

Handing my baby, the SDK, off :)

One more service announcement: as followers of this blog, you know I have always used this channel to announce SDK news and releases. While I’ll keep posting on SDK usage tips and more in general on my visions on the Alfresco Developer Platform directions, I think it’s time to hand off the baby and in line with the full Alfresco (“the company”) support for the SDK, move all communications to the Alfresco Developer Blog.

In particular, our Developer Evangelist is going to play a key role in keeping you updated and collecting feedback on our development experience.

So stay tuned on our Dev Blog, as Ole will soon post a more comprehensive update on this release.

Alfresco SDK 2.0.0 is (finally) out! Merry XMas Alfresco Devs :)

Christmas according to JoyOfTech

I could not possibly hold onto this anymore. After about 3 months of very caring testing of the Community, nurturing, launches, 4 betas and 2 Release Candidates, it’s with extreme pleasure that I can finally announce the so much awaited (and hopefully the best to date) Christmas present for all Alfresco developers out there: the Alfresco SDK 2.0.0 is now released and available in Maven Central!

Here all the details for this release:

Apart from some major internal refactoring to simplify POMs, maximize OOTB cross IDE (tested with Eclipse Luna and IDEA) compatibility and improve performances, key features for this release include (but are not limited to):

  • All Alfresco SDK 2.0.0-beta-4 features, including hot Java code reloading, native IDE integration, a Share AMP archetype and  remote JUnit testing,
  • Simplification of Enterprise development, with the introduction of a -Penterprise profile to simply configure your build to work against Alfresco Enterprise 5.0.
  • Embedded h2 database support, deprecating the external project alfresco-h2-support … thank Carlo for filling this gap for way too long already!

I really do hope this is a welcomed and so much needed addition to the Alfresco Development ecosystem and just the first step in my new Product Management career towards an ever improving developer experience on top of the coolest ECM framework out there!

Looking forward to your feedback here in the comments or even better as issues or contributions to the Alfresco SDK Github project.

Happy Holidays, now off to some well deserved rest since next year is going to be full of exciting challenges!

Joining Alfresco Product Management – talk to me!!!

And since cats are out of the bag (check out last week’s Alfresco Office Hours with the Alfresco Product Management team), I figured it was about time to make the news official here.

I am delighted and excited to announce that, effective as of November 15th, I have accepted the role of Senior Product Manager, Core Platform / API.  This comes as part of a larger investment and restructuring of the Alfresco Product Management organization.

In this role I will be product managing the core of Alfresco (Repository, Solr, and all the core ECM building blocks) and the private (that we use internally for apps development) / public APIs to interact against the content repository.

I feel the need to hugely thank Alfresco for this great opportunity and personally thanking Thomas for the chance he gave me to make a strategic impact for the company I love.

Now, truth to be told, I’m a little scared as this is a major responsibility. But it’s a positive, motivating fear which will help me keep the bar high and hopefully deliver great work in this position.

Read more Joining Alfresco Product Management – talk to me!!!

My #AlfrescoSummit 2014 San Francisco recap, and tips for a successful Alfresco project!

Last week’s Alfresco’s Summit in San Francisco was a blast. Every single day. Every single moment (ok well not the night before the preso, when I had to finish

Here’s a day by day recap of my #AlfrescoSummit, the uncountable reasons why I love this event and why you might want to book a last minute spot at Alfresco Summit, and join us in London next week:

Maven Hipsters
Mehven hipsters sabotage!
  • On day 1: together with Mao, we delivered a 4 hands talk called “Get Your Alfresco Project from Zero to Hero with Maven Alfresco SDK and Alfresco Boxes”, finally covering the automation of the full Alfresco project lifecycle! Check out the slides below, for the ultimate approach to Alfresco project lifecycle, a combination of the:
    • the world class developer experience provided by the Alfresco SDK 2.0
    • the highly automated provisioning / deployment of arbitrarily complex architectures provided by Alfresco Boxes (supporting technologies like Vagrant, Packer, Docker and chef-alfresco).

  • On day 2: I delivered a (hopefully) very well received talk called “10 things you need to know to have a successful Alfresco Project”. I tried in a few slides to gather the top ten common mistakes or overlooks I have seen in my now 7+ years of Alfresco career, in every phase of the project lifecycle, from inception to development, from release to deployment and distribution. As part of this talk, I also introduced for the first time a pilot of the Alfresco Developer Support service, a support add-on package dedicated to Enterprise customers and partners who extensively develop on our platforms and require access to highly skilled senior Alfresco engineers on development matters. Check out the slides below and don’t hesitate reaching out to me if you are interested in the Dev Support service:

On top of my contributions to this Summit, it’s been amazing to:

  • Attend Doug’s, John‘s and Thomas’ keynotes, which were were simply FANTASTIC! So excited to be part of a hugely growing product, which is revolutionizing the way knowledge workers can be  productive in their daily job, while being fully engaged and driving the humongous amount of content that we produce everyday to the degree of control the modern Enterprise requires. Come and join in London for this fantastic outlook on the upcoming Alfresco 5!
  • Get to meet (again) many of the Alfresco gurus I remotely work with on a daily basis. Spending a whole week with great Alfrescans like Peter Monks, Maurizio Pillitu, Greg Mehlan, Gethin James and so many other is really refreshing! Not just from a purely technical standpoint, but most importantly that’s was REAL fun – as Peter’s picture clearly here on the right shows – btw the Italian mullet is a present of mine!)

    Peter Monks, the first Mulleteer! :)
    Peter Monks, the first Mulleteer! :)
  • Network with so many smart partners and customers, getting their feedback on the product, the SDK and how we can help driving you to continuous customer success!
  • Get to meet the Community and not only get (very personally satisfying, have to admit) exciting feedback on the SDK 2.x version but also seeing Order of the Bee t-shirts proliferating was a really positive sign of a growing, lively and never so important Alfresco Community! Nice to see you again Bindu and looking forward to see you Ole! (just to name 2!)

Well I hope I have given you one more reason to come and see us at Summit.

Especially as I relocated to the US, I really look forward to meet many of the long term Alfrescans Community & Enterprise members of the good old European community next week in London!

See you there? 🙂

Alfresco SDK 2.0-beta-4 released in Maven Central!

It’s with extreme pleasure that, thanks to the great support from the Order of the Bee and the Community at large, we have released the Alfresco SDK 2.0.0-beta-4 … this time in Maven Central!

And 2.0.0 release is on the way, definitely out for you to use at the Alfresco Summit!

If you just can’t wait, check out a full tutorial and overview of new hot reloading features and IDE integration in this video (kudos to Ole for putting this together):

If you check out docs and release notes, I hope you’ll be gladly surprised by the number of enhancements and bug-fixes that went in this release, which, without any doubt, is to date the greatest ever achievement in ergonomics, productivity, quality and automation of Alfresco development! This represents a major step towards driving the Alfresco Community to become an organic, self sustained, proactive ecosystem of extensions and plugins for our favorite platform, Alfresco!

There are so many new features in this release, some of them very notable and I’d like to share them with you:

  • Compatibility with Alfresco Community 5.0.a+ (and soon with the upcoming Alfresco Enterprise 5.0.x). For 4.2 and below, you still need to use the SDK 1.x (see full SDK / Alfresco compatibility matrix here)
  • Availability on Maven central (see screenshot below)! Any Maven developer can just run a simple mvn archetype:generate and quickly create Alfresco projects directly from Maven Central! Is this JUST awesome?
Generate Alfresco Projects from Maven Central!
Generate Alfresco Projects from Maven Central!
  • True IDE integration with Eclipse, Idea and Netbeans (just Import Maven Projects) with rapid development support, by hot reloading of your Java classes, Web resources, webscripts, freemarker templates, using Spring Loaded and advanced Tomcat7 features (check out again the video above, you likely need to see it twice to believe it 🙂, to get all excited and farewell to all those ugly slow Alfresco restarts 🙂
  • Unit and integration testing support, with remote JUnit testing features to avoid context reloading and run unit tests (from your IDE) in seconds (or less)
  • Easy new starter setup and run scripts in each archetype. Just create the project, execute ./ and off you go!
  • Updated SDK 2.x docs (separate from SDK 1.x docs)
  • rm profile (enable with -Prm) in the all-in-one archetype to enable Records Management development
  • Multiple bug fixes and stabilization

The feedback we got is that this new version is just AMAZING and enables levels of productivity never seen before on Alfresco project. And, for those of you that have followed me in this journey started 6 years ago, this shouldn’t be anything less than mind-boggling.

I really wish you will experience the same and I’d love to hear your feedback and contributions. I’d welcome comments here, issues or pull requests on the SDK project, or even emails on the Maven Alfresco mailing list. Also, stay tuned, since 2.0.0 final is targeted to introduce new juicy features, like easy Selenium functional testing,  even easier configuration of Community / Enterprise artifacts via a simple profile and integration of the Alfresco Technical Validation tool to ensure quality of your extensions.

And if this is getting you half as excited as I am right now, make sure you come to the next month’s Alfresco Summit (in San Francisco or London) where, together with Maurizio, we’ll extensively present how, in just 50 minutes, you can leverage the Alfresco SDK to get your project from inception to its first release and how, using Alfresco Boxes, you can consume this release and deploy arbitrarily complex architectures, on premise or in the cloud, in FULL automation.  Now that’s what I call an overarching vision

And if you really want to become a Guru, come join the Maven Alfresco training that Maurizio will run in both venues, one very worth day spent to save days of sub-optimal development 🙂

Stay tuned and send us your feedback!

[Maven is not so evil] Avoid webapp redeployment with hot reloading of your Maven project in Eclipse and IDEA. For free? Yes, with Spring-loaded and Tomcat7 :)

This might be the most important feature we have ever added to the (Maven) Alfresco SDK, which explains why we are getting such an amazing feedback following yesterday Tech Talk Live, where we presented the fully hot reloading (no webapp-context reload) early 2.0 version of the SDK.

BTW, if you are an Alfresco Developer and you have missed the talk, I (and not just myself) really recommend you take a hour of your time and check out the recording of the talk and / or the slide deck, because, if you are used to the sometimes frustrating world of WAR reloading (especially with a 100M+ webapp like Alfresco), I really do hope the demo of the new SDK will be no less than mind boggling for you…

Or, well, at least half as excited as I was when I first saw Ole‘s early attempts and when I finally got it working integrated in the SDK just a couple of days ago. Eureka! was my reaction to say the least (and in honor of my Sicilian past, a reference to Archimedes never hurts :).

I figured though that it’s not only Alfresco Developers that can benefit from this new approach, but more in general the community at large of Java developers using Maven to develop J2EE webapps in conjunction with an IDE (tested on Eclipse, IDEA, Netbeans).

And I know first hand the pain it takes to wait for neverending reloads, being this one of the main concerns around Java development with respect to newer / interpreted frameworks which make RAD (Rapid Application Development) their mantra.

So I figured I shared with all of you, eager blog readers, the couple of (simple) tricks that we used to define what, hopefully once and for all, can become the standard de facto to boost rapid develop Java webapps on Maven, in a completely IDE independent (but integrated) way and without the need for proprietary tools like JRebel.

So here we go. Assuming you have a WAR project, follow this steps to forget once and for all lengthy and boring WAR reloading (and contextually drink less coffeee!):

  1. The first building block is spring-loaded, a library from (used to provide hot reloading to the GRails2 framework). This library (free of charge) provides a JVM agent which, transparently, provides class files reloading. All you need to do is get the spring-loaded.jar (e.g. from here) and then run your build with the agend enabled as such:
    MAVEN_OPTS="-javaagent:/path/to/downloads/springloaded-1.2.0.RELEASE.jar -noverify" 
mvn <goals>
  2. The second building block is based on the Tomcat7 VirtualWebapp features. This allows to: configure, via webapp context.xml, your webapp to dynamically load classpath resources (with the and webapp Loader component) and web resources (via ResourcesVirtualDirContext)  from outside a physical WAR / exploded folder. This way it’s very easy to configure your Maven <war> packaging project to automatically load classpath and web-resources directly from where Maven (or your IDE) would compile them, i.e. ${} (for your classpath resources) and ${}/${} for your webapp resources. Basically you just need to create a context.xml file in your Maven project (e.g. in this example in the ${project.basedir}/tomcat folder that looks like this:
    <?xml version="1.0" encoding="UTF-8"?>
    <Context docBase="${alfresco.client.war.folder}" path="${alfresco.client.contextPath}">
      <Resources className="org.apache.naming.resources.VirtualDirContext" 
      extraResourcePaths="/=${}/${}" />
    <Loader searchVirtualFirst="true" className="org.apache.catalina.loader.VirtualWebappLoader" virtualClasspath="${}" />
  3. Once the two building blocks are in place, you just need to wire this in the Maven pom.xml for your war packaging project. You could use Cargo but my dark memories of pain using that plugin suggest that a better, easier and more maintained route is to use the shiny tomcat7-maven-plugin. All you need to do is telling tomcat to use the previously defined context file by specifying:

    NOTE: this is going to bind the tomcat7 plugin to run your WAR, with the RAD configuration, during the pre-integration-test phase.

  4. Now you can run your build with:
    mvn clean integration-test

    and you will see your webapp run in Tomcat7. Nothing spectacular yet, but go the next point 🙂

  5. Now import your Maven project in Eclipse (Luna has already the Maven integration by default) or IDEA and there the fun begins! If you make a change to an existing Java class or web resource, all it takes is for you to hit refresh on your browser and AUTOMAGICALLY changes are there! No more webapp reloads, no more waiting time, just have fun!
  6. If you want an example of how this approach can save you huge amounts of time (and hairloss :P) check out the video below:

Hope you enjoyed what you see and hope you can leverage this ASAP! Feedback and comments are welcome, but in the meanwhile a nice collective farewell to silly webapp reloads 🙂

(Maven) Alfresco SDK migrated to Github!

+  =

As anticipated, I have today completed the migration of the (Maven) Alfresco SDK to the Alfresco Organization in Github.

The new location for the project is Issues and code are already there, let me know if I missed something obvious or if you don’t have the right access to the project.

After 6 years in Google Code, we decided to move to Github to foster even more contributions and an ever growing flourishing community around the Alfresco SDK! I’m excited! 🙂

The old Google Code project location is temporarily still there for a limited amount of time, but I plan to close it for good and redirect to the Github location.

So, what else can I say?

Well, FORK US 🙂

What’s happening with the Maven Alfresco SDK? Get ready for 2.x!

After about 10 (really very busy) months of silence in this blog, I think I owe everyone an update of what’s going on with the Maven Alfresco SDK and more in general with Maven and Alfresco.

Lots happened, and it’s still happening, so here’s an update so that

So first things first, from the Alfresco side:

  • As you know, the long journey of Mavenizing the Alfresco build is ended. After Cloud, now Community and soon Enterprise are building with Maven
  • Alfresco Community 5.0.a is out and it’s fully built with Maven. Took about 5 years, but we made it, so get finally ready for a fully orchestrated ecosystem here 🙂
  • Highly likely the old Java / Eclipse SDK is going to be EOL’d, leaving the Maven SDK as the one and only standard de facto best practice to develop on Alfresco
  • We (and Mau specifically) are developing a Maven + Alfresco training that will be delivered at both Alfresco Summits in London and San Francisco. On this note, did you already sign up for Summit US or EMEA? If not, what are you waiting for? The schedule is, once again this year, just A M A Z I N G!

On the SDK side instead we plan to do the following:

  • Move the SDK project to Github, consolidating it in the Alfresco organization. The rationale here, apart from consolidation, is to move to a more modern SCM system which would foster even more visibility and community contributions. Pretty excited about that 🙂
  • We are preparing the SDK release 2.x, which will be compatible with Alfresco 5.x. In the meanwhile you might want to check out the latest 2.0.0-SNAPSHOTS which are increasingly compatible with 5.0.a (disclaimer: YMMV!). Here all the issues we are targeting to resolve, so some work is still required
  • We are seeing community momentum in the SDK like never before, mostly thanks to Ole’s great community help. In particular, Ole has Mavenized already all the samples of the old Java/Eclipse SDK, so we plan to release those together with the new 2.x SDK release and in general make those the reference examples for Alfresco development. Neat isn’t it?
  • If you are interested please help us testing the snapshots, opening issues or even provide contributions. Don’t be shy!

Stay tuned, as we plan to wrap up all this work by Summit, so less than 2 months away. I will then going to be presenting together with Maurizio on a full end to end process to manage Alfresco process, from development and release with the Maven SDK to continuous delivery and deployment with Alfresco Boxes, in a session called “Get Your Alfresco Project from Zero to Hero with Maven Alfresco SDK and Alfresco Boxes“.


           See you there?

            Sign up Here 🙂