soundcloud / delect Goto Github PK

Or does it requires any others configuration to use?

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.

• What went wrong:
  Execution failed for task ':core-ui:kaptDebugKotlin'.

A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptWithoutKotlincTask$KaptExecutionWorkAction
java.lang.reflect.InvocationTargetException (no error message)

I'm pretty sure in a similar fashion the Moshi code generation could be changed to reflection.

Do you think it is within of scope of this plugin or you would rather have this as a different plugin?

Reading https://stackoverflow.com/questions/10483053/generated-annotation-how-do-we-use-it I'm not sure if it is good/necessary practice at all.

I leave it here for the discussion.

Hi

Will it have any impact on App Launch time ??

These are essential for me to have speed up the builds.

There's no code in here aside from buildSrc

This happens after applying id("com.soundcloud.delect") (0.2.0) in root project's build.gradle file, and running the build with ./gradlew app:assembleDevDebug -Pdagger.reflect=true. We have a mix of android-library and kotlin subprojects.

Output (app is the only application module in the project):

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:prepareLintJar'.
> Found more than one jar in the 'lintChecks' configuration. Only one file is supported. If using a separate Gradle project, make sure compilation dependencies are using compileOnly

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:prepareLintJar'.
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:187)
        at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:263)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:185)

Having an option for something like ./gradlew build -Pdagger.reflect=true would greatly benefit plugin flexibility, I think.

Right now the activation of the plugin is triggered through the gradle.properties property dagger.reflect. In certain circumstances it would however be cool to be able to dynamically trigger this option, either by a project parameter given to the command line or by redirecting to a file-based setting other than gradle.properties.

When using delect with dagger.reflect=true, Android Studio doesn't automatically pick up the location of the generated Component. Can this be fixed or is there something I need to set?

With no entry for dagger.reflect in gradle.properties:

vs

With dagger.reflect=true in gradle.properties:

Hello!

Your plugin is very useful, but do you plan to support full dagger reflection?