lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonas van Vliet (JIRA)" <>
Subject [jira] [Commented] (SOLR-7523) Maven test fails in solr/contrib/map-reduce
Date Tue, 12 May 2015 06:03:00 GMT


Jonas van Vliet commented on SOLR-7523:

The NoClassDefFoundError still occurs in the code after applying the patch if you force the
test to run regardless of assumptions being true or false. This issue should be addressed
in a different bug report.

The problem I experienced was the fact that ant test and maven test returned different results
due to different input parameters. This patch only aligns the test parameters - it does not
fix the test itself.

> Maven test fails in solr/contrib/map-reduce
> -------------------------------------------
>                 Key: SOLR-7523
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: contrib - MapReduce
>    Affects Versions: 5.1
>            Reporter: Jonas van Vliet
>            Assignee: Steve Rowe
>            Priority: Critical
>              Labels: maven, test
>         Attachments: SOLR-7523.patch
> Maven test fails on the following package:
> solr/contrib/map-reduce/
> (seen on solr6 trunk and solr 5.x branch)
> The underlying problem seems to be that when running maven test, the java security manager
is not set. When running ant test, the security manager is set to org.apache.lucene.util.TestSecurityManager.

> The failing test is skipped while running ant test due to an assumption in org/apache/solr/hadoop/
> assumeTrue(
>         "Currently this test can only be run without the lucene test security policy
in place",
>         System.getProperty("", "").equals(""));
> In maven, the test is not skipped and fails.
> I propose aligning the ant and maven test so they use the same security manager.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message