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

Issues resolving performance project when name comes after app project alphabetically #102

Open
rbro112 opened this issue Oct 31, 2023 · 1 comment

Comments

@rbro112
Copy link
Contributor

rbro112 commented Oct 31, 2023

A client recently experienced this and set up a repro: https://github.com/ivanalvarado/EmergeTools-Perf-Analysis-Reproducer

After further investigation, it seems Gradle's project resolution runs in an alphabetical manner, so when the performance module's name comes before the app module's name alphabetically, we experience this issue.

@rbro112
Copy link
Contributor Author

rbro112 commented Nov 8, 2023

Unfortunately this is a more complicated issue that will require some bigger changes to solve. Immediately, the easiest workaround to this problem is to simply name the performance project a name which will come after the main app module's alphabetically (i.e. if app module's name is :terrificapp, the performance module would need to come after it alphabetically, i.e. :terrificperformance).

We have long-term plans to address this in a future major version of our Gradle plugin.

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

No branches or pull requests

1 participant