www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <ja...@planet57.com>
Subject Re: artifactIds and "apache-" prefix for trademark-enabled artifacts
Date Wed, 16 May 2007 08:58:07 GMT
It would be a incredible pity if we had to prefix *every artifact*  
with "apache-".  I believe that wrt to Maven artifacts that the  
"org.apache." groupId prefix should suffice.  Perhaps for  
distribution assemblies if we want to prefix everything with  
"apache-" that should be fine (which it would be nice to get some  
official clarification and documentation on this policy) .

But., for the artifacts themselves... do we really need this?  Apache  
Geroniomo has like 200+ modules and we are already pushing the  
envelope wrt windows paht length limitations with  
"org.apache.geronimo".  In some cases I think we are 10-30 chars away  
from breaching the limit, which does end up biting us from time to  
time.  Anyways, that is our problem, not all of Apache's.

IMO, there is no reason to prefix each and every artifact's filename  
produce by an ASF project with "apache-"... assembly zip/tgz okay,  
maybe... but for other Maven artifacts I belive that the org.apache  
groupId should be sufficient.


On May 14, 2007, at 1:45 AM, Stefano Bagnara wrote:

> Yesterday I was talking to Robert Burrell Donkin on Apache JAMES dev
> list about a work-in-progress release of our mime4j product.
> You can read the whole thread:
> http://mail-archives.apache.org/mod_mbox/james-server-dev/ 
> 200705.mbox/% 
> 3cf470f68e0705130612p6daba5cdve31969c139a8427e@mail.gmail.com%3e
> A summary is that there is an (maybe unwritten) ASF policy  
> requiring us
> to use the "apache-" prefix in every redistributable artifact so to
> enable trademark law to be used against anyone passing off bad  
> packages.
> Browsing the apache m2 repository I found very few products using the
> prefix.
> Of course the short-term solution is to add the "apache-" prefix to  
> all
> of our artifactId but I wanted to spread the word and to hear your
> suggestions on how to make this "policy" more widely adopted by ASF
> products.
> E.g: maybe that an apache m2 plugin could be developed to check  
> that the
> artifactId begins with "apache-" or complain with a text and added to
> the apache root pom? I think that similar technical solutions are much
> more effective than any documentation page :-)
> Stefano

View raw message