On 7/15/16, 12:22 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Hi Alex, > >the difference is that the externs will change, the "tiny parts" of >Falcon will probably never change. That's why I would simply like to fire >them out the door and only think about them if we really need to change >something. OK, so do we want externs as part of the falcon source package or should it be its own source package? What do others think? I'd say that once we get closer to having an RC (assuming we get an externs repo and make the associated build changes and we get more kinks ironed out of the examples) then I would be ok with you pushing these artifacts to Maven but having their source in the Falcon source package. Let's see what other folks think, -Alex