[jira] [Resolved] (METAMODEL-1206) MetaModel-elasticsearch-native module build fails based on unit test run order

["Kasper Sørensen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/METAMODEL-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kasper Sørensen resolved METAMODEL-1206.
----------------------------------------
       Resolution: Fixed
         Assignee: Arjan Seijkens
    Fix Version/s: 5.1.1

Fixed with https://github.com/apache/metamodel/pull/198

> MetaModel-elasticsearch-native module build fails based on unit test run order
> ------------------------------------------------------------------------------
>
>                 Key: METAMODEL-1206
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-1206
>             Project: Apache MetaModel
>          Issue Type: Bug
>            Reporter: Arjan Seijkens
>            Assignee: Arjan Seijkens
>            Priority: Major
>             Fix For: 5.1.1
>
>
> If when building the MetaModel-elasticsearch-native the {{ElasticSearchDataContextTest}} unit test class is executed first, the module will fail to build.
> This seems to be cause by the fact that the class extends the {{org.elasticsearch.test.ESSingleNodeTestCase}} class provided by the Elasticsearch test framework, which apparently sets its of SecurityManager for the JVM, as a result of which the Apache Maven surefire plugin fails to run any consecutive tests.
> I created an issue for this on the Elasticsearch project, because I was able to reproduce this separately outside of the MetaModel project (see [elasticsearch-surefire-test|https://github.com/arjansh/elasticsearch-surefire-test]).
> Anyway, we can probably work around this problem for now by making sure the surefire-plugin always executes the {{ElasticSearchDataContextTest}} unit test class last for this module.



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