You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Chris Burroughs <ch...@gmail.com> on 2011/08/24 05:17:41 UTC
Namespace/Packaging
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
Re: Namespace/Packaging
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
The only problem I can foresee with keeping the old maven coordinates is that as I walk the maven coordinate space for Kafka there's no way for me to easily see which are the old LinkedIn releases and which are the new ASF releases. Placing the releases in a new coordinate space would solve that problem.
Regards,
Alan
On Aug 30, 2011, at 9:50 AM, Jay Kreps wrote:
> 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
> <ch...@gmail.com>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
>>
Re: Namespace/Packaging
Posted by Jay Kreps <ja...@gmail.com>.
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
<ch...@gmail.com>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
>
Re: Namespace/Packaging
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
You'd think so but the documentation seems to be pretty clear, it's optional. How odd.
Regards,
Alan
On Aug 23, 2011, at 9:35 PM, Henry Saputra wrote:
> I think it has to be <groupId>org.apache.kafka</groupId> to make sure
> maven could resolve to the right namespace in the central repo
>
> - Henry
>
> On Tue, Aug 23, 2011 at 8:17 PM, Chris Burroughs
> <ch...@gmail.com> 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
>>
Re: Namespace/Packaging
Posted by Henry Saputra <he...@gmail.com>.
I think it has to be <groupId>org.apache.kafka</groupId> to make sure
maven could resolve to the right namespace in the central repo
- Henry
On Tue, Aug 23, 2011 at 8:17 PM, Chris Burroughs
<ch...@gmail.com> 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
>