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

"Could not resolve" #10

Open
yoavain opened this issue Dec 24, 2014 · 1 comment
Open

"Could not resolve" #10

yoavain opened this issue Dec 24, 2014 · 1 comment
Labels
enhancement

Comments

@yoavain
Copy link

yoavain commented Dec 24, 2014

I would love to have an easy way to find errors. Currently I need to search for "Could not resolve"
@rholder
Copy link
Owner

rholder commented Dec 24, 2014

The custom Gradle model that passes the dependency information back up to the tree for rendering carries that message with it. There should be a way to detect that and output it in the log where it would be more apparent that resolution failed.

rholder added a commit that referenced this issue Apr 27, 2015
@rholder
upgrade internal tooling API to use Gradle 2.3 for #11, upgrade Gradl…
9bccd39 
…e Wrapper to 2.3, add note about #10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yoavain @rholder