Native American Artifacts

Native American Artifacts

It’s my honor – and a a huge personal satisfaction after a few years working on this – to announce the full availability and support of the Alfresco Artifacts Repository, a fully fledged Maven repository hosting the major Alfresco releases and of its flourishing projects ecosystem, both for the Alfresco Community and Enterprise Networks.

For those of you already following this blog this might be no big news, as somehow the information was already around in the Alfresco-sphere and an Alfresco Maven repository has been already unofficially (AKA maintained by me) around for a while. But the great news is that now the repository is officially maintained and artifacts are kept up to date :)

Based on the Nexus OSS mature Artifact Repository technology, and following a few weeks Partner only beta, the repository is now publicly available at:

http://artifacts.alfresco.com (formerly http://maven.alfresco.com)
The Alfresco Artifact Repository

The Alfresco Artifact Repository

What can you find in there (AKA the screenshot is not enough)? Very well, at the moment the Artifact Repository hosts:

  1. Alfresco Community full releases (JARs/WARs) identified with the groupId org.alfresco
  2. NEW: Alfresco Enterprise full releases identified with the groupId org.alfresco.enterprise
  3. NEW: Alfresco Hotfix full releases identified with the groupId org.alfresco.enterprise
  4. Activiti (BPMN 2.0 implementation) Releases and Snapshots
  5. All the versions of the open source Maven Alfresco Lifecycle, a long term but quickly growing Maven SDK approach to Alfresco development
  6. All Spring repository proxies, to ease Spring Surf development by only referring to this repository developing Surf

NOTE: At the moment no POM files / dependency declarations are available, but if you are interested please feel free to vote on this issue :)

Still not sure about the potential? Well, let me just give you an idea:

  • Integration in your standard Enterprise development process, enabling automation and simple version management
  • Choose your development flavor: whether you like the Maven SDK,  you are a Gradle fan or  whether you work with any of the Maven compatible technologies, you can download Alfresco artifacts with just a few lines of code. See an example (for a Spring dependency) on how a Maven repository can adapt to your development technology
  • Have Sources and Javadocs promptly available in your IDE if it’s Maven compliant: in Eclipse, for example, if you have M2Eclipse installed, adding your dependency will automatically result in -sources.jar and -javadoc.jar to be downloaded, enabling in-line documentation and remote debugging for advanced troubleshooting. Neat’o, ain’t it? :)
  • Powerful Artifact identification and search engine, allowing artifact, GAV (groupId, artifactId, version) and even class name search (YES, it searches in JARs :P ) . In the picture, just an example on how to filter on all Alfresco 4.0d Community artifacts

For full documentation on how to use the repository with Maven, please refer to the dedicated wiki page. And if you are missing an Artifact, please open an issue in the appropriate Jira Component or in Alfresco Support if your are an Enterprise Customer.

GAV Search
Artifact GAV Search

We really hope the introduction of a fully supported Artifact repository could be a great driver for simple participation and contribution in the exciting Alfresco ecosystem: and I expect more news to come, that should make (at least Maven and Gradle) Alfresco developers re-joy all over the world.

Ok, I’m maybe being too Italianly dramatic here, but stay tuned because in the next months we will bring our platform and extended ecosystem to the next level.  And let me take time to thank the people who helped making this happen: this would not have happened without them and their support :)

For now, time to open your Champagne Prosecco – as a good friend suggested – bottles and enjoy your well deserved repository :)

4 Responses so far.

  1. [...] since I last touched Maven and I remembered it being pretty easy to use. I also remembered some chatter in Alfresco circles about an official Maven repository for Alfresco, so I decided to dig a little [...]

    • Akio says:

      You’ll have to use whatever mencihasm your OS provides to access remote directories. Assuming that you are under Windows, this means mapping the remote folder to some unused drive letter, such as Z:. The rest of the procedure would then be the same as what is described here.If that does not work on your system, you should consider installing a Maven proxy on your remote machine, such as Nexus or Artifactory. In fact, that would be the recommended way of doing it.

  2. [...] for a few years now and, in this last year, I experienced a momentum never seen before both from a corporate and from a community standpoint. Literally, about to cry [...]

  3. [...] started almost 5 years ago, and through the years, little by little, we made giant steps towards an open development platform. [...]

Leave a Reply