Details
-
Task
-
Status: Closed
-
L3 - Default
-
Resolution: Fixed
-
None
-
None
Description
Impact: OSGi support breaks
The process engine build logs a warning which should go away if we do a simple renaming of an impl package in typed value api
org/camunda/bpm/engine/impl/variable
AT:
- JDIT TM
[WARNING] Manifest org.camunda.bpm:camunda-engine:jar:7.4.0-SNAPSHOT : Split package, multiple jars provide the same package:org/camunda/bpm/engine/impl/core/variable Use Import/Export Package directive -split-package:=(merge-first|merge-last|error|first) to get rid of this warning Package found in [Jar:., Jar:camunda-commons-typed-values] Class path [Jar:., Jar:camunda-bpmn-model, Jar:camunda-xml-model, Jar:camunda-cmmn-model, Jar:camunda-scriptengine-dmn, Jar:camunda-commons-utils, Jar:camunda-engine-dmn, Jar:camunda-dmn-model, Jar:camunda-engine-feel-api, Jar:camunda-engine-feel-juel, Jar:camunda-commons-logging, Jar:slf4j-api, Jar:camunda-commons-typed-values, Jar:commons-email, Jar:mail, Jar:activation, Jar:livetribe-jsr223, Jar:mybatis, Jar:spring-beans, Jar:spring-core, Jar:spring-asm, Jar:junit, Jar:hamcrest-core, Jar:ant, Jar:ant-launcher, Jar:groovy-all, Jar:persistence-api, Jar:geronimo-jta_1.1_spec, Jar:commons-logging, Jar:java-uuid-generator, Jar:log4j, Jar:joda-time, Jar:cdi-api, Jar:javax.inject, Jar:validation-api, Jar:hibernate-jpa-2.0-api, Jar:jboss-annotations-api_1.1_spec, Jar:jboss-ejb-api_3.1_spec, Jar:jboss-el-api_2.2_spec, Jar:jboss-jsf-api_2.1_spec, Jar:jboss-interceptors-api_1.1_spec, Jar:jboss-connector-api_1.6_spec, Jar:jboss-jaspi-api_1.0_spec, Jar:jboss-servlet-api_3.0_spec, Jar:jboss-jsp-api_2.2_spec, Jar:jboss-jstl-api_1.2_spec, Jar:xalan, Jar:serializer, Jar:jboss-transaction-api_1.1_spec, Jar:jboss-jaxrs-api_1.1_spec, Jar:jboss-jaxb-api_2.2_spec, Jar:catalina, Jar:servlet-api, Jar:juli, Jar:annotations-api, Jar:jboss-vfs, Jar:jboss-logging, Jar:jython, Jar:jruby-complete]