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.

Sign up for GitHub

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

Jump to bottom

dexmaker-mockito-inline build fails with Cannot notify listeners of type ProjectEvaluationListener as these listeners are already being notified. #101

Closed
moltmann opened this issue May 2, 2018 · 2 comments
Closed

dexmaker-mockito-inline build fails with Cannot notify listeners of type ProjectEvaluationListener as these listeners are already being notified. #101

moltmann opened this issue May 2, 2018 · 2 comments

Comments

@moltmann
Copy link
Contributor

moltmann commented May 2, 2018

This only happens when syncing gradle files from inside Android Studio. ./gradlew build works. Downgrading to org.jfrog.buildinfo:build-info-extractor-gradle:4.3.0 causes other failures.

This seems to be jfrog/build-info#86

Error:FAILURE: Build failed with an exception.

  • Where:
    Build file '/usr/local/google/home/moltmann/projects/dexmaker/dexmaker-mockito-inline/build.gradle' line: 66

  • What went wrong:
    A problem occurred configuring project ':dexmaker-mockito-inline'.

Failed to notify project evaluation listener.
A problem occurred configuring project ':dexmaker'.
> Cannot notify listeners of type ProjectEvaluationListener as these listeners are already being notified.
A problem occurred configuring project ':dexmaker'.
> Cannot notify listeners of type ProjectEvaluationListener as these listeners are already being notified.

  • 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

BUILD FAILED in 0s

@drewhannay Any idea how we can work around this?
@drewhannay
Copy link
Contributor

@moltmann I was seeing this too, but didn't have time to investigate yet. Is #102 supposed to fix this?

@moltmann
Copy link
Contributor Author

moltmann commented May 3, 2018

No. #102 fixes issues when running the tests out of Android Studio. AS really does not like symlinks. As as I understand there seem to be two solutions to this.

  • Downgrade to org.jfrog.buildinfo:build-info-extractor-gradle:4.3.0
  • Move all the publishing into the top level gradle file

drewhannay pushed a commit to drewhannay/dexmaker that referenced this issue May 19, 2018
Disable Gradle configureondemand - Fixes linkedin#101
0a9bce3 
Configuration on demand + the JFrog plugin seems to cause
Gradle sync issues in Android Studio. Disabling this option
and disabling the Configure on Demand setting in Android Studio
preferences fixes the issue.

This project doesn't need Configure on Demand anyway, so there's
no downside to disabling this option, even if Gradle and JFrog
come up with a different workaround later.

For more details, see:
jfrog/build-info#86
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@drewhannay @moltmann