-
Notifications
You must be signed in to change notification settings - Fork 35
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
0.3.0 fails to build with kapt #48
Comments
Thank you for reporting, I am working on a minimal project to try and reproduce this - will report back if I need more details. May I know if you have |
Yeah that's with it enabled, and the dagger argument is set to |
So it works without full graph validation? By any chance Seems related to google/dagger#970. The only place I access raw I'll work on a gradle task to export info for issues to avoid back and forth in the future. |
Let me try to build with the dagger option on bit without scabbard enabled
and see if it still happens
…On Thu, May 21, 2020 at 12:42 AM Arunkumar ***@***.***> wrote:
So it works without full graph validation?
By any chance LogSyncBaseModule has a binding exposed utilizing
slack.telemetry.Metrics but that class is in a different
module/transitive dep of another module?
Seems related to google/dagger#970
<google/dagger#970>. The only place I access
raw Types apart from already parsed dagger ones in when I try to parse
simple names. I will try to confirm this with a sample when I get time.
Meanwhile could you let me know if setting qualifiedNames true in
scabbard block works?
I'll work on a gradle task to export info for issues to avoid back and
forth in the future.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKMJPVTD3FDHTC5TAG6X53RSSWJ7ANCNFSM4NEMCB2A>
.
|
Building with scabbard disabled but the dagger option for full binding
graph validation appears to work fine
…On Thu, May 21, 2020 at 12:57 AM Henri Sweers ***@***.***> wrote:
Let me try to build with the dagger option on bit without scabbard enabled
and see if it still happens
On Thu, May 21, 2020 at 12:42 AM Arunkumar ***@***.***>
wrote:
> So it works without full graph validation?
>
> By any chance LogSyncBaseModule has a binding exposed utilizing
> slack.telemetry.Metrics but that class is in a different
> module/transitive dep of another module?
>
> Seems related to google/dagger#970
> <google/dagger#970>. The only place I access
> raw Types apart from already parsed dagger ones in when I try to parse
> simple names. I will try to confirm this with a sample when I get time.
> Meanwhile could you let me know if setting qualifiedNames true in
> scabbard block works?
>
> I'll work on a gradle task to export info for issues to avoid back and
> forth in the future.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#48 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAKMJPVTD3FDHTC5TAG6X53RSSWJ7ANCNFSM4NEMCB2A>
> .
>
|
Thanks. Any luck with setting |
Still fails with that set to true as well :/ |
Thanks, I will investigate. Just to confirm scabbard's |
I have the same result regardless I think. Can confirm tomorrow. These
tests for sure at least cover with it set to true
…On Thu, May 21, 2020 at 3:58 AM Arunkumar ***@***.***> wrote:
Thanks, I will investigate. Just to confirm scabbard's
fullBindingGraphValidation is set to false right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKMJPV7A3H445YVH4KZFNTRSTNKFANCNFSM4NEMCB2A>
.
|
@arunkumar9t2 I have similar issue related to SLF4J binding:
I completely removed dependency to
|
Same issue here...
|
Will look into this soon, @Morteza-Rastgoo, could you please run the build with @ultraon From a cursory look, seems unrelated to this issue. I will create a separate issue for that log4j error. |
The text was updated successfully, but these errors were encountered: