Mailing-List: contact commits-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r610625 -
 /maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt
Date: Thu, 10 Jan 2008 01:15:39 -0000
To: commits@maven.apache.org
From: vsiveton@apache.org
Message-Id: <20080110011545.16F791A9897@eris.apache.org>

Author: vsiveton
Date: Wed Jan  9 17:15:11 2008
New Revision: 610625

URL: http://svn.apache.org/viewvc?rev=610625&view=rev
Log:
MNG-2954: Docu incomplete: "Guide to uploading artifacts to the Central Repository": Jira project not specified, Attachment usage unclear

o fixed as suggested

Modified:
    maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt

Modified: maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt?rev=610625&r1=610624&r2=610625&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-central-repository-upload.apt Wed Jan  9 17:15:11 2008
@@ -43,6 +43,7 @@
 
  * dependencies
 
+ []
 
  <<groupId>>: it will identify your project uniquely across all
  projects, so we need to enforce a naming schema. For projects with artifacts already uploaded to the Central Repository it can
@@ -57,7 +58,7 @@
 
  Look at {{{http://java.sun.com/docs/books/jls/third_edition/html/packages.html#7.7}
  More information about package names}}. Check also the guide about
- {{{guide-naming-conventions.html}Maven naming conventions}}
+ {{{guide-naming-conventions.html}Maven naming conventions}}.
 
  Examples:
 
@@ -65,6 +66,7 @@
 
  * oness.sf.net -> net.sf.oness
 
+ []
 
 * Explanation
 
@@ -78,8 +80,6 @@
  its life time and we are trying create tools to help normal people sort out licensing issues. For example, knowing all the licenses
  for a particular graph of artifacts we could have some strategies that would identify potential licensing problems.
 
-
-
 * A basic sample:
 
 +----+
@@ -116,7 +116,7 @@
   <repositories></repositories>
   <pluginRepositories></pluginRepositories>
   -->
-</project> 
+</project>
 
 +----+
 
@@ -141,7 +141,7 @@
 
  If your project name is <<<foo>>> at SourceForge, then <<<net.sf.foo>>>. If it's foo at dev.java.net, then <<<net.java.dev.foo>>>
 
-
+ []
 
 Sync'ing your own repository to the central repository automatically
 
@@ -155,7 +155,7 @@
  {{{http://svn.apache.org/viewvc/maven/archiva/tools/trunk/maven-meeper/src/bin/synchronize/m2-sync/conf/}current scripts}},
  open an issue under {{{http://jira.codehaus.org/browse/MAVENUPLOAD}MAVENUPLOAD}} and attach the script, and we'll add it to the automatically synced repos.
 
- Make sure you <<provide proof of owning the domain>> that matches the groupId (see groupId considerations above). Proof means either the server to sync from has a name 
+ Make sure you <<provide proof of owning the domain>> that matches the groupId (see groupId considerations above). Proof means either the server to sync from has a name
  under that domain, your name shows up in a prominent place in the domain, or you provide a link to a whois database where your name shows up as the domain owner.
 
  If you are using ssh in your own server you need to add the {{{http://www.ibiblio.org/maven/id_dsa.pub}maven public key}} to the authorized ones to allow us to log
@@ -175,7 +175,7 @@
  issue first describing what and why you are trying to do it, and you may be designated the "unofficial" mantainer of the repository section associated to that project,
  and you will be responsible of publishing the new releases for that project in your repository if other users request it. You can opt out at any time.
 
-
+ []
 
 Manual upload of artifacts
 
@@ -186,7 +186,6 @@
  It means that for each version you release and want to upload to the central repository you will have to wait that time. If a problem is detected it will
  be notified in the Jira issue and <<you will wait again>> until the next time the issues are processed.
 
-
 * Step 1: Create an upload bundle
 
  Use the repository plugin provided with the standard Maven distribution to create an upload bundle:
@@ -199,7 +198,7 @@
 
  The bundle will be created in your <<<target>>> directory with the name:
  <<<${pom.artifactId}-${pom.currentVersion}-bundle.jar>>>
- 
+
  If you want to include a jar with java sources in your upload (recommended, unless your license doesn't
  allow sources to be redistributed) the command to run is:
 
@@ -236,14 +235,15 @@
 * Step 2: Posting the request
 
  Post your request to {{{http://jira.codehaus.org/secure/CreateIssue.jspa?pid=10367&amp;issuetype=3}JIRA}}.
- In the description you must write the URL of the upload bundle
+ Under this URL, you need to choose that the project is "maven-upload-requests" and issue type is "wish".
+ In the description, you must write the URL of the upload bundle
  (if you're uploading more than one bundle please add all the urls under the same issue),
  then leave a blank line and provide the following:
 
  * a url where the project can be found.
 
  * if you are one of its developers, a url where your name or email can be found inside the project site.
- 
+
  []
 
  This will speed up the uploading process.
@@ -276,8 +276,6 @@
 
 +----+
 
-
-
 Manual process FAQ and common mistakes
 
  * I use parent poms how do I include them in the bundle?
@@ -288,7 +286,7 @@
 
  No, please ignore the bundle url field and put in only one Jira issue the URLs of all bundles in the description or comments fields.
 
-
+ []
 
 Maven partners
 
@@ -304,6 +302,7 @@
 
  * {{{http://www.opensymphony.com/}OpenSymphony}}
 
+ []
 
 For Maven developers
 
@@ -346,3 +345,4 @@
 
   * upload requests for popular projects require being extremely careful (javax.* groups, spring, hibernate,...)
 
+  []