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
Could you reopen this Issue? It is not possible to downgrade Dagger to version 2.0 in my project. And with v2.11 the mapzen library will not build.
My app is also using the kotlin annotation processor and the mapzen library is using the default gradle annotation processor. This combination is failing at the moment.
@BaN4NaJ0e Thanks for the 👍 to this work. Now that we have v1.6.1 out the door, we're going to be going through and upgrading all dependencies to latest versions.
I've created #479 to track the separate but likely related issue for the kotlin annotation processor build failures. Reopening the previous issue would only cause for confusion :)
As a workaround for now I have build the mapzen sdk by myself. I have updated the dagger version inside the MapZen SDK to v2.12 and replaced the annotationProcessor with the Kotlin kapt version. So far everything seems to work. So you guys should have no problems to update all dependencies to latest versions too.
Looking forward for a new MapZen SDK release with the latest depencies. ;) Keep up the good work!
Activity
BaN4NaJ0e commentedon Oct 9, 2017
Could you reopen this Issue? It is not possible to downgrade Dagger to version 2.0 in my project. And with v2.11 the mapzen library will not build.
My app is also using the kotlin annotation processor and the mapzen library is using the default gradle annotation processor. This combination is failing at the moment.
msmollin commentedon Oct 9, 2017
@BaN4NaJ0e Thanks for the 👍 to this work. Now that we have v1.6.1 out the door, we're going to be going through and upgrading all dependencies to latest versions.
I've created #479 to track the separate but likely related issue for the kotlin annotation processor build failures. Reopening the previous issue would only cause for confusion :)
BaN4NaJ0e commentedon Oct 23, 2017
As a workaround for now I have build the mapzen sdk by myself. I have updated the dagger version inside the MapZen SDK to v2.12 and replaced the annotationProcessor with the Kotlin kapt version. So far everything seems to work. So you guys should have no problems to update all dependencies to latest versions too.
Looking forward for a new MapZen SDK release with the latest depencies. ;) Keep up the good work!
msmollin commentedon Oct 23, 2017
@BaN4NaJ0e fantastic! Would you want to submit that as a PR?
BaN4NaJ0e commentedon Oct 24, 2017
All I did was changing the version numbers inside the build.gradle file and added the Kotlin Annotation Processor. So instead of writing:
annotationProcessor 'com.google.dagger:dagger-compiler:2.0'I changed it to:
kapt 'com.google.dagger:dagger-compiler:2.11'Do not forget to add the Kotlin Stuff at the top of the build gradle file:
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-kapt'
That was all!