hello, olivier!

how can I help you today?

Hi, the instructions on how to configure the uploadArchives task saved my day. Almost everything else I could find was bitrotted to death.

um, you're welcome!

However I would like to push both a release (at mylib) and a debug version (at mylib-debug) and I can't find out how to dothat.

what does "at mylib" and "at mylib-debug" mean?

In another case I would like to push several release flavors and likewise I have no idea how to do it. I gave up googling because everything is baroque, does not work or both.

I do not mess with flavors in libraries, and so I have no experience with that, sorry

if by "at mylib" and "at mylib-debug", you mean those are two separate artifact names, I do not know how to do that for a single library

I try to keep my library publishing fairly simple

if you have additional questions, go right ahead

sorry, a JS blocker had interfered with the chat functionality

OK

my understanding is that maven can serve only one artifact per directory, so release and debug have to be uploaded to different directories

that's very possible

I don't distribute debug and release versions, so I have no idea how to do that

the release variant of "mylib" goes to "mylib", as per defaults, and I would like the debug variant to go to "mylib-debug" or anything else.

that might be possible, but I do not know how to do that

my experience here is very narrow

that's probably not a common scenario, admittedly. but the flavors one might be a bit more common and should be similar.

it would be nice if you could figure it out at some point

documentation on this is very scant and this is one way your book could add real value

I would place about a 0.1% chance that I will get around to that, sorry

from what I've seen, that whole area is fraught with complications

bummer. meanwhile, in your experience, is the lifecycle stuff in architecture ready for prime time? I wired it up to an AppCompatActivity and it did not work. I saw a bug re. plain Activities but apparently it doesn't work even with AppCompatActivity. and yes I had set it up as a custom LifeCycleObserver as per the docs

make sure you are using 26.1.0

of the support libraries

AppCompatActivity should now be lifecycle-aware

that being said, this stuff still has an alpha label

good. and how is arch coming along? it has been stuck at alpha9 for ages.

well, it bumped to the strange alpha9-1 last week

and alpha9 itself is only a few weeks old IIRC

about four weeks (August 19th)

ok

my guess is that their attention turned to the Paging stuff for a while

and I don't know how many engineers are working on this

plus, unlike ConstraintLayout being tied to Android Studio (and driving deadlines), Google has no obvious pressure to get a significant chunk of the Architecture Components to a 1.0.0

they *did* release a few artifacts as 1.0.0, which ties into the 26.1.0 support libraries point from before

so, if you're planning on shipping your app in 2017, I would not use the Architecture Components just yet

I don't know that even Google has a formal release schedule for these bits

ok. that's a pity because Room is one of the few compelling things I have seen in a while and I'd like to use it. the est, not so much

Room IMO is exactly what an ORM should be

they're doing fairly good scope control on Room with respect to stuff being logged in the issue tracker

and so getting to a 1.0.0 final is clearly a priority objective

I just can't tell you when that will be

it takes care of the CRUD boilerplate but wisely defers to SQL for queries

one last thing: am I the only one to be underwhelmed by RecyclerView? other than pluggable layout managers (finally!) I don't see what it brings to the table. it has *less* functionality than the old ListView

oh, RecyclerView is *much* more flexible than ListView

it is tougher to use "out of the box"

you don't say. I can't believe it forces you to implement single selection yourself

there's little question that they could use more standard implementations of that sort of thing

but still have them be pluggable

akin to how they didn't have divider rows, but had a decorator API with no implementation

yes. it feels half-baked

later, they added a stock implementation for handling simple divider rows, which covers a decent-sized chunk of the use cases

I'd phrase it more as their focus was on extensibility, more so than providing a simple out-of-the-box experience

and that causes some amount of pain

given staffing limits, I don't know that I would have done it differently

but having one more engineer focused on the out-of-the-box experience surely would have helped

and that's a wrap for today's chat

the next chat is Thursday, also at 9am US Eastern

ok, thank you

and, as usual, the transcript will be published to https://commonsware.com/office-hours/ shortly

have a pleasant day!