I believe that there is a bit of confusion over the whole project structure and configuration. UPDATE - since the time of this posting, there have been much progress in the gradle build process, thus this answer might not be the recommended best practice and new changes might even brake it. The problem is that for the main project I can use this Build types to configure differently the application for different scenarios, but how can I do the same for the Library Project?īecause at the moment from what I read in the library only will use the debug mode while testing. Public static final boolean USE_DEBUGING = false Public static final boolean USE_DEBUG_LOGGING = false Public static final boolean USE_LOGGING = false Public static final boolean USE_ANALYTICS = true Public static final boolean USE_REPORTING = true Release -> java -> config -> PlayerEnvConfig Structure of the files: src - > debug -> java -> config -> PlayerEnvConfig In the Library, when running in debug mode, then print all the logs so I can see them while developing. The problem is that how I can do the same for a library project? I created this library for this project and I would like to setup different Build Variants for different scenarios. With Gradle I can setup different Environmental Configuration (with a class inside a config file) for the main application using the Build Variants so I can execute code according to this variables. I am trying to configure with Gradle a project which contains some external libraries.
0 kommentar(er)
