最近公司有工作流需求,但是架构师要求用最新的activiti7 做测试流程及其开发
发现选择版本容易出现这样那样的问题
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.activiti.dependencies</groupId>
<artifactId>activiti-dependencies</artifactId>
<version>${activiti-dependencies.version}</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
<activiti-dependencies.version>7.1.0.M6</activiti-dependencies.version>
<<坑>>当启动流程时,会曝出类似这样的错误
Process definition with the given id:‘process-7c7bee14-9383-408e-a594-460cbfd13724:1:4’ belongs to a different application version.
解决方案摘自别处
The new logic will be used when a project manifest file is set via the property project.manifest.file.path. Here is an example. All the versions of process definitions will be bumped up when the version of project changes inside the manifest file.
翻译过来,新的逻辑会被使用当一个工程的mainifest文件被project.mainifest.file.path属性设定后。所有的流程定义的版本都会被改变当mainifest文件里的工程版本被改变时。
OK,说的很清楚了,在resource目录下加上default-project.json文件,然后在application.properties文件里指定project.manifest.file.path属性即可。(貌似没有卵用)
目前发现有一个版本可用 不会出现此问题<activiti-dependencies.version>7.1.123</activiti-dependencies.version>