Skip to content

Latest commit

 

History

History
57 lines (37 loc) · 2.14 KB

README.md

File metadata and controls

57 lines (37 loc) · 2.14 KB

Micro Strategies Logo

Alfresco Process Services Archetype

This is the home of the Alfresco Process Services Archetype (formerly Activiti Enterprise Archetype). This is an Apache Maven archetype to create a base project from which to create extensions to Alfresco Process Services. These extensions can include task listeners, event listeners, custom REST calls, etc.

The approach is relatively simple and should be usable within the major IDE's. It has specifically been validated with IntelliJ Ultimate 14.1.4/14.1.5 and Eclipse Mars 4.5.0 but should work with any Maven enabled IDE.

The archetype will create two projects:

  • activiti-app
    • This is the activiti-app WAR that can be run within a container.
    • This will include your extension project.
  • {artifact id}-ext
    • {artifact id} will be replaced by whatever you name the root artifact.
    • This is the extension project where extensions will be placed.
    • It is possible to add multiple extension projects however they must be added to the activiti-app project.

Using this Archetype

To use the Archetype you really only need to know the group ID and the artifact ID:

  • Group ID - com.microstrat.activiti
  • Artifact ID - activiti-archetype

Using on Command Line

A new project can be created from the command line as follows:

mvn archetype:generate -DarchetypeCatalog=local -Dfilter=com.microstrat.activiti:activiti-archetype

Using in Eclipse

Using in IntelliJ

TODO

License

This project is released under the [Apache License, Version 2.0] (http://www.apache.org/licenses/LICENSE-2.0.html).

Next Steps

As this is the initial release there are a number of things that still need to be done. The biggest things are more logistical such as:

  • Usage documentation needs to be written and made available.
  • Supplementary documentation like How-to blogs and videos.
  • Add more samples to work from.
  • Create a separate archetype for the examples to keep the archetype clean (possibly)