Duplicate resource files when upgrading to version 7.13.0

Hello guys.

I am using the Camunda Engine embedded in a SpringBoot project. When upgrading to version 7.13.0, an error occurred while running the Maven duplicate-finder-maven-plugin.

Found duplicate classes/resources in runtime classpath.
Found duplicate and different resources in [org.camunda.bpm.model:camunda-bpmn-model:7.13.0, org.camunda.bpm.model:camunda-dmn-model:7.13.0]:
  DC.xsd
  DI.xsd

The workaround was to add the following configuration to my pom.xml:

<plugin>
	<groupId>org.basepom.maven</groupId>
	<artifactId>duplicate-finder-maven-plugin</artifactId>
        <configuration>
		<exceptions>
                	<exception>
                    		<conflictingDependencies>
                        		<dependency>
                            			<groupId>org.camunda.bpm.model</groupId>
                            			<artifactId>camunda-bpmn-model</artifactId>
                        		</dependency>
                        		<dependency>
                            			<groupId>org.camunda.bpm.model</groupId>
                            			<artifactId>camunda-dmn-model</artifactId>
                        		</dependency>
                    		</conflictingDependencies>
                    		<resources>
                        		<resource>DC.xsd</resource>
                        		<resource>DI.xsd</resource>
                    		</resources>
                	</exception>
            	</exceptions>
	</configuration>
</plugin>

Can you explain the procedure you went through when upgrading and what docs you might have followed?

Hello.

I followed the guide published at https://docs.camunda.org/manual/latest/update/minor/712-to-713/#spring-boot-starter-update.

I just updated the dependency version in pom.xml.

<dependency>
    <groupId>org.camunda.bpm.springboot</groupId>
    <artifactId>camunda-bpm-spring-boot-starter</artifactId>
    <version>7.13.0</version>
</dependency>

My project runs the Maven plugin ‘duplicate-finder-maven-plugin’ via Jenkins. When I updated the dependency the project build failed with the reported error.