Apache Directory Project - Re: Naming conventions for artifactIds, groupIds and how this relates

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > January 2006 > Re: Naming conventions for artifactIds, groupIds and how this relates





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: Naming conventions for artifactIds, groupIds and how this relates
Alex Karasulu

2006-01-24, 5:47 pm

Jose Alberto Fernandez wrote:

>
>This is the only one that makes sense in my opinion. It is short and
>informative enough.
>
>
>
>
>None of them sound right. I do not think you need to say that is a
>codec-filter, you just need to say it is a bridge between mina and
>netty. The details of the implementation do not need to be transparent
>on the name of the artefact.
>
>So something like:
> <artifactId>mina-netty</artifactId>
>
>Should be good enough.
>
>


Exactly, re: "The details of the implementation do not need to be
transparent

on the name of the artifact."

In the same light other modules like the ans1 and ssl modules not have filter or codec added to the artifactId. There should be documentation on the site or a README/README.layout file in mina top level that can explain the details if people have any que
stions.

We are going to far ... playing with these names. Let's add a readme, shorten the names and let's stabilize.

Alex



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com