NativeScript / NativeScript/android
Metadata build task in gradle does not depend on `libs` folder
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 563
- Forks
- 144
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 14
Description
Currently, the buildMetadata task in the app/build.gradle does not depend on changes in the application's App_Resources/Android/libs folder.
The bug is reproduced with the following steps:
- execute
tns build android - add a JAR dependency in
App_Resources/Android/libsin the application's folder - execute
tns build android
After the last build, there would be no metadata for the classes in the added JAR. This is caused by the buildMetadata not being run.
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 in app/build.gradle and inspect the buildMetadata task alongside the application's App_Resources/Android/libs folder. Reproduce the two-build sequence with a newly added JAR, then verify that the metadata build is triggered and includes classes from that dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- build-system, mobile-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100