You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2019/02/04 14:59:00 UTC

[jira] [Created] (IGNITE-11196) A number of suited failed because of maven-enforcer-plugin failure for Java 11 build

Dmitriy Pavlov created IGNITE-11196:
---------------------------------------

             Summary: A number of suited failed because of maven-enforcer-plugin failure for Java 11 build
                 Key: IGNITE-11196
                 URL: https://issues.apache.org/jira/browse/IGNITE-11196
             Project: Ignite
          Issue Type: Bug
            Reporter: Dmitriy Pavlov
            Assignee: Peter Ivanov


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

{noformat}
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
{noformat}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)