Skip to content
This repository has been archived by the owner on Apr 24, 2018. It is now read-only.

Add aar to Maven Central #142

Closed
gabrielemariotti opened this issue Jan 16, 2014 · 22 comments
Closed

Add aar to Maven Central #142

gabrielemariotti opened this issue Jan 16, 2014 · 22 comments

Comments

@gabrielemariotti
Copy link

It would be nice to see it in maven central in aar format.

Check here if you need a gradle script to update on maven: https://github.com/chrisbanes/gradle-mvn-push
Check here if you need help to register your first artifact on Sonatype OSS Repository:
http://gmariotti.blogspot.it/2013/09/publish-aar-file-to-maven-central-with.html

@hielkehoeve
Copy link

Not having this library available is preventing me from using this library and is forcing me to use other libraries which suck...

(Having libraries stored in a source version control system or having to checkout sources from a third party in order to use it goes against the whole idea of source version control)

@theblang
Copy link

theblang commented Feb 3, 2014

This would be so amazing.

@peitek
Copy link

peitek commented Mar 8, 2014

I second this.

@blurpy
Copy link

blurpy commented Mar 8, 2014

I agree, aar would be great. See also issue #7

@amlcurran
Copy link
Owner

Can't promise anything, but I'll try to take a look at it again this evening
On Mar 8, 2014 4:02 PM, "Christian Ihle" notifications@github.com wrote:

I agree, aar would be great. See also issue #7#7

Reply to this email directly or view it on GitHubhttps://github.com//issues/142#issuecomment-37101400
.

@WonderCsabo
Copy link

I would be very glad if this could happen. I face the same problem as @hielkehoeve .

@amlcurran
Copy link
Owner

OK! Good news. I've finally got the project up on Maven - but only the new branch. That's under groupId com.github.amlcurran.showcaseview, artifact library, version 5.0.0-SNAPSHOT. I haven't been able to add it as a dependency as of yet, but it's definitely on Central. But this version is the new version, so if you plan on using it, beware of basically the entire API changing!

If I get time, I'll upload the master branch's version tomorrow

@WonderCsabo
Copy link

Thanks @amlcurran for your work. But i think you should not push snapshot releases to central, OSS snapshot repo is a better place for that.

BTW, it does not appear on Central, yet.

Edit: Oops, it is in the OSS snapshot repo actually.

@WonderCsabo
Copy link

BTW, could you provide an apklib type artifact? This can be easily done, with gradle, too.

@amlcurran
Copy link
Owner

Sorry, I used the wrong term - the snapshot is indeed on the snapshot repository (proof!).

@amlcurran
Copy link
Owner

As for apklib, I won't be doing that yet, but I'll see what I can do.

@WonderCsabo
Copy link

Thanks!

@amlcurran
Copy link
Owner

OK, the apklib is up there too now, but I can't seem to give them different names (else they seem to go to staging). I don't know if this will cause any problems?

@peitek
Copy link

peitek commented Apr 26, 2014

The .aar works perfectly. Awesome! Thank you so much. I finally can use the library 😄

@amlcurran
Copy link
Owner

\o/

@WonderCsabo
Copy link

@amlcurran The apklib has a wrong structure. The correct structure is described here. Could you update your build gradle? I think it should be something like this:

from 'src/main/AndroidManifest.xml'
into('res') {
    from 'src/main/res'
}
into('src') {
    from 'src/main/java'
}

@amlcurran
Copy link
Owner

@WonderCsabo whoops, I thought I had changed that! I've uploaded what should be the correct version now.

@WonderCsabo
Copy link

Thanks! There is another problem. :( You are using support lib version 19.+. Unfortunately this notation is not supported by maven so maven build will fail (for aar and apklib, too). Also, the POM should define the android dependency. You can use another .gradle file for maven builds, so the normal build.gradle is not modified. @gabrielemariotti wrote a great tutorial on this, please check the first comment of this issue.

@amlcurran
Copy link
Owner

I can't see any ideas how to change this in Gabriele's blog post. However, I've now moved to using fixed dependency versions, so hopefully that will sort the issue with the apklib. I'm pushing it as we speak.

Please let me know how it is going and thanks for helping me test this!

@WonderCsabo
Copy link

See this example used in ListViewAnimations.

Edit: Sorry, i thought dependencies can be simply changed in the pom part in the gradle file, but that's not true. Now i remember the solution was using fixed version in ListViewAnimations, too.

@WonderCsabo
Copy link

I managed to build a project using your lib as an apklib dependency, with mvn install and from eclipse, too. Thanks for your supporting this, really appreciated!

@amlcurran
Copy link
Owner

I CAN FINALLY CLOSE THIS! Thanks everyone

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants