Could not resolve all artifacts - com.github.chrisbanes:PhotoView:2.3.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- build-system, mobile-dev
Research direction
Start by reproducing the app:devDebugRuntimeClasspath failure in the dataBindingMergeDependencyArtifactsDevDebug task, using the reported PhotoView 2.3.0 dependency and Gradle 7.4.2. The report names no repository files or tests, so first determine whether the failure is reproducible and identify the missing dependency-resolution details; done means the dependency resolves successfully or the cause is documented.
Written by the indexing model from the issue text.
Description
Today we started with the following issues in our build! Do you have any issues with this repository?
Thanks!
**Task :app:dataBindingMergeDependencyArtifactsDevDebug FAILED**
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:dataBindingMergeDependencyArtifactsDevDebug'.
> Could not resolve all dependencies for configuration ':app:devDebugRuntimeClasspath'.
> Could not determine artifacts for **com.github.chrisbanes:PhotoView:2.3.0**: Skipped due to earlier error
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
* Get more help at https://help.gradle.org/
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.4.2/userguide/command_line_interface.html#sec:command_line_warnings
- Dominant language
- Java
- Stars
- 18.8k
- Forks
- 3.9k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Baseflow/PhotoView
-
PohenOpen
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
KhanOpen
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
.Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
-
842Open
Difficulty 1/5 Under an hour Newbie friendliness 10/100
-
OkOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
All issues in Baseflow/PhotoView
Similar issues
-
1.0.0-rc2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/dpdp-accelerator#377 ·
Maintainers usually reply within 1 day
-
area/dependencies backport/26.4 kind/cve severity/high source/scan-dependencies status/triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
(primitive-collections-base) Use `NumberInput` to parse numeric map keys, as `jackson-databind` doesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FasterXML/jackson-datatypes-collections#270 ·
Maintainers usually reply within 1 day
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day