Hi,
turned out the problem was something completely different.
I needed to to add this and explicitly use testNG:
test {
useTestNG()
}
I thought this would be transparent given that I have testNG as a
dependency. It also did not help that at least once I get some test reports.
Not sure how this came about and I don't think anything got really run.
Funny enough, now I get the following messages in debug mode:
[org.gradle.api.internal.tasks.testing.testng.TestNGDetector]
test-class-scan : failed to scan parent class java/lang/Object, could not
find the class file
Seems that 'failed to scan parent class' does not mean anything. I wonder
why it is there at all. Very confusing.
--Hardy
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Tests-are-skipped-due-to-failed-to-scan-parent-class-java-lang-Object-tp5160607p5435025.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
