You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openjpa.apache.org by al...@apache.org on 2012/11/27 21:41:36 UTC
svn commit: r1414393 - in /openjpa/site/trunk: WhoIsWorkingOnWhat.txt
content/publishing-serp-to-maven-central-repository.mdtext
Author: allee8285
Date: Tue Nov 27 20:41:35 2012
New Revision: 1414393
URL: http://svn.apache.org/viewvc?rev=1414393&view=rev
Log:
CMS migration updates.
Modified:
openjpa/site/trunk/WhoIsWorkingOnWhat.txt
openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext
Modified: openjpa/site/trunk/WhoIsWorkingOnWhat.txt
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/WhoIsWorkingOnWhat.txt?rev=1414393&r1=1414392&r2=1414393&view=diff
==============================================================================
--- 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
query-notes.mdtext
done quick-start.mdtext
recovering-from-a-vetoed-release.mdtext
Modified: openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext?rev=1414393&r1=1414392&r2=1414393&view=diff
==============================================================================
--- 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](http://sourceforge.net/projects/serp)
. 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|http://issues.apache.org/jira/browse/OPENJPA-2240]) which
+problem was discovered [JIRA OPENJPA-2240](http://issues.apache.org/jira/browse/OPENJPA-2240) which
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: https://sourceforge.net/projects/serp/
-Serp homepage: http://serp.sourceforge.net
-Serp sourcecode: http://serp.cvs.sourceforge.net/serp
+SourceForge Serp: <https://sourceforge.net/projects/serp/> <br/>
+Serp homepage: <http://serp.sourceforge.net> <br/>
+Serp sourcecode: <http://serp.cvs.sourceforge.net/serp> <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:
-https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository.
+<https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository>.
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](https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository)
.
-{note:title="Not documented.."}
-One process point that was not documented on that [wiki page](https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository)
- 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="https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository">wiki page</a>
+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|https://issues.sonatype.org/browse/OSSRH-4247]
+Here's an <a href="https://issues.sonatype.org/browse/OSSRH-4247">example JIRA</a>
that worked for me. If all else fails, contact Joel Orlina,
jorlina@sonatype.com.
-{note}
+</tr></table>
<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>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
@@ -92,19 +94,20 @@ committed these changes to HEAD (1.14.2
<goal>jar</goal>
</goals>
</execution>
- </executions>
- </plugin>
- <plugin>
+ </executions>
+ </plugin>
+
+ <plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<executions>
<execution>
<id>attach-javadoc</id>
<goals>
- <goal>jar</goal>
+ <goal>jar</goal>
</goals>
</execution>
- </executions>
- </plugin>
+ </executions>
+ </plugin>
If we continue to require changes to Serp, we may want to do more extensive