NativeScript / NativeScript/android
Missing custom local dependencies should fail the build
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 563
- Forks
- 144
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 14
Description
Currently, if in the app.gradle there is a custom dependency like:
implementation fileTree(dir: '/test/test', include: ['test.jar']) and it is not on the file system, the build should fail instead of finishing and failing at runtime.
Contributor 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.
Research direction
Start with the app.gradle dependency declaration using fileTree and reproduce the case where /test/test/test.jar is absent. Trace how the build handles that missing custom local dependency, then verify that the build fails instead of completing and failing at runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100