Martin Egri

Sorry for not getting back sooner. So what I have right now is a way to reflect on Scala type members a la carte. My issue is that tying this...

What do we make of this? :)

Alright, I'll retrofit is as far as I can and create a branch!

I'm interested in a discussion about this! One idea: 1. Look for a source-file containing `object Plugins extends ` from one or several paths (~/.cbt, /usr/local/.cbt etc) 2. If found,...

Good argument! A .gitignored template file could be forcibly added to the repository instead of having it generated. Another issue that comes to mind is scoping: most plugins should be...

Maybe I'm overthinking it. My reasoning was that you may want to enable some plugin for all `BaseBuild`s in a multi-project build, while another plugin should only be registered once...

I have a working stage2 plugin in dev right now, but I'm not clear on whether you want this to be a plugin available to users of cbt, or if...

Also, I see a lot of common code between compiler plugins at the moment. These could be factored out to a base trait `CompilerPlugin`.

I'm not sure I like this idea. It seems to me like seed would become a stepping-stone to other build tools, when it is actually a competent build tool in...

I'm having a try at the first of those checkboxes and have some questions: * Should I "inherit" the compilerDeps at the parse step ([processBuild](https://github.com/tindzk/seed/blob/7fa092f606180f8d03abcde5c52b8ec2f3de2e69/src/main/scala/seed/config/BuildConfig.scala#L53-L67)), at the resolution step ([compilerDeps](https://github.com/tindzk/seed/blob/7fa092f606180f8d03abcde5c52b8ec2f3de2e69/src/main/scala/seed/artefact/ArtefactResolution.scala#L105-L135)),...