-
Notifications
You must be signed in to change notification settings - Fork 2k
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
NoSuchMethod Exception #113
Comments
I am also seeing this when using snapshot: Maybe related to google/auto@e02e2a8? |
Yeah seems like asTypeElements method changed - google/auto@e02e2a8#diff-117761445d686cc88f0b75d965af5a1aL466 |
What's the correct way to set up gradle to use the jar files to avoid SNAPSHOT issues like this? I've tried
but it doesn't seem to be working. It compiles without error but it force closes when I run the app |
You haven't included the dependencies of the |
Thanks. Adding the following based on the pom.xml file worked (to use the dagger-compiler jar, sort of)
However, since dagger-compiler depends on the snapshot version of auto-common anyway, back to square one I guess! For others running into this
|
Damn, this is bad, one snapshot library depends on another snapshot library.. What about semantic versioning and/or fixed inner dependencies? I don't want to talk about #109, but inner snapshot dependencies — serious problem for production |
Ugh, please no. A shaded compiler jar is all that's needed. |
Downloading jars... Interesting, how many developers are currently thinking "WTF with my build?" :) |
To expand a bit on the workaround, you need to download and reference three separate jars, temporarily replacing the dagger-compiler dependency with the following:
|
With the above workaround I was running into apt ('com.google.dagger:dagger-compiler:2.0-SNAPSHOT') {
exclude group: 'com.google.auto'
}
apt files('libs/auto-common-1.0-20150122.001631-7.jar') so that requites only one jar instead of three, hopefully this gets fixed soon |
IMHO it might be done easier, since fortunately dagger-compiler has it's Here's how I changed my
Actually, this is madness (#109). But it works. |
+1 I have the same problem. |
I was seeing this error earlier as well. Just out of interest, was that causing peoples |
I am in the process of exporting a new update - this was the syncs getting out of sync, and I"ll fix. I'm also going to be jarjar-ing the binary so when we publish a snapshot (or release) it'll be resistent to dependency version skew. |
👍 |
Thanks @cgruber! |
Thank you for looking into this. |
PR #115 fixes this. Should merge shortly. |
So - apologies for all of this. Having seen these interactions, I'm going to do a little work on my end to keep us from dealing with this sort of skew. But the new version should be out, and it should work. |
@cgruber it's okay for alpha-beta-whatever-snapshot, at least, Dagger didn't delete /usr/ folder 👍 |
Thanks! 👍 |
Appreciated |
It's alive again! Thanks @cgruber ! |
👍 💯 |
I'll close this now. As this is working with the latest snapshot. Thanks @cgruber (and co). |
I think this is related to the latest google/auto snapshot pushed today. But
dagger-compiler
throws the following error:The text was updated successfully, but these errors were encountered: