svn commit: r1222253 - /incubator/jena/site/trunk/content/jena/download/maven.mdtext

[an...@apache.org]

Author: andy
Date: Thu Dec 22 14:26:29 2011
New Revision: 1222253

URL: http://svn.apache.org/viewvc?rev=1222253&view=rev
Log:
Update for Apache release

Modified:
    incubator/jena/site/trunk/content/jena/download/maven.mdtext

Modified: incubator/jena/site/trunk/content/jena/download/maven.mdtext
URL: http://svn.apache.org/viewvc/incubator/jena/site/trunk/content/jena/download/maven.mdtext?rev=1222253&r1=1222252&r2=1222253&view=diff
==============================================================================
--- incubator/jena/site/trunk/content/jena/download/maven.mdtext (original)
+++ incubator/jena/site/trunk/content/jena/download/maven.mdtext Thu Dec 22 14:26:29 2011
@@ -20,32 +20,9 @@ http://repository.apache.org/content/rep
  * [http://repository.apache.org/content/repositories/releases/](http://repository.apache.org/content/repositories/releases/)
  * [http://repository.apache.org/content/repositories/snapshots/](http://repository.apache.org/content/repositories/snapshots/) for development builds.
 
-Stable Jena releases are automatically indexed by Maven central, so there will
-normally be no need to add any extra repositories to your
-<code>pom.xml</code> or <code>settings.xml</code>.
-
-If you want to depend on Jena development snapshots, e.g. to get access
-to recent bug fixes, you should add the following to your <code>pom.xml</code>:
-
-    <repositories>
-      <repository>
-        <id>apache-repo-releases</id>
-        <url>http://repository.apache.org/content/repositories/releases/</url>
-        <releases>
-         <enabled>true</enabled>
-        </releases>
-      </repository>
-      <repository>
-        <id>apache-repo-snapshots</id>
-        <url>http://repository.apache.org/content/repositories/snapshots/</url>
-        <releases>
-          <enabled>false</enabled>
-        </releases>
-        <snapshots>
-          <enabled>true</enabled>
-        </snapshots>
-      </repository>
-    </repositories>
+Stable Jena releases are automatically mirrored by the central Maven
+repositories, so there will normally be no need to add any extra 
+repositories to your <code>pom.xml</code> or <code>settings.xml</code>.
 
 ### Specifying Jena or ARQ as a dependency
 
@@ -60,6 +37,16 @@ on a version of Jena and ARQ stable rele
 
 You do not need to specify a dependency on Jena, since ARQ depends on Jena and Maven
 will transitively resolve all the dependencies for you (including Jena).
+if you do need to use the Apache release repository, add the follwoong to
+the <code>&lt;repositories</code> section of your <ocde.pom.xml</code>.
+
+   <repository>
+     <id>apache-repo-releases</id>
+     <url>http://repository.apache.org/content/repositories/releases/</url>
+     <releases>
+      <enabled>true</enabled>
+     </releases>
+   </repository>
 
 Please check for the latest version.
 
@@ -108,9 +95,8 @@ this is all you need in your <code>pom.x
 
 ### Specifying dependencies on SNAPSHOTs
 
-Don't forget to include 
-<code>http://repository.apache.org/content/repositories/snapshots/</code>
-in your repositories!
+If you want to depend on Jena development snapshots, e.g. to get access
+to recent bug fixes, you should add the following to your <code>pom.xml</code>:
 
       <repository>
         <id>apache-repo-snapshots</id>
@@ -161,4 +147,10 @@ install them in your local Maven reposit
     cd jena-arq
     mvn clean install
 
-Subversion projects also exist for TDB, Fuseki and others modules, you can browse the subversion repository [here](http://svn.apache.org/repos/asf/incubator/jena/Jena2/).
+    svn co https://svn.apache.org/repos/asf/incubator/jena/Jena2/TDB/trunk jena-tdb
+    cd jena-tdb
+    mvn clean install
+
+
+Subversion projects also exist for Fuseki and others modules, you can browse the
+subversion repository [here](http://svn.apache.org/repos/asf/incubator/jena/Jena2/).