Include jar artifacts. - Githubissues

square / assertj-android

A set of AssertJ helpers geared toward testing Android.

https://square.github.io/assertj-android/

Apache License 2.0

1.58k stars 156 forks source link

Include jar artifacts. #156

Closed JakeWharton closed 9 years ago

JakeWharton commented 9 years ago

Closes #110. Closes #149.

roman-mazur commented 9 years ago

This seems to have removed

<packaging>aar</packaging>

from the POM file. As a result we get a Gradle build error

version com.squareup.assertj:assertj-android-support-v4:1.0.1-SNAPSHOT depends on libraries but is a jar

roman-mazur commented 9 years ago

The question is will Maven users be able to pick up the jar if packaging is defined as AAR? Because my feeling is that AAR should be the packaging specified in the POM.

kriegfrj commented 9 years ago

Maybe this problem could be resolved by publishing the JAR-packaged artifacts under a distinct artifact ID - either instead of, or perhaps in addition to, the artifact ID used by the AAR-packaged artifact?

JakeWharton commented 9 years ago

@roman-mazur Yes, by specifying the qualifier.

@kriegfrj I do not want to do that.

kriegfrj commented 9 years ago

@JakeWharton: agreed - I offered it as "a" solution though it didn't seem like the most elegant. The qualifier approach should achieve much the same thing but cleaner.