Distribute Android binaries through a Maven repository

[GregoryComer]

🚀 The feature, motivation and pitch

We currently build Android AARs and make them accessible for direct download from S3. We can build on top of this by uploading and distributing the binaries through a Maven repository. This will allow users to simply add the dependency to their Maven or Gradle build and automatically pull the appropriate binary without needing to manually download and manage the artifact.

I don't personally have a ton of context on the Java / Android package management ecosystem, so I'll defer to experts (CC @kirklandsign), but it seems like Maven Central Repository is the way to go. We may be able to leverage work previously done by the PyTorch Dev Infra team to do this.

We will upload to maven and have a page like this. We would need to upload AAR and a POM file

Alternatives

No response

Additional context

No response

RFC (Optional)

No response

cc @larryliu0820 @lucylq @kirklandsign @cbilgin @mergennachin @byjlw

[digantdesai]

Should this be a discussion?

[GregoryComer]

Should this be a discussion?

I think we want to do this and have alignment, so it should be ready to pick up. There's a lot of interest in getting away from source builds for mobile use cases and Hansong has already done the work to generate the pre-builts, we just need to register and upload them.

Edit: So I think it can be left as an issue. It's actionable.

[jathu]

@kirklandsign should we include 0.5 initially and setup CI to push 0.6 when released? or should we just make 0.6 as the initial release?

cc @larryliu0820 @mergennachin

[kirklandsign]

0.6 should be the initial release.

I would love to have some snapshot from main to test it out before 0.6 though.

[byjlw]

Should this be a discussion?

I think we want to do this and have alignment, so it should be ready to pick up. There's a lot of interest in getting away from source builds for mobile use cases and Hansong has already done the work to generate the pre-builts, we just need to register and upload them.

Edit: So I think it can be left as an issue. It's actionable.

@kirklandsign can we update the description of this issue to include what success looks like since it's a scheduled item?

[kirklandsign]

Should this be a discussion?

I think we want to do this and have alignment, so it should be ready to pick up. There's a lot of interest in getting away from source builds for mobile use cases and Hansong has already done the work to generate the pre-builts, we just need to register and upload them.
Edit: So I think it can be left as an issue. It's actionable.

@kirklandsign can we update the description of this issue to include what success looks like since it's a scheduled item?

Updated. Artifact in https://mvnrepository.com/artifact/org.pytorch/executorch-android