Scabbard applies itself even when dagger is not present/used about scabbard

[arunkumar9t2]

Thanks, noted. Will target a fix for 0.3.1.

[arunkumar9t2]

I took at shot at this in #53 but it is not fully fixed yet.

New behaviors

1. Scabbard will lazily apply its dependencies only when the configuration is resolved and dagger is present in the project.
2. For Java projects, compiler arguments will be added lazily and only if dagger is there.
3. Kapt is a different story
   • Kapt eagerly evaluates and applies the kapt arguments during plugin application. This means I have to pass arguments very early but at that time dependencies might not be available. Technically I can do configuration.dependencies.all {} or whenObjectAdded but that cause eager evaluation and I want to avoid it for now. Created https://youtrack.jetbrains.com/issue/KT-39521
   • I thought The following options were not recognized by any processor warning was spit out based on supported options alone but it seems to check for supportedTypes as well. Checking for dagger presence alone might not be sufficient to avoid this error. Failing functional test.

I will keep this open and look for any workaround.

[arunkumar9t2]

Update: I saw this JetBrains/kotlin@19708cf and also now Kapt options are using provider instead of evaluating eagerly. I will investigate if this can be fixed soon,

[ruieduardosoares]

@arunkumar9t2 i also have this issue an nothing is being generated in kapt3/classes/ folder.