For my part I would prefer to keep the plain kafka namespace, I don't think naming conflicts are a common problem, and I think putting your organization's name into the code is kind of odd (be it com.linkedin or org.apache, neither is relevant to folks wanting to use the code).
No problem making the maven co-ordinates be org.apache.kafka if that helps people. -Jay On Tue, Aug 23, 2011 at 8:17 PM, Chris Burroughs <[email protected]>wrote: > So from what I can tell it's common practice [1] for Java projects to > switch to using the the org.apache namespace. Scala/kafka doesn't even > follow the reverse FQDM convention, so I don't see a need to change the > source code. But what about for packaging? Ought a project depending > on kafka be using: > > <groupId>kafka</groupId> > <artifactId>core-kafka</artifactId> > > or > > <groupId>org.apache.kafka</groupId> > <artifactId>core-kafka</artifactId> > > > [1] http://incubator.apache.org/guides/mentor.html#repackaging >
