How do I import all library modules in one line for version 0.2.0?

[vestrel00]

Problem

Importing all modules is not working when doing,

dependencies {
    implementation 'com.github.vestrel00:contacts-android:0.2.0'
}

However, it still works for 0.1.0.

WTF?

EDIT: The real issue is discovered starting here: #203 (comment)

Panic mode

So, the 0.2.0 release in JitPack is showing ✅ for successful deployment.

However, today I did a sanity check by attempting to pull it into a new project. The build fails with...

Looking at the JitPack logs...

It seems like it should have succeeded...

This really sucks. I'll have to figure this out QUICKLY before people really try to download it and realize 0.2.0 will not be downloadable.

[vestrel00]

First thing I'll try is to just rebuild the release tag in JitPack...

[vestrel00]

First thing I'll try is to just rebuild the release tag in JitPack...

That didn't work lol. Same issue.

Next, I'll try to debug this locally. Running; ./gradlew clean build publishToMavenLocal seems to reproduce the issue.

Notice the unspecified should really be the version 0.2.0.

So, what caused this regression??? Taking a look at the changes; 0.1.10...0.2.0

The only things that could have affected this is the upgrade from AGP 7.0.3 -> 7.1.0 and/or Gradle wrapper 7.0.2 -> 7.2.

I'll take a look at what happens if I revert these upgrades..

[vestrel00]

Okay. Reverting those changes DID NOT fix the issue. WTF! I also checked out the 0.1.10 tag and the issue is there too even though it was not there before!!! So, something must have changed outside the project's configuration... But what...

[vestrel00]

The only other thing I can think of is the maven-publish plugin! It is currently declared as...

plugins {
    ...
    id 'maven-publish'
}

The version of the maven-publish plugin is NOT SPECIFIED!!!

[vestrel00]

I took another look at the JitPack docs on publishing libraries... It seems that they have changed it... https://developer.android.com/studio/publish-library/configure-pub-variants#single-pub-var

This step was not there as far as I remember several months ago when I integrated JitPack...

[vestrel00]

Also, it seems like the publication code has changed too; https://developer.android.com/studio/publish-library/upload-library#create-pub

This is different from what are currently doing...

[vestrel00]

I set our publish code as...

publishing {
    publications {
        release(MavenPublication) {
            afterEvaluate {
                from components.release
            }
        }
    }
}

I omitted the groupId, artifactId, and version. I'm still getting unspecified but hopefully GitHub+JitPack will fill that in for me. I'll give it a try.

[vestrel00]

That did not work... This could be a JitPack issue where it is no longer filling out the groupId, artifactId, and version...

[vestrel00]

Okay... Maybe I'm getting the issue all wrong. I tried to reproduce the issue using the same configuration I have in a sample Jitpack project I created several months ago, https://github.com/vestrel00/jitpack-publish-sample, but I'm not able to...

I don't think that I'll be able to debug this issue locally. I will need to retry reverting the upgrade from AGP 7.0.3 -> 7.1.0 and/or Gradle wrapper 7.0.2 -> 7.2 and run it in JitPack.

[vestrel00]

So, the real issue is in the way the dependencies are declared in the consumer Gradle file. The following works perfectly...

implementation 'com.github.vestrel00.contacts-android:async:0.2.0'
implementation 'com.github.vestrel00.contacts-android:core:0.2.0'
implementation 'com.github.vestrel00.contacts-android:customdata-gender:0.2.0'
implementation 'com.github.vestrel00.contacts-android:customdata-googlecontacts:0.2.0'
implementation 'com.github.vestrel00.contacts-android:customdata-handlename:0.2.0'
implementation 'com.github.vestrel00.contacts-android:customdata-pokemon:0.2.0'
implementation 'com.github.vestrel00.contacts-android:customdata-rpg:0.2.0'
implementation 'com.github.vestrel00.contacts-android:debug:0.2.0'
implementation 'com.github.vestrel00.contacts-android:permissions:0.2.0'
implementation 'com.github.vestrel00.contacts-android:test:0.2.0'
implementation 'com.github.vestrel00.contacts-android:ui:0.2.0'

BUT the following does not work...

implementation 'com.github.vestrel00:contacts-android:0.2.0'

However, it does work for the previous release...

implementation 'com.github.vestrel00:contacts-android:0.1.10'

[vestrel00]

Downgrading AGP from 7.1.0 -> 7.0.3 and the Gradle wrapper 7.2 -> 7.0.2 does NOT fix the issue.

[vestrel00]

This might be similar to #179

This might just be an issue with JitPack? Hopefully, the issue will just magically go away...

For now, I'll just update the README installation instructions to instruct consumers to NOT do implementation 'com.github.vestrel00:contacts-android:0.2.0'.

I made this a discussion and set the title to "Installing all dependencies using implementation 'com.github.vestrel00:contacts-android:0.2.0' is not working". I also posted a help wanted label 🤞

[vestrel00]

The only thing I can think of now is perhaps this issue only occurs if the library reaches a certain number of modules. In the previous release (0.1.10), there were only 8 modules. Now in 0.2.0 there are 11 modules. This is something worth exploring. It's a quick check. I can just delete the new custom data modules introduced in the new release one by one until it hopefully starts working again.

If my theory is correct, I should use the official sample JitPack project to reproduce the issue https://github.com/jitpack/android-example/

[vestrel00]

So, my theory is correct. The issue only occurs if there are more than 10 library modules published...

I'll try to reproduce it in the official sample JitPack projects;

• https://github.com/jitpack/android-example/
• https://github.com/jitpack/gradle-modular

Then, file a bug ticket in https://github.com/jitpack/jitpack.io

[vestrel00]

Interesting. I'm not able to reproduce it in https://github.com/jitpack/android-example/ I'll take a deeper look tomorrow.

[vestrel00]

I should probably check if the issue just went away tomorrow...

I just ran the release build again. Will check tomorrow!

[vestrel00]

It works fine in my new temporary project but not the sample in this project. Hmmm...

[vestrel00]

Maybe, the issue only occurs on certain consumer configurations because something might have changed with the publish outputs. I'll look into this.

[vestrel00]

Okay. I finally figure it out!

The issue is not present if our library users use the new dependency resolution management; https://developer.android.com/studio/build/dependencies#remote-repositories

This is where the Jitpack repository needs to be added. Inside settings.gradle, it should look like,

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        ...
        maven { url "https://jitpack.io" }
    }
}

This only applies to releases starting with 0.2.0. Prior releases can still be imported using the old way in the root build.gradle,

allprojects {
    repositories {
        ...
        maven { url "https://jitpack.io" }
    }
}

I wonder if this entire situation must have been due to an update in JitPack or is it really because I updated the library project's AGP to 7.1.0? Whatever, it doesn't matter now. I wasted enough time on this already.

[vestrel00]

I'll update the README and write up a docs page for this.

[vestrel00]

It's done 🤗 https://vestrel00.github.io/contacts-android/setup/installation/#installing-all-modules-in-one-line