Closed AlonsoFloo closed 1 year ago
@AlonsoFloo, Thanks for bringing this matter to our attention! To address the issue, we created a pull request at https://github.com/jfrog/artifactory-gradle-plugin/pull/46. Please feel free to review it at your convenience. We'll keep you informed as soon as it gets merged.
Amazing, thanks a lot. Just checked the PullRequest, I saw you added a specific project and UnitTest for Android project.
We are looking forward to integrate it !
Describe the bug
When using the extractor plugin on a multimodule android project with multi-variant, the configuration cannot be resolve
Stacktrace :
To Reproduce
Update the :app:gradle.build file to actualy use the :library module
./gradlew clean artifactoryPublish
Expected behavior
The dependency of each configured module shall be found and uploaded to the artifactory server
Versions
Additional context
Based on this example : https://github.com/jfrog/project-examples/tree/master/gradle-examples/gradle-android-example The submodule "lib" is actually not used, therefore the dependency tree do not reflect a concrete app. Where module actualy are included in the final .apk or .aab file android project produce
Personal analysis Based on the pluging code, but also this issue on the Official gradle/gradle#5953
GradleModuleExtractor.java
is not usable in modern Android projectThe function
getResolvedArtifacts
will not resolve the artefact cause (I quote this comment)