svn commit: r1543533 - /mahout/site/mahout_cms/trunk/content/developers/thirdparty-dependencies.mdtext

[is...@apache.org]

Author: isabel
Date: Tue Nov 19 19:12:37 2013
New Revision: 1543533

URL: http://svn.apache.org/r1543533
Log:
MAHOUT-1245 - minor formatting changes to page detailing treatment of third party dependencies

Modified:
    mahout/site/mahout_cms/trunk/content/developers/thirdparty-dependencies.mdtext

Modified: mahout/site/mahout_cms/trunk/content/developers/thirdparty-dependencies.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/trunk/content/developers/thirdparty-dependencies.mdtext?rev=1543533&r1=1543532&r2=1543533&view=diff
==============================================================================
--- mahout/site/mahout_cms/trunk/content/developers/thirdparty-dependencies.mdtext (original)
+++ mahout/site/mahout_cms/trunk/content/developers/thirdparty-dependencies.mdtext Tue Nov 19 19:12:37 2013
@@ -1,23 +1,28 @@
 Title: Thirdparty Dependencies
+
+# Adding Thirdparty Dependencies in Maven
+
 If you have a dependency on a third party artifact that is not in Maven,
 you should:
 
-1. Ask the project to add it if at all possible.  Most open source projects
+
+* Ask the project to add it if at all possible.  Most open source projects
 want wider adoption, so this kind of request is often well received.
-1. If they won't add it, we may be able to add it to our Maven repo,
+* If they won't add it, we may be able to add it to our Maven repo,
 assuming it can be published at the ASF at all (no GPL code, for instance).
  Please ask on the mailing list first.
-1. Assuming it can be, then you need to sign and deploy the artifacts, as
+* Assuming it can be, then you need to sign and deploy the artifacts, as
 described below:
-  mvn gpg:sign-and-deploy-file	     
--Durl=https://repository.apache.org/service/local/staging/deploy/maven2 
--DrepositoryId=apache.releases.https -DgroupId=org.apache.mahout.foobar
--DartifactId=foobar -Dversion=x.y -Dpackaging=jar -Dfile=foobar-x.y.jar
-1. Once it is deployed, go into http://repository.apache.org/ (use your SVN
+
+> mvn gpg:sign-and-deploy-file	     
+> -Durl=https://repository.apache.org/service/local/staging/deploy/maven2 
+> -DrepositoryId=apache.releases.https -DgroupId=org.apache.mahout.foobar
+> -DartifactId=foobar -Dversion=x.y -Dpackaging=jar -Dfile=foobar-x.y.jar
+
+* Once it is deployed, go into http://repository.apache.org/ (use your SVN
 credentials to login in)
-1. Select Staging
-1. Find your repository artifacts
-1. Close them (this makes them publicly available, since you are closing the
+* Select Staging
+* Find your repository artifacts
+* Close them (this makes them publicly available, since you are closing the
 staging repo)
-1. Promote them. This adds them to the public Maven repo.
-
+* Promote them. This adds them to the public Maven repo.