[plc4x] 02/02: chore(build): Added a configuration to exclude the milo classes from jacoco instrumentation as these were causing exceptions in the build output.

[cd...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

cdutz pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/plc4x.git

commit 97615bfcfcef4330c43f6a4e36bff85fe6bc7f46
Author: christoferdutz <ch...@c-ware.de>
AuthorDate: Mon Jul 11 17:20:09 2022 +0200

    chore(build): Added a configuration to exclude the milo classes from jacoco instrumentation as these were causing exceptions in the build output.
---
 plc4j/drivers/opcua/pom.xml | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/plc4j/drivers/opcua/pom.xml b/plc4j/drivers/opcua/pom.xml
index 3294b4f66..dbb3cdaf9 100644
--- a/plc4j/drivers/opcua/pom.xml
+++ b/plc4j/drivers/opcua/pom.xml
@@ -98,6 +98,20 @@
           </instructions>
         </configuration>
       </plugin>
+      <!--
+        When instrumenting the Eclipse Milo files for code coverage calculation
+        We're getting errors which don't hurt, but sort of make the build ugly.
+        So we're telling the plugin to exclude them from instrumentation.
+      -->
+      <plugin>
+        <groupId>org.jacoco</groupId>
+        <artifactId>jacoco-maven-plugin</artifactId>
+        <configuration>
+          <excludes>
+            <exclude>org/eclipse/**/*</exclude>
+          </excludes>
+        </configuration>
+      </plugin>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-dependency-plugin</artifactId>