[
https://issues.apache.org/jira/browse/STANBOL-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-620.
-----------------------------------------
Resolution: Fixed
Assignee: Rupert Westenthaler
Stanbol now uses Junit 4.11. This release changed execution oder for unit
tests. looks like that the execution order is no longer the same os the method
order within the source code. Not a problem, because unit tests must not depend
on each other ... but required several changes to existing tests that depended
on the ordering.
fixed with http://svn.apache.org/viewvc?rev=1409748&view=rev
> 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.9.0-incubating
> Environment: Maven 3.0.4
> OpenJDK-7
> Ubuntu 12.04
> Reporter: Peter Ansell
> Assignee: Rupert Westenthaler
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
