Gradle is just a corporate thing at Netflix. FYI - I'm going to put Curator (my ZooKeeper lib) into Incubator and when I do I'll switch to Maven.
My suggestion is for me to add any features from Governator that you folks like into Onami (Warmup and LazySingleton come to mind). As I mentioned in my other message I'd like to make sure Onami can support the reasons I created Governator: to wit… At Netflix we have a concept of "library" which is a Jar which exposes a specific Interface and one or more properties files. The convention (prior to Governator) was that apps would be responsible for initializing the library. If an app used multiple libraries then all would have to be initialized in the right order, etc. You guys know all about this. I looked around the net and guiceyfruit seemed to be mothballed and nothing else did all the things I needed, thus Governator. I guess Onami was 6 months too late for me ;) As an aside, have any of you thought about object creation ordering? That's been a big problem for us. I've had to resort to child injectors which have had lots of annoying side effects. -Jordan On Feb 22, 2013, at 12:56 AM, Eric Charles <[email protected]> wrote: > The less easy points I see are: > > - All Netflix opensource projects [3] (I use a few of them) rely on Gradle, > and Onami is maven minded. > - Collaboration/Convergence is a nice word for something more concrete which > would be like Neflix contributing in the sandbox to finally migrate in Onami > trunk...
