0

Here in my company we're building a Player SDK for android using GMF and Exoplayer as transitive dependencies and we would like to see which one is the best strategy to upload it to a maven repository ( we have a SonaType account ) that allow our clients to download it with a simple compile command.

We've been searching online but we couldn't reach a "perfect" or "ideal" solution. We came across this "gradle-mvn-push" plugin but looks like it's deprecated. Did anyone come across this problem? How did you solve it?

Thanks =)

Thiago Miranda de Oliveira
  • 5,790
  • 5
  • 20
  • 24
  • Are you asking what is the best way to publish to a maven repo from gradle? – RaGe Jan 27 '16 at 20:32
  • I'm almost there but there was a problem with the transitive dependencies. It can't seems to work at all hence they are not included even using transitive = true. compile(project(':second-level-lib')) { transitive=true } – Thiago Miranda de Oliveira Jan 28 '16 at 14:05
  • If you're publishing to a maven repo, use the [new `maven-publish` plugin](https://docs.gradle.org/current/userguide/publishing_maven.html). aar's are not accompanied by a pom file by default, you'll have to construct your own. See here: http://stackoverflow.com/a/34914603/745574 – RaGe Jan 28 '16 at 14:25
  • player-sdk asdf unspecified compile com.android.support appcompat-v7 23.1.1 compile – Thiago Miranda de Oliveira Jan 28 '16 at 16:56
  • Thanks for your suggestion! Unfortunately when including a module as a dependency the resulting pom.xml goes like this. We are trying to achieve something like the brightcove's skd example ( http://docs.brightcove.com/en/perform/mobile-sdks/brightcove-player-sdk-for-android/guides/studio-android-sdk-quick-start.html ) – Thiago Miranda de Oliveira Jan 28 '16 at 17:02

0 Answers0