blundell / release-android-library Goto Github PK

Remote script to create a maven compatible release of an android library (aar)

License: Apache License 2.0

release-android-library's Introduction

release-android-library

🚨 Deprecated 🚨

This script is deprecated in favour of: novoda/bintray-release

Remote script to create a maven compatible release of an android library (aar). This release comes in a zip or exploded form and is only created locally inside your own build folder. You can these use these files to release to JCenter or Maven Central.

Matching blog post here: http://blog.blundellapps.co.uk/locally-release-an-android-library-for-jcenter-or-maven-central-inclusion/

adding to your library

apply plugin: 'com.android.library'

ext {
    PUBLISH_GROUP_ID = 'com.blundell'
    PUBLISH_ARTIFACT_ID = 'example-library-name'
    PUBLISH_VERSION = '1.0.0'
}

android {
    // configs, flavors etc
}

dependencies {
    // dependencies
}

// Copy the file locally and use
apply from: 'android-release-aar.gradle'
// or use the remote copy to keep update with latest changes
apply from: 'https://raw.githubusercontent.com/blundell/release-android-library/master/android-release-aar.gradle'

useage

./gradlew clean build generateRelease

example output

 :engine:zipRelease
 :engine:generateRelease
 Release 1.0.0 can be found at /Users/Blundell/Developer/git_repo/ExampleAndroidLibrary/build/release/1.0.0/
 Release 1.0.0 zipped can be found /Users/Blundell/Developer/git_repo/ExampleAndroidLibrary/build/release-1.0.0.zip

 BUILD SUCCESSFUL
 
 Total time: 23.609 secs

release-android-library's People

Contributors

Stargazers

Watchers

release-android-library's Issues

Task ordering

I am not sure this is really a bug, and I must admit I haven't tried your gradle script yet. But reading the source, I am wondering:
Shouldn't you put zipRelease.mustRunAfter uploadArchives somewhere? I have the impression that with the current code, the zipping could happen before the 'mavening'.

How can I apply obfuscation to my AAR

...is this possible at all?

Bintray error - Add a POM file to the latest version of your package

I am trying to use your remote gradle script and it seems to work great.
A zip file is created with the structure as described in the blog post.

But when I try to add my package to JCenter (manually from the Bintray site) I get the
"Add a POM file to the latest version of your package"
error.

I can see the pom inside the zip but still something is wrong.. maybe the name of the pom file?
Any help will be appreciated

Task 'generateRelease' is ambiguous in root project

After running ./gradlew clean build generateRelease I get the following error message:

FAILURE: Build failed with an exception.

* What went wrong:
Task 'generateRelease' is ambiguous in root project <my project name>. Candidates are: 'generateReleaseAssets', 'generateReleaseBuildConfig', 'generateReleaseResValues', 'generateReleaseResources', 'generateReleaseSources'.

* Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 4.09 secs

As of gradle build 3.0.1 and buildToolVersion 27 there's no zip

Can't find the release-${version} in the build folder. What could go wrong?

Remove parts not required from zip

Hi,

maybe a simple question: Is there a way to exclude artifacts from being bundled into the final ZIP? E.g. I don't want to publish sources and javadoc and debug AAR, so it is a bit cumbersome and error prone to remove them later on from the ZIP

Not Working Locally

Could not get unknown property 'PUBLISH_GROUP_ID' for root project
When I tried it locally

Build fails at generating javadoc if custom libs included

I use recyclerview lib and get an errors like "package android.support.v7.widget not found", "cannot resolve RecyclerView" etc. when run "gradlew clean build generateRelease". Process fails on javadoc task.

Gradle plugin 1.1.0 -- Cannot call getBootClasspath() before setTargetInfo() is called

I'm having an issue syncing my project with my gradle files.

Here's my library module's build.gradle file:

apply plugin: 'com.android.library'

ext {
    PUBLISH_GROUP_ID = 'me.mattlogan.artiste'
    PUBLISH_ARTIFACT_ID = 'artiste'
    PUBLISH_VERSION = '2.0.1'
}

android {
    compileSdkVersion 21
    buildToolsVersion "21.1.2"

    defaultConfig {
        minSdkVersion 10
        targetSdkVersion 21
        versionCode 2
        versionName "2.0.1"
    }
}

apply from: 'https://raw.githubusercontent.com/blundell/release-android-library/master/android-release-aar.gradle'

When I try to sync my project, I see the following error:

This is definitely caused by the android-release-aar task, as the error goes away when I comment out that line.

Include local project library

I have a project library included in my library. Is there a way to have it include in the release ?

Just to be clear, how will gradle manage library dependencies like compile 'com.squareup.picasso:picasso:2.5.0' ? Will gradle download it ?