You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by de...@apache.org on 2008/06/17 13:34:05 UTC
svn commit: r668619 -
/maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt
Author: dennisl
Date: Tue Jun 17 04:34:04 2008
New Revision: 668619
URL: http://svn.apache.org/viewvc?rev=668619&view=rev
Log:
o Minor changes to format and wording.
Modified:
maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt
Modified: maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt?rev=668619&r1=668618&r2=668619&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt Tue Jun 17 04:34:04 2008
@@ -10,21 +10,21 @@
[]
- * <<groupId>> it will identify your project uniquely in internet
+ * <<groupId>> will identify your project uniquely across all projects,
so we need to enforce a naming schema. 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}
More information about package names}}.
- eg. <<<org.apache.maven>>>, <<<org.apache.jakarta.commons>>>
+ eg. <<<org.apache.maven>>>, <<<org.apache.commons>>>
- * A good way to determine the granularity of the group ID is to use the project structure. That is, if
+ A good way to determine the granularity of the <<<groupId>>> is to use the project structure. That is, if
the current project is a multiple module project, it should append a new identifier to the parent's
- group ID.
+ <<<groupId>>>.
eg. <<<org.apache.maven>>>, <<<org.apache.maven.plugins>>>, <<<org.apache.maven.reporting>>>
- * <<artifactId>> the name of the jar without version. If you created it then you can choose
+ * <<artifactId>> is the name of the jar without version. If you created it then you can choose
whatever name you want with lowercase letters and no strange symbols. If it's a third party jar
you have to take the name of the jar as it's distributed.
@@ -32,7 +32,7 @@
* <<version>> if you distribute it then you can choose any typical version with numbers and dots
(1.0, 1.1, 1.0.1, ...).
- Don't use dates as they are usually associated with snapshot (nightly) builds. If it's a third
- party artifact, you have to use their version number whatever it is, and as strange it can look.
+ Don't use dates as they are usually associated with SNAPSHOT (nightly) builds. If it's a third
+ party artifact, you have to use their version number whatever it is, and as strange as it can look.
eg. <<<2.0>>>, <<<2.0.1>>>, <<<1.3.1>>>