hello, Scott!

hello!

how can I help you today?

you ever use travis?

nope, sorry

ok next question

we talked about using the maven repo for release builds, and local modules for debug last time.

I implemented debugImplementation... and releaseImplementation... for the sdk

however, there are other variants

staging for example

is that a build type or a product flavor?

build type

What I ended up doing is defining a boolean (USE_MAVEN) at the top of the build script and setting it to true in the release build variant definition

false otherwise

then I put an if statement in the dependencies block

It seems to work, but doesn't seem elegant

why not just add a stagingImplementation line?

if staging is a build type, it's a peer of debug and release

what does it mean to be a peer?

debug and release are build types

staging is a build type

so, all three are build types

ok

if you are using debugImplementation and releaseImplementation, then stagingImplementation would seem to be what you are missing

well we have... 5 build variants and 2 flavors

do you mean 5 build types? with 2 flavors, the count of build variants would have to be even

I guess so. 5 build types, 2 flavors, so 10 versions of the library

right

in principle, you would need five editions of the ...Implementation line: debugImplementation, stagingImplementation, releaseImplementation, and two more for whatever those other build types are named

there may be ways to simplify that, but I haven't had a need for that many build flavors, so I am not certain what the options are

ok

I'll stick with this boolean then. The main module has to define the other modules, so that would be something like 5 * 4 lines for the dependencies is I specified each build type

next question

I think I know the answer to this, but I'm having a hard time keeping all of this stuff straight

the repositories defined by my sdk are not preserved in the packaging process. Is that right?

correct

why is that?

security reasons?

¯\_(ツ)_/¯

that would be a question for the people who developed Maven

ok

next question

In Android Studio, I can press cmd + option + L to autoformat the focused file

it's an option in the Code menu I think

yes

I would like to make it so that ./gradlew lint fails if that code formatting would have any work to do.

I do not know how

you're looking for something like ktlint

oh, wait -- which language are you using again?

java

ah, ok, ktlint is for Kotlin

something like Checkstyle might have a Lint-style Gradle task for Java -- I have never looked for one

there is nothing built into Android Studio, but you should be able to find a Gradle plugin that does what you want for Java

ok I'll look around.

I posted in the /r/androiddev hiring thread.

I'll let you know next week if I get any bites.

sounds good! best o' luck!

aight

well that's it for me. Have a good night!

you too!