— Brice
--
You received this message because you are subscribed to the Google Groups "mockito-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mockito-dev...@googlegroups.com.
To post to this group, send email to mocki...@googlegroups.com.
Visit this group at http://groups.google.com/group/mockito-dev.
For more options, visit https://groups.google.com/d/optout.
It’s getting complicated to ship multiple jars.
hell yeah :)
hamcrest entertained the idea of putting java version in front, e.g.: mockito-core:8.x would be java8 compat. Seems inflexible and potentially confusing.
Agreed let’s not do that, 3.x is ok imho.
So 2.x for java5 compatibility and 3.x for java8.
Yes
I’m not a big fan of splitting again mockito in several smaller dependencies
Any specific reason? Options b/c already do this.
Extracting the Mockmaker seems a good idea as it is a pluggable component. But I wouldn’t split mockito any further. I don’t think it brings significant value for a test related jar.
Also it may lead to some DependenciesDeclarationOverflowDeveloperError
.
— Brice