[IGNITE-11196] A number of suites failed because of maven-enforcer-plugin failure for Java 11 build

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Assignee: Peter Ivanov
• Reporter: Dmitry Pavlov
• Created: 04/Feb/19 14:58
• Updated: 28/Jul/20 09:22
• Resolved: 05/Feb/19 12:26

Description

A number of exit codes occurred in Java 11 tests build:

• SPI (URI Deploy) [ tests 0 Exit Code ] 1 queued
• RDD* [ tests 0 Exit Code ]
• OSGi [ tests 0 Exit Code ]
• Logging [ tests 0 Exit Code ]
• AOP [ tests 0 Exit Code ]
• JCache TCK 1.1 [ tests 0 Exit Code ]
• Licenses Headers [ tests 0 Exit Code ]
• Cassandra Store [ tests 0 Exit Code ]

For example, SPI (URI Deploy) failed with maven enforcer plugin:

https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=2995900&_focus=1525

org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce (default) on project ignite-tools: Execution default of goal org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce: java.lang.ExceptionInInitializerError: null

Issue Links

• blocks: IGNITE-11189 Support Java 11 for Apache Ignite
• relates to: IGNITE-11213 A number of suites failed because of maven-surefire-plugin NPE for Java 11 build