-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for release into maven repository #16
Comments
@shevek we'd also love to get a new release of your plugin. We need to pick up ASM8 support upgrade Please release 1.0.2 from current master. |
I hope this will help you #20 but there is current no publish included |
Thanks for the new input. Would you be able to provide an example on how to use the jarjar 1.0.3 in gradle. When I change the aTalk build.gradle to
} Gradle sync immediately exit with the following errors: A problem occurred configuring project ':buildSrc'.
=============== I also made refer to the following file, but none help. |
Should we try to publish this repo from a fork under a different maven coordinate? |
I suggest moving to https://github.com/johnrengelman/shadow That's what we ended up doing on my team. |
I tried on aTalk project but facing problem. Any advice will be appreciated. Unable to use shadow to achieve the same result as jarjar tools for aTalk project #761 |
Appreciate if you can consider release your jarjar libraries into the official maven repository, so aTalk can refer to it.
aTalk release the apk into android playstore and Fdroid. Fdroid has restriction on inclusion of any pre-built jar into the source.
aTalk is an open source: https://github.com/cmeng-git/atalk-android
Currently aTalk build.gradle is making reference to 'org.anarres.jarjar' jarjar, but seems this tool has not been updated for a while and is facing some problem i.e. NullPointerException in LambdaClass.createLambdaImplMethodTarget
=================
buildscript {
repositories {
google()
jcenter()
}
}
apply plugin: 'org.anarres.jarjar'
The text was updated successfully, but these errors were encountered: