You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
./nx graph does not detect direct dependency in android gradle project, showing a "flat" graph instead - e.g:
Expected Behavior
NX should detect the dependencies in the gradle project and display them.
For example the example project from the docs detects correctly the dependencies:
<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->
<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->
<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->
## Current Behavior
<!-- This is the behavior we have today -->
## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->
## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->
Fixes#27160
(cherry picked from commit 7c45589)
Current Behavior
./nx graph
does not detect direct dependency in android gradle project, showing a "flat" graph instead - e.g:Expected Behavior
NX should detect the dependencies in the gradle project and display them.
For example the example project from the docs detects correctly the dependencies:
GitHub Repo
https://github.com/spetrov/nx-android
Steps to Reproduce
app
depend on the library - i.e. the app'sbuild.gradle
add in the dependenciesimplementation(project(":mylibrary"))
npx nx@latest init
./nx graph
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: