[
https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280753#comment-13280753
]
Rupert Westenthaler commented on STANBOL-620:
---------------------------------------------
Thx Peter for the detailed analysis.
As far as I know there are also a lot of other Unit Test within Stanbol that
depend on the execution order. So this may affect tests of several components!
Based on [1] I assume that junit-4.11 will be released soonish™
[1] http://tech.groups.yahoo.com/group/junit/message/23898
> Commons Solr Managed tests fail on second invocation
> ----------------------------------------------------
>
> Key: STANBOL-620
> URL: https://issues.apache.org/jira/browse/STANBOL-620
> Project: Stanbol
> Issue Type: Bug
> Components: Commons
> Affects Versions: 0.10.0-incubating
> Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
> Reporter: Peter Ansell
>
> The following test fails on the second time trying to run mvn clean install
> on the commons reactor after clearing the maven cache repository of all
> org.apache.stanbol artifacts:
> testGetManagedIndexes(org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest)
> To reproduce clear the repository cache
> rm -rf ~/.m2/repository/org/apache/stanbol/
> cd stanbol/commons/
> mvn clean install (should fail on org.apache.stanbol.commons.opennlp due to
> missing dependency, see STANBOL-588 )
> mvn clean install (should now fail on org.apache.stanbol.commons.solr.managed
> when the tests passed fine the first time through)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
