You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2018/03/11 09:58:44 UTC
svn commit: r1826432 - in /maven/site/trunk/content:
apt/guides/mini/guide-central-repository-upload.apt
apt/guides/mini/guide-maven-evangelism.apt fml/project-faq.fml site.xml
Author: hboutemy
Date: Sun Mar 11 09:58:44 2018
New Revision: 1826432
URL: http://svn.apache.org/viewvc?rev=1826432&view=rev
Log:
moved every Central menu entry into main "Maven Central Repository" main entry
Modified:
maven/site/trunk/content/apt/guides/mini/guide-central-repository-upload.apt
maven/site/trunk/content/apt/guides/mini/guide-maven-evangelism.apt
maven/site/trunk/content/fml/project-faq.fml
maven/site/trunk/content/site.xml
Modified: maven/site/trunk/content/apt/guides/mini/guide-central-repository-upload.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/guides/mini/guide-central-repository-upload.apt?rev=1826432&r1=1826431&r2=1826432&view=diff
==============================================================================
--- maven/site/trunk/content/apt/guides/mini/guide-central-repository-upload.apt (original)
+++ maven/site/trunk/content/apt/guides/mini/guide-central-repository-upload.apt Sun Mar 11 09:58:44 2018
@@ -32,25 +32,27 @@ Guide to uploading artifacts to the Cent
In order for users of Maven to utilize artifacts produced by your project, you must deploy them to
a remote repository. Many open source projects want to allow users of their projects who build with
Maven to have transparent access to their project's artifacts. In order to allow for this, a project
- must have their artifacts deployed to the Central Repository.
+ must have their artifacts deployed to {{{/repository/}the Central Repository}}.
-{Requirements}
+Requirements
- Only releases can be uploaded to the central repository, that means files that won't change and that only depend on other files
+ Only <releases> can be uploaded to the central repository, that means files that won't change and that only depend on other files
already released and available in the repository.
- There are some requirements for the minimal information in the POMs that are in the central repository.
+ There are some requirements for the minimal information in the POMs that are in the Central repository.
The updated list of requirements can be found {{{http://central.sonatype.org/pages/requirements.html}here}}.
-{Choosing your coordinates}
+Choosing your coordinates
Picking the appropriate coordinates for your project is important. See the guidelines
{{{http://central.sonatype.org/pages/choosing-your-coordinates.html}here}}.
* Explanation
- Some folks have asked why do we require all this information in the POM for deployed artifacts so here's a small explanation. The POM
+ Some folks have asked <"why do we require all this information in the POM for deployed artifacts?">, so here's a small explanation.
+
+ The POM
being deployed with the artifact is part of the process to make transitive dependencies a reality in Maven. The logic for getting
transitive dependencies working is really not that hard, the problem is getting the data. The other applications
that are made possible by having all the POMs available for artifacts are vast, so by placing them into the repository as part of the
@@ -97,7 +99,7 @@ Guide to uploading artifacts to the Cent
</dependencies>
<!--
- NOT ALLOWED: (see FAQ)
+ NOT RECOMMENDED: (see FAQ)
<repositories></repositories>
<pluginRepositories></pluginRepositories>
-->
@@ -140,9 +142,9 @@ Guide to uploading artifacts to the Cent
[]
-{Publishing your artifacts to the Central Repository}
+Publishing your artifacts to the Central Repository
-* {Approved Repository Hosting}
+* Approved Repository Hosting
Instead of maintaining repository rsync feeds for each projects, we now encourage projects to use an approved repository hosting location.
@@ -160,13 +162,13 @@ Guide to uploading artifacts to the Cent
that meet certain minimum criteria such as validation of PGP keys and pom contents as defined above. If you are interested in
becoming an approved Forge, contact us at <<<...@maven.apache.org>>>.
-* {Other Projects}
+* Other Projects
The easiest way to upload another project is to use the
{{{http://central.sonatype.org/pages/ossrh-guide.html}Open Source Software Repository Hosting (OSSRH)}}, which is an approved repository provided
by Sonatype for <any> OSS Project that want to get their artifacts into Central Repository.
-* {Explanations}
+* Explanations
Having each project maintain its own repository with rsync to Central Repository used to be the preferred process until January 2010.
But we are no longer accepting rsync requests on a per project basis.
Modified: maven/site/trunk/content/apt/guides/mini/guide-maven-evangelism.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/guides/mini/guide-maven-evangelism.apt?rev=1826432&r1=1826431&r2=1826432&view=diff
==============================================================================
--- maven/site/trunk/content/apt/guides/mini/guide-maven-evangelism.apt (original)
+++ maven/site/trunk/content/apt/guides/mini/guide-maven-evangelism.apt Sun Mar 11 09:58:44 2018
@@ -26,10 +26,10 @@
~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html
-Guide to add, improve or fix metadata in the Central Maven 2 repository
+Guide to add, improve or fix metadata in the Central Maven repository
- There are artifacts in the repository that don't have POMs. They come from projects with repositories that have
- been synced into central without extra checks (particularly historical ones that were in Maven 1 format). We
+ There are artifacts in the {{{/repository/}Central Maven repository}} that don't have POMs. They come from projects with repositories that have
+ been synced into central without extra checks (particularly historical ones that were in <Maven 1> format). We
know about the problems but can't do anything unless you provide a POM for it or you ask the project in
question to add the POM when they add the artifacts.
@@ -51,4 +51,3 @@ Guide to add, improve or fix metadata in
*Important:* by default assume that we won't trust your info, so you must provide all links
to the project documentation you can to convince us that your solution is right.
-
Modified: maven/site/trunk/content/fml/project-faq.fml
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/fml/project-faq.fml?rev=1826432&r1=1826431&r2=1826432&view=diff
==============================================================================
--- maven/site/trunk/content/fml/project-faq.fml (original)
+++ maven/site/trunk/content/fml/project-faq.fml Sun Mar 11 09:58:44 2018
@@ -38,18 +38,19 @@
</p>
<p>
Whether you want to use Maven or not, users of your project - especially if you provide a framework or
- reusable library - may choose to use Maven. The quality of the metadata in the Maven repository is important
- to your users as they list dependencies on your metadata, and link in the information into their own
+ reusable library - may choose to use <a href="/repository/">Central Maven repository</a>.
+ The quality of the metadata in the Central Maven repository is important
+ to your users, as they list dependencies on your metadata and link in the information into their own
projects.
</p>
<p>
- Maintaining the metadata for your project is not hard - you can submit it to Maven at release time (and
+ Maintaining the metadata for your project is not hard - you can submit it to Central Maven repository at release time (and
for large projects it can be setup automatically), and just need to describe your project, its location,
- version and most importantly dependencies. Not doing so, or providing incomplete or invalid information
+ version and most importantly its dependencies. Not doing so, or providing incomplete or invalid information
leaves this responsibility to the users of your project.
</p>
<p>
- The Maven team does work on this metadata actively to improve its quality, but with thousands of artifacts in
+ The Maven team does <a href="/guides/mini/guide-maven-evangelism.html">work on this metadata actively to improve its quality</a>, but with thousands of artifacts in
the repository and only a certain level of knowledge of other projects this is not ideal. Nobody knows your
project better than you.
</p>
@@ -60,8 +61,8 @@
<answer>
<p>
It is best to get it right at the time of a release to avoid having to make difficult updates later on.
- Your information can be submitted to Maven using the regular
- <a href="/guides/mini/guide-central-repository-upload.html">repository upload procedure</a>.
+ Your information can be submitted to Central Maven repository using the regular
+ <a href="/guides/mini/guide-central-repository-upload.html">Central repository upload procedure</a>.
</p>
<p>
The following information is what is best to provide:
@@ -102,10 +103,10 @@
</answer>
</faq>
<faq id="how-to-automatically-sync">
- <question>How do I ensure my latest releases automatically appear in the Maven repository?</question>
+ <question>How do I ensure my latest releases automatically appear in the Central Maven repository?</question>
<answer>
<p>
- If you able to publish your releases to a Maven2 style repository and make it available over rsync,
+ If you are able to publish your releases to a Maven2 style repository and make it available over rsync,
we can automatically publish them to ibiblio when released. This procedure requires that you take full
responsibility for your metadata, but also ensures the best service for your users. If this is interesting
to your project, contact dev@maven.apache.org.
Modified: maven/site/trunk/content/site.xml
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/site.xml?rev=1826432&r1=1826431&r2=1826432&view=diff
==============================================================================
--- maven/site/trunk/content/site.xml (original)
+++ maven/site/trunk/content/site.xml Sun Mar 11 09:58:44 2018
@@ -89,6 +89,9 @@ under the License.
<item name="Maven API" href="/ref/current/index.html"/>
</item>
<item name="Maven Central Repository" href="/repository/index.html" collapse="true">
+ <item name="Maintaining your Metadata" href="/project-faq.html" />
+ <item name="Guide to Uploading Artifacts" href="/guides/mini/guide-central-repository-upload.html" />
+ <item name="Fixing Metadata" href="/guides/mini/guide-maven-evangelism.html" />
</item>
<item name="Maven Developer Centre" href="/developers/index.html"/>
<item name="Books and Resources" href="/articles.html" />
@@ -99,10 +102,9 @@ under the License.
<item name="Community Overview" href="/community.html" />
<item name="Project Roles" href="/project-roles.html" />
<item name="How to Contribute" href="/guides/development/guide-helping.html" />
- <item name="Maven Repository" href="/guides/mini/guide-maven-evangelism.html" />
<item name="Getting Help" href="/users/getting-help.html" />
<item name="Issue Tracking" href="/issue-tracking.html" />
- <item name="Source Repository" href="/source-repository.html" />
+ <item name="Getting Maven Source" href="/source-repository.html" />
<item name="The Maven Team" href="/team-list.html" />
</menu>
</body>