Giter Club home page Giter Club logo

multi-flavor-lib-demo's Introduction

Publish multi-flavor android libraries with jitpack.io

This project demonstrates how to publish multi-flavor android libraries to jitpack.

Release

The gist of it is using dcendents gradle plugin and understanding that jitpack calls "./gradlew install" if left to auto-config

What's here:

  • on the multi-lib branch
    • a project that publishes 2 libraries (matterlib and energylib) each with their own flavors
    • a demoapp that gets to use the libs
  • on the single-lib branch
    • just one library with flavors
    • the demoapp that uses it

There's a difference in the way jitpack names the artifacts for single vs multiple library repositories.

Flavor coordinates on jitpack

Single library project

If the project includes a single library, the repository name gets to be the artifactId, even if you specify otherwise.

To include a flavor as a dependency:

implementation "com.github.<USER>:<REPO>:<git-tag>:<flavor-name>@aar"

If the library has a defaultPublishConfig, there should be an artifact with the normal jitpack coordinates:

implementation "com.github.<USER>:<REPO>:<git-tag>"

An example for this setup is in the single-lib branch of this project.

multi-lib project

If the project produces multiple libraries, the coordinates change a little.

When working with a flavor of the library, include it like this:

implementation "com.github.<USER>.<REPO>:<library-module>:<git-tag>:<flavor-name>@aar"

And if the library has a defaultPublishConfig, there should be an artifact with the following coordinates:

implementation "com.github.<USER>.<REPO>:<library-module>:<git-tag>"

An example for this setup is in the multi-lib branch of this project.

jitpack.io is great for OSS.

Note

You can see the build logs for this sample library here: https://jitpack.io/#mirceanis/multi-flavor-lib-demo

multi-flavor-lib-demo's People

Contributors

mirceanis avatar rahulraj64 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

multi-flavor-lib-demo's Issues

Task with name 'bundleSolidRelease' not found in project ':matterlib'.

Hi could you explain what is happening here? When I checkout the single lib branch, I get an error that reads:
Task with name 'bundleSolidRelease' not found in project ':matterlib'.

if (android.productFlavors.size() > 0) {
    android.libraryVariants.all { variant ->
        if (variant.name.toLowerCase().contains("debug")) {
            return
        }

        def bundleTask = tasks["bundle${variant.name.capitalize()}"]

        artifacts {
            archives(bundleTask.archivePath) {
                classifier variant.flavorName
                builtBy bundleTask
                name = project.name
            }
        }
    }
}

Can't see what I am doing wrong really this is all pretty confusing, I get the same error in my project ๐Ÿ˜„ I would like to publish build variants for my library.

Build product flavour with transitive dependencies

When we build the library without specifying the product flavor, it correctly builds the library module specified using 'defaultPublishConfig' (AAR file along all of the transitive dependencies specified in that module) so that the consumer of the library do not require to include the dependencies of the library module. This works fine.
implementation "com.github.mirceanis.multi-flavor-lib-demo:matterlib:$library_version"

But, when we try to build a particular product flavor by using
implementation "com.github.mirceanis:multi-flavor-lib-demo:$library_version:solid@aar"
It does not include the transitive dependencies of the library module and the consumer of the library gets runtime exceptions stating that the class files could not be found. So when we build the product flavor, how to include all of the dependencies specified inside that library so that the consumer of the library do not require to include the dependencies themselves?

package sources

demo a way to package sources properly so they are easily linkable in IDE

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.