Skip to content
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

Dependency conflicts #2

Open
samuelashraff opened this issue Oct 15, 2024 · 1 comment
Open

Dependency conflicts #2

samuelashraff opened this issue Oct 15, 2024 · 1 comment

Comments

@samuelashraff
Copy link

samuelashraff commented Oct 15, 2024

Hi,

I downloaded the source code from here and did all of the necessary steps. I then changed the build variant to release and ran the application. I then encountered the following dependency conflicts:

`Task failed with an exception.
* What went wrong:
Execution failed for task ':app:mergeReleaseJavaResource'.

Could not resolve all files for configuration ':app:releaseRuntimeClasspath'.
Could not find com.blankj:utilcode:1.30.6.
Searched in the following locations:
- file:/home/sas/.m2/repository/com/blankj/utilcode/1.30.6/utilcode-1.30.6.pom
- https://jitpack.io/com/blankj/utilcode/1.30.6/utilcode-1.30.6.pom
- https://repo.maven.apache.org/maven2/com/blankj/utilcode/1.30.6/utilcode-1.30.6.pom
- https://jcenter.bintray.com/com/blankj/utilcode/1.30.6/utilcode-1.30.6.pom
- https://dl.google.com/dl/android/maven2/com/blankj/utilcode/1.30.6/utilcode-1.30.6.pom
Required by:
project :app > com.litongjava:litongjava-android-utils:1.0.0
Could not find com.mylhyl:acp:1.1.5.
Searched in the following locations:
- file:/home/sas/.m2/repository/com/mylhyl/acp/1.1.5/acp-1.1.5.pom
- https://jitpack.io/com/mylhyl/acp/1.1.5/acp-1.1.5.pom
- https://repo.maven.apache.org/maven2/com/mylhyl/acp/1.1.5/acp-1.1.5.pom
- https://jcenter.bintray.com/com/mylhyl/acp/1.1.5/acp-1.1.5.pom
- https://dl.google.com/dl/android/maven2/com/mylhyl/acp/1.1.5/acp-1.1.5.pom
Required by:
project :app > com.litongjava:litongjava-android-utils:1.0.0`

Is this a known bug, and if so, how can I fix this?

@samuelashraff
Copy link
Author

Update: got this to work by adding the following parameters to the org.gradle.jvmargs setting in gradle.properties:

--add-exports=java.base/sun.nio.ch=ALL-UNNAMED \ --add-opens=java.base/java.lang=ALL-UNNAMED \ --add-opens=java.base/java.lang.reflect=ALL-UNNAMED \ --add-opens=java.base/java.io=ALL-UNNAMED \ --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant