openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1414393 - in /openjpa/site/trunk: WhoIsWorkingOnWhat.txt content/publishing-serp-to-maven-central-repository.mdtext
Date Tue, 27 Nov 2012 20:41:36 GMT
Author: allee8285
Date: Tue Nov 27 20:41:35 2012
New Revision: 1414393

CMS migration updates.


Modified: openjpa/site/trunk/WhoIsWorkingOnWhat.txt
--- openjpa/site/trunk/WhoIsWorkingOnWhat.txt (original)
+++ openjpa/site/trunk/WhoIsWorkingOnWhat.txt Tue Nov 27 20:41:35 2012
@@ -96,7 +96,7 @@ done			opentraderserver.mdtext
 done			performance-guide.mdtext
 done			powered-by.mdtext
 done			privacy-policy.mdtext
-			publishing-serp-to-maven-central-repository.mdtext
+done			publishing-serp-to-maven-central-repository.mdtext
 done			quick-start.mdtext

Modified: openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext
--- openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext (original)
+++ openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext Tue Nov
27 20:41:35 2012
@@ -1,5 +1,6 @@
 Title: Publishing Serp to Maven Central Repository
 <a name="PublishingSerptoMavenCentralRepository-PublishingSerptoMavenCentralRepository"></a>
 # Publishing Serp to Maven Central Repository
 <a name="PublishingSerptoMavenCentralRepository-SerpProject"></a>
 ## Serp Project
@@ -7,24 +8,23 @@ Serp is used by OpenJPA for the bytecode
 maintained as a [SourceForge project](
 .  Serp has been a very solid third-party dependent software project. 
 OpenJPA has had a dependency on Serp v1.13.1 for a long time.  Recently, a
-problem was discovered ([JIRA
-OPENJPA-2240|]) which
+problem was discovered [JIRA OPENJPA-2240](
 required an update to Serp.  Eventually, it was determined that this
 problem was resolved in the 1.14.1 version of Serp.  Unfortunately, the
 last version of Serp that was published to Maven Central was version
 1.13.1.  This page discusses how to get an updated Serp release into the
 Maven Central repository.
-SourceForge Serp:
-Serp homepage:
-Serp sourcecode:
+SourceForge Serp:  <> <br/>
+Serp homepage:	<> <br/>
+Serp sourcecode:  <> <br/>
 <a name="PublishingSerptoMavenCentralRepository-MavenInstructions"></a>
 ## Maven Instructions
 The easiest way to get the updated artifacts for Serp 1.14.1 into Maven
 Central was to follow the instructions on this page: 
  You will need a GPG utility and signature (instructions on that page). 
 You will also need a login for Sonatype's Nexus server (instructions also
 on that page).
@@ -67,15 +67,17 @@ This bundle is what I uploaded to the So
 outlined on that [wiki page](
-{note:title="Not documented.."}
-One process point that was not documented on that [wiki page](
- was the need for a JIRA to be created against the OSSRH project (Open
+<table class="note"><tr>
+  <td valign="top"> <IMG src="images/warning.gif" width="16" height="16" border="0">
+  <td> <B>Not documented..</B><BR>One process point that was not
documented on that
+<a href="">wiki
+was the need for a JIRA to be created against the OSSRH project (Open
 Source Project Repository Hosting).  This JIRA should include the Central
 Repository staging URL that is provided after you upload the bundle. 
-Here's an [example JIRA|]
+Here's an <a href="">example JIRA</a>
  that worked for me.  If all else fails, contact Joel Orlina,
 <a name="PublishingSerptoMavenCentralRepository-SerpCodeUpdates"></a>
 ## Serp Code Updates
@@ -83,7 +85,7 @@ In order to create the -javadoc and -sou
 couple of minor updates to the existing pom file for serp 1.14.1.  I
 committed these changes to HEAD (1.14.2 snapshot) for future reference:
-          <plugin>
+        <plugin>
@@ -92,19 +94,20 @@ committed these changes to HEAD (1.14.2 
-    	 </executions>
-          </plugin>
-          <plugin>
+    	  </executions>
+        </plugin>
+        <plugin>
-    		    <goal>jar</goal>
+    	      <goal>jar</goal>
-    	 </executions>
-          </plugin>
+    	  </executions>
+        </plugin>
 If we continue to require changes to Serp, we may want to do more extensive

View raw message