Author: brett
Date: Thu Oct 23 03:34:24 2008
New Revision: 707339

URL: http://svn.apache.org/viewvc?rev=707339&view=rev
Log:
note conventions

Modified:
    
incubator/nmaven/trunk/site/versioned/src/site/apt/user-guide/dependencies.apt

Modified: 
incubator/nmaven/trunk/site/versioned/src/site/apt/user-guide/dependencies.apt
URL: 
http://svn.apache.org/viewvc/incubator/nmaven/trunk/site/versioned/src/site/apt/user-guide/dependencies.apt?rev=707339&r1=707338&r2=707339&view=diff
==============================================================================
--- 
incubator/nmaven/trunk/site/versioned/src/site/apt/user-guide/dependencies.apt 
(original)
+++ 
incubator/nmaven/trunk/site/versioned/src/site/apt/user-guide/dependencies.apt 
Thu Oct 23 03:34:24 2008
@@ -36,4 +36,13 @@
 </dependency>
 ----
 
- 
\ No newline at end of file
+* Artifact Conventions
+
+The agreed upon conventions for NMaven artifacts are as follows:
+
+  * standard Maven notation for group IDs, ie <<<org.nunit>>>, 
<<<org.apache.maven.dotnet>>>
+
+  * CamelCase notation for artifact IDs, ie <<<NUnit.Framework>>>, 
<<<System.DirectoryServices>>>
+ 
+For artifacts that need a different name on the filesystem, the 
<<<finalName>>> element of the POM can be used to override the artifact ID, eg 
for<<<nunit.framework>>>.
+This is often needed for files where the version is not to be included in the 
file name when the assembly is reused.


Reply via email to