Activiti

Homepage: http://activiti.org

Activiti is a light-weight workflow and Business Process Management (BPM) Platform targeted at business people, developers and system admins. Its core is a super-fast and rock-solid BPMN 2 process engine for Java. It's open-source and distributed under the Apache license. Activiti runs in any Java application, on a server, on a cluster or in the cloud. It integrates perfectly with Spring, it is extremely lightweight and based on simple concepts.

**NOTE: We moved to the master branch all the content of the development branch that we were using to design and code the next major version of the project. If you want to contribute with version 6.x please look at the 6.x branch.**

If you want to read more about our Repositories structure you can read our GitBook.

Preview Propagation

This repository includes an automated Preview Propagation mechanism for testing cross-module integration with downstream repositories like activiti-cloud. When working on features that span multiple modules:

1. Add labels preview + preview-propagation to your PR
2. The system automatically builds a preview version and creates a test PR in activiti-cloud
3. Test the integration in the downstream PR
4. When your source PR closes/merges, the test PR automatically closes

Preview snapshots (0.0.1-PR-<number>-SNAPSHOT) and develop alpha releases are published to both Nexus and Cloudsmith, using activiti-snapshots and activiti-releases, respectively. Propagation starts after both deployments succeed.

For Cloudsmith publishing, set the GitHub Actions variable CLOUDSMITH_NAMESPACE to hyland and grant the activiti-activiti service account write access to both targets. The cloudsmith-auth action uses GitHub OIDC to provide temporary CLOUDSMITH_USERNAME and CLOUDSMITH_API_KEY credentials for settings.xml; no static Cloudsmith secret is required.

Each propagation writes the GitHub Actions run ID (BUILD_RUN_ID) to preview-build.properties in the downstream repository, ensuring a new commit for each new workflow run even when the preview snapshot version is unchanged.

This eliminates manual version bumping and cleanup while ensuring integration changes are validated before merge.

Configuring IntelliJ

• Force language level 25, to fail-fast when (accidentally) using features available only in newer Java versions.

  • Open menu File, menu item Project Structure
  • Click list item Modules, for each module, tab Sources, combobox Language level should be automatically set to 25 ...

• Avoid that changes in some resources are ignored in the next run/debug (and you are forced to use mvn)

  • Open menu File, menu item Settings or menu IntelliJ IDEA, menu item Preferences... if on a Mac
  • Click tree item Compiler, textfield Resource patterns: change to !?*.java (remove other content)

• Avoid a StackOverflowError when building

  • Open menu File, menu item Settings or menu IntelliJ IDEA, menu item Preferences... if on a Mac
  • Click tree item Compiler, tree item Java Compiler, textfield Additional command line parameters
  • Add -J-Xss1024k

• Recommended code style: use the Google Java Style Guide with editorconfig

  • Download the IntelliJ code style xml from: [https://google.github.io/styleguide/intellij-java-google-style.xml]
  • Open menu File, menu item Settings or menu IntelliJ IDEA, menu item Preferences... if on a Mac
  • Click tree item Code Style, click cogwheel and select Import scheme, then IntelliJ code style xml
  • Browse where you downloaded the xml and open it. Check that GoogleStyle is the active scheme.
    • Note: IntelliJ IDEA doesn't format your code automatically. You have to press Ctrl+Alt+L keyboard combination to trigger auto formatting when coding is done.
  • There's an .editorconfig what has definition for indents, file encoding, line endings.
  • If you disable it, you need to set the file encoding and number of spaces correctly manually.
  • Eclipse code style xml: [https://google.github.io/styleguide/eclipse-java-google-style.xml]

以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗