Closed WonderCsabo closed 9 years ago
@JakeWharton any thoughts?
Yes, please release as a JAR as well. I'd like to migrate from fest over to assertj and use with Robolectric. Also, there are dependency issues with Gradle and the way it is creating AAR files, that will be blocked from being distributed to Maven Central if they contain invalid poms (i.e. ones generated following the IVY specs).
The way the AARs are created currently break with Maven based tooling.
See: https://code.google.com/p/android/issues/detail?id=72807 https://twitter.com/jvanzyl/status/540930500513120257 https://twitter.com/jvanzyl/status/540930855854559233
Not sure if this is everything that is necessary for creating the jars during the gradle build: https://github.com/square/assertj-android/pull/149
We used the patch in #149 and it works well to produce the necessary jar versions so we can use it in our maven builds and with the maven-surefire-plugin and robolectric. The AARs are not added to the classpath if you specify a test scope, and if you specify them as a normal dependency they get included in the APK.
I looked at the snapshot release and i see it only comes with AAR packaging. Can we get an artifact with simple jar packaging? This way this library could be easily used in eclipse, where there is no way to use AARs. Actually i see no reason to package this library as an AAR, since this contains only classes, no resources, also its nature fits a jar much more.