Nah, I just wanted to show an example of Library with Classes distributed as llb's.
It was on me at the time, but that example is for reuse, hence the namespacing.
I have played with both, namespacing and not for Plugin Classes, I don't think it matters too much.
Well if they are truly Plugins then they do not have to be part of the application build process, only the 'interface' Class does.
However, it could be (both part of, and scripted) - it would depend on the application.
I don't have to create a unique source distribution for each llb, I can do multiple llb's in one source distribution.
Very clever