Author: carlos
Date: Mon Nov 7 14:18:59 2005
New Revision: 331623
URL: http://svn.apache.org/viewcvs?rev=331623&view=rev
Log:
Added more groupId explanations
Modified:
maven/site/trunk/src/site/apt/guides/mini/guide-ibiblio-upload.apt
Modified: maven/site/trunk/src/site/apt/guides/mini/guide-ibiblio-upload.apt
URL:
http://svn.apache.org/viewcvs/maven/site/trunk/src/site/apt/guides/mini/guide-ibiblio-upload.apt?rev=331623&r1=331622&r2=331623&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-ibiblio-upload.apt
(original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-ibiblio-upload.apt Mon Nov
7 14:18:59 2005
@@ -96,7 +96,12 @@
projects, so we need to enforce a naming schema. For projects with artifacts
already uploaded to ibiblio it can
be equal to the previous used, but for new projects it has to follow the
package name rules, what
means that has to be at least as a domain name you control, and you can
create as many subgroups
- as you want. Look at
{{{http://java.sun.com/docs/books/jls/third_edition/html/packages.html#7.7}
+ as you want.
+ There are a lot of poorly defined package names so you have to provide proof
that you control the domain that
+ matches the package name. Provide proof means that the project is hosted at
that domain or they own it although
+ not using it. eg. If you use a com.sun.xyz package name we expect that the
project is hosted at http://xyz.sun.com.
+
+ Look at
{{{http://java.sun.com/docs/books/jls/third_edition/html/packages.html#7.7}
More information about package names}}. Check also the guide about
{{{guide-naming-conventions.html}Maven naming conventions}}
