You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2023/02/08 20:32:15 UTC
svn commit: r1907529 [19/22] - in /maven/website/content: ./ apache-resource-bundles/ archives/maven-2.x/ background/ developers/ developers/conventions/ developers/release/ developers/website/ docs/ docs/2.0.1/ docs/2.0.10/ docs/2.0.11/ docs/2.0.2/ do...
Modified: maven/website/content/project-roles.html
==============================================================================
--- maven/website/content/project-roles.html (original)
+++ maven/website/content/project-roles.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/project-roles.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/project-roles.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Apache Maven Project Roles</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
@@ -122,7 +122,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Apache_Maven_Project_Roles"></a>Apache Maven Project Roles</h1><!--
+<h1>Apache Maven Project Roles</h1><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -142,7 +142,7 @@ under the License.
-->
<p>The Apache Maven project is not just the software it produces.
-The Apache Foundation has a phrase: Community over code which
+The Apache Foundation has a phrase: “Community over code” which
is about how it is the community that grows around a project
that is the most important thing.</p>
<p>Everyone reading this is part of the Apache Maven community,
@@ -157,8 +157,8 @@ with others in the community.</p>
<p><em>Note:</em> the right to disagree with other people's opinions
comes with the responsibility not to deliberately cause offence
or discord.</p><section>
-<h2><a name="Informal_roles"></a>Informal roles</h2><section>
-<h3><a name="Lurkers"></a>Lurkers</h3>
+<h2>Informal roles</h2><section>
+<h3>Lurkers</h3>
<p>People who do not use Maven at all, but have an interest in
the project. This can include people who are developing
competing software tools to Apache Maven.</p>
@@ -171,7 +171,7 @@ we will welcome you with open armsȂ
with open arms, please advise the <a href="mailto:private@maven.apache.org" class="externalLink">Project management committee</a>
who are responsible for ensuring that the community is a healthy
one)</p></section><section>
-<h3><a name="Consumers"></a>Consumers</h3>
+<h3>Consumers</h3>
<p>People who use Maven, but do not actively join the community.
This does not include people who are: subscribed to one of the
Maven mailing lists; active in a Maven user community (e.g.
@@ -198,7 +198,7 @@ mind that Apache Foundation projects are
the community at the ASF, so you will get more eyes and a
quicker response if you engage directly with the ASF hosted
community.</p></section><section>
-<h3><a name="Users"></a>Users</h3>
+<h3>Users</h3>
<p>People who use Maven and have joined the community. This includes people who have:</p>
<ul>
@@ -218,7 +218,7 @@ have an answer. Pay it forward!</p>
<p>We hope your experience in one of the other Maven user
communities is a positive one, so why not join the canonical
Maven user community and subscribe to the <a href="mailto:users@maven.apache.org" class="externalLink">Maven user list</a>?</p></section><section>
-<h3><a name="Contributors"></a>Contributors</h3>
+<h3>Contributors</h3>
<p>People who use Maven, have joined the Maven community and contribute
back to the community. This includes people who:</p>
<ul>
@@ -234,8 +234,8 @@ related issues.</li>
<p>Keep up the contributions, you are a critical member of our
community. If we like what we see, we may even ask you to
consider taking a formal role in our project.</p></section></section><section>
-<h2><a name="Formal_roles"></a>Formal roles</h2><section>
-<h3><a name="Committers"></a><a href="https://www.apache.org/foundation/how-it-works.html#committers" class="externalLink">Committers</a></h3>
+<h2>Formal roles</h2><section>
+<h3><a href="https://www.apache.org/foundation/how-it-works.html#committers" class="externalLink">Committers</a></h3>
<p>These are those people who have been given write access to the
Apache Maven code repository and have a signed
<a href="https://www.apache.org/licenses/#clas" class="externalLink">Contributor License Agreement (CLA)</a> on file with the ASF.</p>
@@ -247,7 +247,7 @@ commit is covered by a valid CLA.</p>
ways to demonstrate the responsibilities listed in the PMC Members
section in order to make it easier for PMC members to decide
that the committer is ready for the responsibility.</p></section><section>
-<h3><a name="Emeritus_committers"></a>Emeritus committers</h3>
+<h3>Emeritus committers</h3>
<p>If a committer decides that they cannot currently continue with
the responsibilities of a committer, they may elect to go
emeritus.</p>
@@ -255,7 +255,7 @@ emeritus.</p>
may decide that they want to become an active committer again
by informing the <a href="mailto:private@maven.apache.org" class="externalLink">project management committee</a>. The current
policy is that committer role reinstatement is automatic.</p></section><section>
-<h3><a name="Project_Management_Committee"></a><a href="https://www.apache.org/foundation/how-it-works.html#pmc-members" class="externalLink">Project Management Committee</a></h3>
+<h3><a href="https://www.apache.org/foundation/how-it-works.html#pmc-members" class="externalLink">Project Management Committee</a></h3>
<p>The Project Management Committee as a whole is the entity that
controls the project. Membership of the Project Management Committee
is decided by the board of the Apache Software Foundation, based on
@@ -305,11 +305,11 @@ are covered by a compatible license.</li
<li>Knows and respects the goals and processes of the community and helps educate
newer members about them.</li>
</ul><section>
-<h4><a name="Standards_for_Community_Commitment"></a>Standards for Community Commitment</h4>
+<h4>Standards for Community Commitment</h4>
<p>In the spirit of supporting the health of our community, Project
Management Committee members refrain from actions that subvert the
functioning of the committee itself.</p></section><section>
-<h4><a name="Promotion_of_other_projects"></a>Promotion of other projects</h4>
+<h4>Promotion of other projects</h4>
<p>The Apache Foundation currently does not have a policy requiring projects to
cross-promote. For example Subversion is an Apache project, yet projects
are free to choose from Subversion and Git (a non-Apache project) for source
@@ -332,7 +332,7 @@ project hosted elsewhere.</p>
<p>PMC members with a stated interest / involvement should try to abstain from
making binding votes in either direction with respect to the relevant
technology choices.</p></section><section>
-<h4><a name="Forks_of_the_project_codebase"></a>Forks of the project codebase</h4>
+<h4>Forks of the project codebase</h4>
<p>All code that gets released by the community should have sufficient opportunity
for review both:</p>
<ul>
@@ -374,7 +374,7 @@ of the PMC and committers such that when
bring the changes in their fork back to the Apache Maven project their
contribution may end up being rejected on the basis of the review of a
large set of changes being too difficult/time-consuming.</p></section></section><section>
-<h3><a name="Project_Management_Chair"></a><a href="https://www.apache.org/foundation/how-it-works.html#pmc-chair" class="externalLink">Project Management Chair</a></h3>
+<h3><a href="https://www.apache.org/foundation/how-it-works.html#pmc-chair" class="externalLink">Project Management Chair</a></h3>
<p>For various legal reasons, there are certain things that the Apache
Software Foundation can only delegate to an officer of the foundation.</p>
<p>The Project Management Committee is responsible for nominating
Modified: maven/website/content/reference/maven-classloading.html
==============================================================================
--- maven/website/content/reference/maven-classloading.html (original)
+++ maven/website/content/reference/maven-classloading.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/reference/maven-classloading.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/reference/maven-classloading.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Maven classloading</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
@@ -122,7 +122,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Maven_classloading"></a>Maven classloading</h1><!--
+<h1>Maven classloading</h1><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -142,13 +142,13 @@ under the License.
-->
<p><img src="maven-classloading.png" alt="" /></p><section>
-<h2><a name="ClassWorlds_bootstrap_classloader"></a>ClassWorlds bootstrap classloader</h2>
+<h2>ClassWorlds bootstrap classloader</h2>
<p>This classloader is created and managed by the calling environment: JVM launcher, integration testing harness, etc.</p>
<p>During normal command line Maven invocation this is the JVM System classloader and contains classes from <code>${maven.home}/boot/plexus-classworlds-*.jar</code> and classes from <code>-javaagent</code>.</p></section><section>
-<h2><a name="Maven_Core_classloader"></a>Maven Core classloader</h2>
-<p>This classloader contains core Maven runtime classes like MavenProject, AsbtractMojo and so on. This is the classloader set as the container realm in the Plexus container instance unless Maven Extensions classloader is created (see below).</p>
+<h2>Maven Core classloader</h2>
+<p>This classloader contains core Maven runtime classes like MavenProject, AsbtractMojo and so on. This is the classloader set as the “container realm” in the Plexus container instance unless Maven Extensions classloader is created (see below).</p>
<p>Contents of this classloader are configured in <code>${maven.home}/bin/m2.conf</code> and typically contains <code>${maven.home}/lib/ext/*.jar</code> and <code>${maven.home}/lib/*.jar</code>.</p></section><section>
-<h2><a name="Maven_Core_Extensions_classloaders"></a>Maven Core Extensions classloaders</h2>
+<h2>Maven Core Extensions classloaders</h2>
<p>Core Extensions is a new mechanism introduced in Maven 3.3.0 which allows additional components to be loaded into Maven Core as part of a build session.</p>
<p>Each core extension is loaded in a separate classloader and there is no mechanism to share classes among core extensions. Core extensions classloaders use Maven Core classloader as the parent and have access to both exported and internal Maven Core classes.</p>
<p>Core extension can use <code>META-INF/maven/extension.xml</code> descriptor to declare packages and artifacts exported by the extension. If the descriptor is not present, no packages or artifacts are exported, but the extension can still contribute components to Maven Core extension points.</p>
@@ -166,27 +166,27 @@ under the License.
</extensions>
</code></pre></div>
<p>Core extensions are loaded as part of Maven runtime startup and disposed of as part of Maven runtime shutdown.</p></section><section>
-<h2><a name="Maven_extensions_classloader"></a>Maven extensions classloader</h2>
+<h2>Maven extensions classloader</h2>
<p>Maven extensions classloader aggregates packages exported by core extensions realms. It also loads additional classpath entries specified in <code>-Dmaven.ext.class.path</code> command line parameter.</p>
-<p>Maven extensions classloader is created only when core extensions are configured for the build. If created, it will be set as container realm in the Plexus container.</p></section><section>
-<h2><a name="Maven_API_classloader"></a>Maven API classloader</h2>
+<p>Maven extensions classloader is created only when core extensions are configured for the build. If created, it will be set as “container realm” in the Plexus container.</p></section><section>
+<h2>Maven API classloader</h2>
<p>Maven API classloader aggregates exported packages from Maven Core and Maven Core Extensions classloaders. Maven API classloader does not include any classes directly.</p>
<p>Maven API uses approximate JVM Bootstrap classloader as its parent. (there is no API to access JVM Bootstrap classloader, implementation uses <code>ClassLoader.getSystemClassLoader().getParent()</code>). The parent classloader does not contain any application or javaagent classes, which allows for consistent Maven API classpath regardless how Maven JVM was launched.</p></section><section>
-<h2><a name="Build_Extension_classloaders"></a>Build Extension classloaders</h2>
+<h2>Build Extension classloaders</h2>
<p>Modern Maven 3.x build extensions are build extensions that either consist of multiple artifacts or have <code>META-INF/maven/extension.xml</code>. Each modern build extension is loaded in a a fully isolated classloader, i.e. it is not possible to share classes or inject components among extensions.</p>
<p>Maven guarantees that each distinct modern build extension (as identified by plugin groupId, artifactId, version and set of dependecies) is loaded by one and only one extensions classloader and the classloader is wired to all projects that use the extension.</p>
<p>Build extension classloaders use ClassWorld bootstrap classloader as the parent, which allows build extensions access to <code>-javaagent</code> classes.</p></section><section>
-<h2><a name="Project_classloaders"></a>Project classloaders</h2>
+<h2>Project classloaders</h2>
<p>Project classloader aggregates Maven API packages, packages exported by project build extensions.</p>
<p>Project classloaders use Maven API classloader as the parent and import exported classes from project build extension realms. Legacy Maven 2.x build extensions, i.e. extensions that consist of single artifact which does not include <code>META-INF/maven/extension.xml</code> descriptor, are directly in project classloaders.</p>
<p>Maven guarantees there will be one and only one project classloader for each unique set of project build extensions and the same classloader will be used by all projects that have the set of build extensions.</p></section><section>
-<h2><a name="Plugin_classloaders"></a>Plugin classloaders</h2>
+<h2>Plugin classloaders</h2>
<p>Plugin classloaders are wired differently for projects with and without build extensions.</p>
<p>For projects without build extensions, single classloader is created for each plugin identified by groupId:artifactId:version and the classloader imports API packages from Maven API classloader. Maven will create one and only one classloader for each unique plugin+dependency combination.</p>
<p>For projects that use build extensions, plugin classloaders are wired to project classloaders. This gives plugin code access to both Maven API packages and packages exported by the project build extensions. Maven will create one and only one classlaoder for each unique plugin+dependencies+build-extensions combination.</p>
<p>All plugin classloaders use ClassWorlds bootstrap classloader as the parent. This provides relatively clean and therefore consistent plugin classpath, while still allowing plugins access to <code>-javaagent</code> classes (see <a href="https://issues.apache.org/jira/browse/MNG-4747" class="externalLink">MNG-4747</a>).</p>
<p>Reporting plugins are wired differently still, but reporting plugins are a special case and are outside of the scope of this document.</p></section><section>
-<h2><a name="Exported_artifacts_and_packages"></a>Exported artifacts and packages</h2>
+<h2>Exported artifacts and packages</h2>
<p>Maven Core, Session and Build Extensions use <code>META-INF/maven/extension.xml</code> descriptor to declare API packages and artifacts exported by the classloader.</p>
<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><?xml version="1.0" encoding="UTF-8"?>
Modified: maven/website/content/release-notes-all.html
==============================================================================
--- maven/website/content/release-notes-all.html (original)
+++ maven/website/content/release-notes-all.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/release-notes-all.md.vm at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/release-notes-all.md.vm at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Release Notes</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
@@ -122,7 +122,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Release_Notes"></a>Release Notes</h1><!--
+<h1>Release Notes</h1><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
Modified: maven/website/content/repositories/artifacts.html
==============================================================================
--- maven/website/content/repositories/artifacts.html (original)
+++ maven/website/content/repositories/artifacts.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/repositories/artifacts.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/artifacts.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Maven Artifacts</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
@@ -130,7 +130,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Maven_Artifacts"></a>Maven Artifacts</h1><!--
+<h1>Maven Artifacts</h1><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -149,217 +149,217 @@ specific language governing permissions
under the License.
-->
-<p>An Artifact is anything (any file) that can be addressed using its coordinates, and Maven downloads, installs or
+<p>An Artifact is “anything” (any file) that can be addressed using its coordinates, and Maven downloads, installs or
deploys for you. Most of them are POMs and JARs but
an artifact can be really anything. A very important thing about artifacts is that they have coordinates,
-so they are not just files, but they are files that are in some way addressable by Maven.</p>
+so they are not “just files”, but they are files that are in some way addressable by Maven.</p>
<p>Artifact coordinates, are most often represented as <code>groupId:artifactId:version</code>, or GAV in short or when
informally used (please note that Artifact coordinates has more fields, but for brevity we still call the
-coordinates GAV, not GAVCE). The artifact coordinates uniquely describe the artifact you are referring to,
+coordinates “GAV”, not “GAVCE”). The artifact coordinates uniquely describe the artifact you are referring to,
but does not tell anything about its source (or origin). It is up to Maven to figure out (or you to tell Maven
how to figure it out).</p>
<p>A word about uniqueness: as stated above, GAV coordinates uniquely identifies artifact, but only <strong>within one repository</strong>.
It is clearly possible (but discouraged) to have multiple repositories with overlapping content (so R1 and R2 both
contain artifact with same GAV). If those files are not-identical (truly, ie. hash wise), it may cause severe
issues without you noticing it. In short, these cases should be avoided.</p>
-<p>While Maven internally uses the notion of artifact thoroughly (just look at sources!), end users may never hit this term.
-That's due the fact, that while for Maven, everything is artifact (internally), Maven end users actually speak about
-projects, parent projects, dependencies, build plugins, reporting plugins, build extensions and so on.</p><section>
-<h2><a name="Artifact_Properties"></a>Artifact Properties</h2>
+<p>While Maven internally uses the notion of “artifact” thoroughly (just look at sources!), end users may never hit this term.
+That's due the fact, that while for Maven, “everything is artifact” (internally), Maven end users actually speak about
+“projects”, “parent projects”, “dependencies”, “build plugins”, “reporting plugins”, “build extensions” and so on.</p><section>
+<h2>Artifact Properties</h2>
<p>The artifacts that Maven (internally) uses has following (for our topic related) properties:</p>
-<table border="0" class="table table-striped">
+<table class="table table-striped">
<thead>
<tr class="a">
<th>Name</th>
<th>Description</th></tr></thead><tbody>
<tr class="b">
-<td align="left">groupId</td>
+<td>groupId</td>
<td>The artifact group</td></tr>
<tr class="a">
-<td align="left">artifactId</td>
+<td>artifactId</td>
<td>The artifact id</td></tr>
<tr class="b">
-<td align="left">version</td>
+<td>version</td>
<td>The artifact version (linked w/ baseVersion)</td></tr>
<tr class="a">
-<td align="left">baseVersion</td>
+<td>baseVersion</td>
<td>The artifact base version (linked w/ version)</td></tr>
<tr class="b">
-<td align="left">classifier</td>
+<td>classifier</td>
<td>The artifact distinguishing classifier (optional)</td></tr>
<tr class="a">
-<td align="left">extension</td>
-<td>The artifact extension (default: jar)</td></tr></tbody>
+<td>extension</td>
+<td>The artifact extension (default: “jar”)</td></tr></tbody>
</table>
<p>One property worth explaining is a bit of special one: <code>baseVersion</code> that is actually derived/linked to
<code>version</code> (or the other way around, depending on the context): for release artifacts, it holds the same value as
-<code>version</code>, whereas for snapshot artifacts, it holds the non-timestamped snapshot version. For example,
-for snapshot version 1.0-20220119.164608-1, the <code>baseVersion</code> would have the value 1.0-SNAPSHOT.
+<code>version</code>, whereas for snapshot artifacts, it holds the “non-timestamped snapshot version”. For example,
+for snapshot version “1.0-20220119.164608-1”, the <code>baseVersion</code> would have the value “1.0-SNAPSHOT”.
So, <code>version</code> and <code>baseVersion</code> are linked, derived from each other, but <strong>they have different values only in
case of snapshots</strong>.</p>
<p>Important note about Artifacts: the fact is an artifact a snapshot or not, should be queried with method
<code>Artifact#isSnapshot()</code>.</p></section><section>
-<h2><a name="But_where_do_I_set_Artifact_extension.3F"></a>But where do I set Artifact extension?</h2>
-<p>In short, nowhere. Or maybe you rarely have to. Maven POM (where you declare your project, parent project,
+<h2>But where do I set Artifact extension?</h2>
+<p>In short, nowhere. Or maybe “you rarely have to”. Maven POM (where you declare your project, parent project,
dependencies, plugins and other), maps those elements onto artifact coordinates with some extra logic.</p>
-<p>In case of project and parent project aka POMs (after POM made into effective POM, ie. parent values inherited):</p>
-<table border="0" class="table table-striped">
+<p>In case of “project” and “parent project” aka POMs (after POM made into effective POM, ie. parent values inherited):</p>
+<table class="table table-striped">
<thead>
<tr class="a">
<th>Artifact Property</th>
<th>Project POM (pom.xml)</th>
<th>POM Artifact</th></tr></thead><tbody>
<tr class="b">
-<td align="left">groupId</td>
+<td>groupId</td>
<td><code>project/groupId</code></td>
<td>-> groupId</td></tr>
<tr class="a">
-<td align="left">artifactId</td>
+<td>artifactId</td>
<td><code>project/artifactId</code></td>
<td>-> artifactId</td></tr>
<tr class="b">
-<td align="left">version</td>
+<td>version</td>
<td><code>project/version</code></td>
<td>-> version</td></tr>
<tr class="a">
-<td align="left">classifier</td>
+<td>classifier</td>
<td>-</td>
<td>"" (always)</td></tr>
<tr class="b">
-<td align="left">extension</td>
+<td>extension</td>
<td>-</td>
<td><code>pom</code> (always)</td></tr></tbody>
</table>
-<p>In case of build plugins and build extensions, as they are JARs, this is how corresponding elements are mapped
+<p>In case of “build plugins” and “build extensions”, as they are JARs, this is how corresponding elements are mapped
(for build extension change the XML path prefix to <code>project/build/extensions/extension[x]</code>):</p>
-<table border="0" class="table table-striped">
+<table class="table table-striped">
<thead>
<tr class="a">
<th>Artifact Property</th>
<th>Plugin in Project POM</th>
<th>Plugin/Extension Artifact</th></tr></thead><tbody>
<tr class="b">
-<td align="left">groupId</td>
+<td>groupId</td>
<td><code>project/build/plugins/plugin[x]/groupId</code></td>
<td>-> groupId</td></tr>
<tr class="a">
-<td align="left">artifactId</td>
+<td>artifactId</td>
<td><code>project/build/plugins/plugin[x]/artifactId</code></td>
<td>-> artifactId</td></tr>
<tr class="b">
-<td align="left">version</td>
+<td>version</td>
<td><code>project/build/plugins/plugin[x]/version</code></td>
<td>-> version</td></tr>
<tr class="a">
-<td align="left">classifier</td>
+<td>classifier</td>
<td>-</td>
<td>-> "" (always)</td></tr>
<tr class="b">
-<td align="left">extension</td>
+<td>extension</td>
<td>-</td>
<td>-> <code>jar</code> (always)</td></tr></tbody>
</table>
-<p>And finally, in case of dependencies, this is the mapping (no, scope is NOT part of artifact coordinates):</p>
-<table border="0" class="table table-striped">
+<p>And finally, in case of “dependencies”, this is the mapping (no, scope is NOT part of artifact coordinates):</p>
+<table class="table table-striped">
<thead>
<tr class="a">
<th>Artifact Property</th>
<th>Dependency in Project POM</th>
<th>Dependency Artifact</th></tr></thead><tbody>
<tr class="b">
-<td align="left">groupId</td>
+<td>groupId</td>
<td><code>project/dependencies/dependency[x]/groupId</code></td>
<td>-> groupId</td></tr>
<tr class="a">
-<td align="left">artifactId</td>
+<td>artifactId</td>
<td><code>project/dependencies/dependency[x]/artifactId</code></td>
<td>-> artifactId</td></tr>
<tr class="b">
-<td align="left">version</td>
+<td>version</td>
<td><code>project/dependencies/dependency[x]/version</code></td>
<td>-> version</td></tr>
<tr class="a">
-<td align="left">classifier</td>
+<td>classifier</td>
<td><code>project/dependencies/dependency[x]/classifier</code></td>
<td>-> classifier</td></tr>
<tr class="b">
-<td align="left">extension</td>
+<td>extension</td>
<td><code>project/dependencies/dependency[x]/type</code></td>
<td>-> type handler provided, or same as type</td></tr></tbody>
</table>
-<p>Here, we need to make a short detour to explain type (of a dependency) and how it becomes artifact extension.</p>
-<p>Maven for dependencies defines type, that describes what that dependency is (should it be added to classpath and
+<p>Here, we need to make a short detour to explain “type” (of a dependency) and how it becomes artifact extension.</p>
+<p>Maven for dependencies defines “type”, that describes what that dependency is (should it be added to classpath and
many other things). Plugins and extensions may define new types, that is usually a must for plugins introducing
-a packaging (lifecycle mapping) by providing <code>ArtifactHandler</code> components with name corresponding to type name.</p>
-<p>Maven Core out of the box <a href="/ref/current/maven-core/artifact-handlers.html">defines following types (handled by same named <code>ArtifactHandler</code> components)</a>:</p>
-<table border="0" class="table table-striped">
+a “packaging” (lifecycle mapping) by providing <code>ArtifactHandler</code> components with name corresponding to type name.</p>
+<p>Maven Core out of the box <a href="/ref/current/maven-core/artifact-handlers.html">defines following “types” (handled by same named <code>ArtifactHandler</code> components)</a>:</p>
+<table class="table table-striped">
<thead>
<tr class="a">
<th>Type Name</th>
<th>Extension</th>
<th>Classifier</th></tr></thead><tbody>
<tr class="b">
-<td align="left">pom</td>
+<td>pom</td>
<td><code>pom</code></td>
<td> </td></tr>
<tr class="a">
-<td align="left">jar</td>
+<td>jar</td>
<td><code>jar</code></td>
<td> </td></tr>
<tr class="b">
-<td align="left">maven-plugin</td>
+<td>maven-plugin</td>
<td><code>jar</code></td>
<td> </td></tr>
<tr class="a">
-<td align="left">ear</td>
+<td>ear</td>
<td><code>ear</code></td>
<td> </td></tr>
<tr class="b">
-<td align="left">ejb</td>
+<td>ejb</td>
<td><code>jar</code></td>
<td> </td></tr>
<tr class="a">
-<td align="left">ejb-client</td>
+<td>ejb-client</td>
<td><code>jar</code></td>
<td><code>ejb-client</code></td></tr>
<tr class="b">
-<td align="left">javadoc</td>
+<td>javadoc</td>
<td><code>jar</code></td>
<td><code>javadoc</code></td></tr>
<tr class="a">
-<td align="left">java-source</td>
+<td>java-source</td>
<td><code>jar</code></td>
<td><code>sources</code></td></tr>
<tr class="b">
-<td align="left">rar</td>
+<td>rar</td>
<td><code>rar</code></td>
<td> </td></tr>
<tr class="a">
-<td align="left">test-jar</td>
+<td>test-jar</td>
<td><code>jar</code></td>
<td><code>tests</code></td></tr>
<tr class="b">
-<td align="left">war</td>
+<td>war</td>
<td><code>war</code></td>
<td> </td></tr>
<tr class="a">
-<td align="left"><strong>any</strong></td>
+<td><strong>any</strong></td>
<td>any</td>
<td> </td></tr></tbody>
</table>
-<p>From table above, we can see that if we define the dependency type as war, we will hit the war handler, that will
+<p>From table above, we can see that if we define the dependency type as “war”, we will hit the “war” handler, that will
result in using the <code>war</code> extension (which may not be obvious, as the type and extension we end up with are the same, but internally this
-indirection does happen). The test-jar is more obvious, as it translates to <code>jar</code> extension. Finally, the <strong>any</strong>
-last row will be used if none above matches, hence in that case your type is used just as extension, for example
+indirection does happen). The “test-jar” is more obvious, as it translates to <code>jar</code> extension. Finally, the <strong>any</strong>
+last row will be used if none above matches, hence in that case your “type” is used just as “extension”, for example
you can write <code><type>tar.gz</type></code> for dependency, and you will end up with extension <code>tar.gz</code> (all this happens
-because as there is no artifact handler named tar.gz in table above). Still, you should be aware that this table
+because as there is no artifact handler named “tar.gz” in table above). Still, you should be aware that this table
above may be extended by various plugins and extensions you use in your build!</p>
-<p>Also, this has interesting consequences, consider for example following Artifact:
+<p>Also, this has “interesting” consequences, consider for example following Artifact:
<code>org.project:reusable-test-support:1.0:tests:jar</code>. With type handlers above, maybe surprisingly, the dependency to
this very same artifact can be described in two ways:</p>
@@ -379,15 +379,15 @@ this very same artifact can be described
<type>test-jar</type>
</dependency>
</code></pre></div>
-<p>Obvious difference is presence of <code>classifier</code> in first case, while in second lack of it but presence of <code>type</code> test-jar,
-that in the other hand, implies classifier of tests. In both cases, extension is jar (in first it uses the default
+<p>Obvious difference is presence of <code>classifier</code> in first case, while in second lack of it but presence of <code>type</code> “test-jar”,
+that in the other hand, implies classifier of “tests”. In both cases, extension is “jar” (in first it uses the default
value for this property, while in second type defines it).</p>
-<p>Note: In this very case, using the first way is somewhat explicit, and is recommended way. Not so for the
+<p>Note: In this very case, using the first way is somewhat “explicit”, and is recommended way. Not so for the
cases when type handler carries some important extra information (like some custom packaging), where using <code>type</code>
-is more appropriate. Simply put, in this case the type test-jar is like an alias for ordinary JARs with tests
+is more appropriate. Simply put, in this case the type “test-jar” is like an alias for ordinary JARs with “tests”
classifier.</p></section><section>
-<h2><a name="Summary"></a>Summary</h2>
-<p>In short, this is how various Maven bits like project, parent project, plugin, extension and dependency
+<h2>Summary</h2>
+<p>In short, this is how various Maven bits like “project”, “parent project”, “plugin”, “extension” and “dependency”
have artifact coordinates mapped from POM elements. Using this knowledge, we can always deduce the artifact coordinate
of these POM elements.</p></section></section>
</main>
Modified: maven/website/content/repositories/index.html
==============================================================================
--- maven/website/content/repositories/index.html (original)
+++ maven/website/content/repositories/index.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/repositories/index.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/index.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Maven Repositories</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
@@ -130,7 +130,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Maven_Repositories"></a>Maven Repositories</h1><!--
+<h1>Maven Repositories</h1><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -154,8 +154,8 @@ and artifacts you build are being stored
fundamental concepts of Maven since its inception: Maven command line tool and Maven Repositories were mold together
and developed since the beginning of Maven project itself.</p>
-<p align="center">
-<img src="../repository/maven-repositories.png" border="0" usemap="#map" alt="" />
+<p>
+<img src="../repository/maven-repositories.png" alt="" />
<map name="map">
<area shape="rect" coords="596,326,666,363" alt="JBoss" href="http://repository.jboss.org/maven2/" />
<area shape="rect" coords="0,184,460,421" alt="central (default)" href="../repository/index.html" />
Modified: maven/website/content/repositories/layout.html
==============================================================================
--- maven/website/content/repositories/layout.html (original)
+++ maven/website/content/repositories/layout.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/repositories/layout.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/layout.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Maven Repository Layout</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
@@ -130,7 +130,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Maven_Repository_Layout"></a>Maven Repository Layout</h1><!--
+<h1>Maven Repository Layout</h1><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -151,43 +151,43 @@ under the License.
<p>The layout is responsible for translating the <a href="artifacts.html">artifact coordinates</a> into generic paths, that is later used to construct some
URI (file path, URL, it depends on context). Obviously, since Maven inception in 2002 the layout evolved as well.
-For simplicity, we will cover current layout (aka maven2 or default), as since Maven 3.x release, the deprecated
-Maven1 layout (aka legacy) is not supported anymore.</p>
-<p>This above implies following: if the repository contains a file that is not on layout (does not obey layout
-transformation rules discussed below), that file is not addressable by Maven coordinates, you cannot address that file
+For simplicity, we will cover current layout (aka “maven2” or “default”), as since Maven 3.x release, the deprecated
+“Maven1 layout” (aka “legacy”) is not supported anymore.</p>
+<p>This above implies following: if the repository contains a file that is “not on layout” (does not obey layout
+transformation rules discussed below), that file is “not addressable” by Maven coordinates, you cannot address that file
in Maven nor make it to download it using GAV coordinates!</p>
<p>The original premise of layout was simplicity: from historical perspective, a remote repository was expected to be run
by some computer with file storage (where artifacts were laid down) and served by a HTTP server, essentially publishing
the files on file paths for consumption (mainly for HTTP GET requests).</p>
<p>The transformation rule is quite simple for that matter: consider artifact properties below:</p>
-<table border="0" class="table table-striped">
+<table class="table table-striped">
<thead>
<tr class="a">
<th>Name</th>
<th>Transformation</th>
<th>Result example</th></tr></thead><tbody>
<tr class="b">
-<td align="left">groupId</td>
-<td>Replace . (dot) characters with / (slash) character</td>
+<td>groupId</td>
+<td>Replace “.” (dot) characters with “/” (slash) character</td>
<td><code>org.apache.maven</code> -> <code>org/apache/maven</code></td></tr>
<tr class="a">
-<td align="left">artifactId</td>
+<td>artifactId</td>
<td>none</td>
<td><code>apache-maven</code></td></tr>
<tr class="b">
-<td align="left">version</td>
+<td>version</td>
<td>none</td>
<td><code>3.8.4</code></td></tr>
<tr class="a">
-<td align="left">baseVersion</td>
+<td>baseVersion</td>
<td>none</td>
<td>(in this example same as version)</td></tr>
<tr class="b">
-<td align="left">classifier</td>
+<td>classifier</td>
<td>none</td>
<td><code>bin</code></td></tr>
<tr class="a">
-<td align="left">extension</td>
+<td>extension</td>
<td>none</td>
<td><code>tar.gz</code></td></tr></tbody>
</table>
@@ -208,10 +208,10 @@ the files on file paths for consumption
<div class="source"><pre class="prettyprint linenums"><code>org/apache/maven/apache-maven/3.8.4/apache-maven-3.8.4-bin.tar.gz
</code></pre></div>
-<p>And that is it! By applying this algorithm above to ANY Artifact we can build up the path segment that
+<p>And that is it! By applying this “algorithm” above to ANY Artifact we can build up the path segment that
artifact is expected to be.</p>
<p>Important note: in case of locally installed artifacts (those you built locally and invoked <code>mvn install</code>) will use
-Artifact baseVersion property instead of version. The full-blown timestamped versions are used only in
+Artifact baseVersion property instead of version. The full-blown “timestamped” versions are used only in
remote repositories, when the artifact is deployed.</p></section>
</main>
</div>
Modified: maven/website/content/repositories/local.html
==============================================================================
--- maven/website/content/repositories/local.html (original)
+++ maven/website/content/repositories/local.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/repositories/local.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/local.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Maven Local Repositories</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
@@ -130,7 +130,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Maven_Local_Repositories"></a>Maven Local Repositories</h1><!--
+<h1>Maven Local Repositories</h1><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -153,17 +153,17 @@ under the License.
remote repositories along with locally built and installed ones.</p>
<p>While the local repository does reside on local filesystem, users should <strong>never</strong> reach for its contents directly
using plain file operations, but use the provided API instead. Reason for this strict expectation is that even
-today different implementations of local repository exists. Hence, reverse engineering the layout and direct
+today different implementations of local repository exists. Hence, “reverse engineering” the layout and direct
access to locally cached or installed files may not only break in the future, but may also circumvent important
-aspects like locking and synchronization, and so forth. Latest resolver even implements split local repository,
+aspects like locking and synchronization, and so forth. Latest resolver even implements “split” local repository,
where user may configure local repository to split the installed and cached artifacts, hence to make them physically
split from each other.</p>
<p>All these underlying changes remain hidden from code using local repository API, and hence, the code will
be more robust and time proof.</p><section>
-<h2><a name="The_baseVersion_Artifact_Property"></a>The <code>baseVersion</code> Artifact Property</h2>
-<p>As noted in <a href="layout.html">Layout</a> page, locally built and installed (implies to local repository) artifacts will use
+<h2>The <code>baseVersion</code> Artifact Property</h2>
+<p>As noted in <a href="layout.html">Layout</a> page, locally built and installed (implies “to local repository”) artifacts will use
<code>baseVersion</code> while calculating layout. Hence, in this case both, <code>baseVersion</code> and <code>version</code> of them will both
-contain same value, the one ending with SNAPSHOT constant string, no transformation is applied to file name.</p>
+contain same value, the one ending with “SNAPSHOT” constant string, no transformation is applied to file name.</p>
<p>Snapshots pulled from remote and cached in local repository will have timestamped <code>version</code> property instead, hence
they will have the full-blown timestamped version applied to file name.</p></section></section>
</main>
Modified: maven/website/content/repositories/metadata.html
==============================================================================
--- maven/website/content/repositories/metadata.html (original)
+++ maven/website/content/repositories/metadata.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/repositories/metadata.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/metadata.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Maven Metadata</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
@@ -130,7 +130,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Maven_Metadata"></a>Maven Metadata</h1><!--
+<h1>Maven Metadata</h1><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -149,7 +149,7 @@ specific language governing permissions
under the License.
-->
-<p>Repositories contain metadata (aka repository metadata) files as well, that enables several discovery and resolution-like operations
+<p>Repositories contain metadata (aka “repository metadata”) files as well, that enables several “discovery” and “resolution”-like operations
for Maven. These metadata files are <strong>not</strong> Artifacts, and hence, are not addressable by Maven users. They are instead
transparently operated and handled by Maven itself in automatic manner. These files are XML files named as
<code>maven-metadata.xml</code> (are deployed with checksums just like artifacts are).</p>
@@ -172,20 +172,20 @@ and its <a href="/ref/current/maven-repo
kinds of metadata (for different Artifacts)! Consider these two artifacts: <code>org.foo:bar:1.0</code> and <code>org.foo.bar:baz:1.0</code>.
With default layout, the repository path <code>org/foo/bar</code> is once A level for first, and G level for second artifact.
Note: this is extreme example, and such artifact naming should be avoided!</p><section>
-<h2><a name="The_G_Level_Metadata"></a>The G Level Metadata</h2>
-<table border="0" class="table table-striped">
+<h2>The G Level Metadata</h2>
+<table class="table table-striped">
<thead>
<tr class="a">
<th>What</th>
<th>How</th></tr></thead><tbody>
<tr class="b">
-<td align="left">Location</td>
+<td>Location</td>
<td>Path corresponding to groupId</td></tr>
<tr class="a">
-<td align="left">Repositories containing it</td>
+<td>Repositories containing it</td>
<td>Release and Snapshots</td></tr>
<tr class="b">
-<td align="left">Artifacts related to them</td>
+<td>Artifacts related to them</td>
<td>Only <code>maven-plugin</code> packaged</td></tr></tbody>
</table>
@@ -195,21 +195,21 @@ considered for this kind of metadata is
<p>Example: <a href="https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml" class="externalLink">https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml</a></p>
<p>When user uses some plugin prefix on CLI, Maven will go through registered <code>pluginGroups</code> groupIds, download their
G level metadata, and look for prefix. If found, Maven has obtained G (from pluginGroups) and A (from metadata)
-coordinates of plugin, and will go for given version, or attempt to discover latest version.</p></section><section>
-<h2><a name="The_A_Level_Metadata"></a>The A Level Metadata</h2>
-<table border="0" class="table table-striped">
+coordinates of plugin, and will go for given version, or attempt to discover “latest” version.</p></section><section>
+<h2>The A Level Metadata</h2>
+<table class="table table-striped">
<thead>
<tr class="a">
<th>What</th>
<th>How</th></tr></thead><tbody>
<tr class="b">
-<td align="left">Location</td>
+<td>Location</td>
<td>Path corresponding to artifactId</td></tr>
<tr class="a">
-<td align="left">Repositories containing it</td>
+<td>Repositories containing it</td>
<td>Release and Snapshots</td></tr>
<tr class="b">
-<td align="left">Artifacts related to them</td>
+<td>Artifacts related to them</td>
<td>All</td></tr></tbody>
</table>
@@ -225,20 +225,20 @@ contains list of versions of given GA co
<li><code>metadata/versionining/lastUpdated</code></li>
</ul>
<p>Example: <a href="https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/maven-metadata.xml" class="externalLink">https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-jar-plugin/maven-metadata.xml</a></p></section><section>
-<h2><a name="The_V_Level_Metadata"></a>The V Level Metadata</h2>
-<table border="0" class="table table-striped">
+<h2>The V Level Metadata</h2>
+<table class="table table-striped">
<thead>
<tr class="a">
<th>What</th>
<th>How</th></tr></thead><tbody>
<tr class="b">
-<td align="left">Location</td>
+<td>Location</td>
<td>Path corresponding to baseVersion</td></tr>
<tr class="a">
-<td align="left">Repositories containing it</td>
+<td>Repositories containing it</td>
<td>Snapshots only</td></tr>
<tr class="b">
-<td align="left">Artifacts related to them</td>
+<td>Artifacts related to them</td>
<td>Only Snapshots</td></tr></tbody>
</table>
Modified: maven/website/content/repositories/remote.html
==============================================================================
--- maven/website/content/repositories/remote.html (original)
+++ maven/website/content/repositories/remote.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/repositories/remote.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repositories/remote.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Maven Remote Repositories</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
@@ -130,7 +130,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Maven_Remote_Repositories"></a>Maven Remote Repositories</h1><!--
+<h1>Maven Remote Repositories</h1><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -160,15 +160,15 @@ repositories are holding the artifacts t
<p>In essence, Maven using <a href="layout.html">Layout</a> produces relative paths for <a href="artifacts.html">Artifacts</a>, that in turn are
resolved against baseURL of Remote Repositories ending in absolute URLs. The policy decides should a release or snapshot
artifact looked for in given repository.</p><section>
-<h2><a name="The_baseVersion_Artifact_Property"></a>The <code>baseVersion</code> Artifact Property</h2>
+<h2>The <code>baseVersion</code> Artifact Property</h2>
<p>In case of snapshot artifacts (hence Snapshot Remote Repositories implied) we already hinted that some
-sort of version transformation happens. We can distinguish two cases:</p><section>
-<h3><a name="Deploying_Snapshot_Artifact"></a>Deploying Snapshot Artifact</h3>
-<p>Your POM locally usually contains snapshot versions in a form of a string that ends with SNAPSHOT constant string
-(for example 1.0-SNAPSHOT). But, in case of deploy, this version is being transformed to a timestamped snapshot
+sort of “version transformation” happens. We can distinguish two cases:</p><section>
+<h3>Deploying Snapshot Artifact</h3>
+<p>Your POM locally usually contains snapshot versions in a form of a string that ends with “SNAPSHOT” constant string
+(for example “1.0-SNAPSHOT”). But, in case of deploy, this version is being transformed to a “timestamped snapshot”
on the fly (by Maven) and when you check the deployed result, you will see that artifact file does not end up with
-SNAPSHOT anymore, but a timestamp and build number. Also, during deploy, Maven will deploy required Maven V Level Metadata
-as well that will describe for consumers of this snapshot how to reverse this process.</p>
+“SNAPSHOT” anymore, but a timestamp and build number. Also, during deploy, Maven will deploy required Maven V Level Metadata
+as well that will describe for consumers of this snapshot how to “reverse” this process.</p>
<p>So, in case of snapshot deploy, version transformation happens in form of:</p>
<div class="source"><pre class="prettyprint linenums"><code>1.0-SNAPSHOT -> Maven (on the fly) -> 1.0-${YYYYMMDD.HHMMSS}-${counter}
@@ -176,10 +176,10 @@ as well that will describe for consumers
<p>Where the date in <code>Etc/UTC</code> timezone (used in <code>YYYYMMDD.HHMMSS</code> format) is constant across deploy from same session (is time when Maven
Session was created), and counter is increased counter from previously deployed metadata (or if no
remote metadata exists, is initialized with 1).</p></section><section>
-<h3><a name="Consuming_Snapshot_Artifacts"></a>Consuming Snapshot Artifacts</h3>
+<h3>Consuming Snapshot Artifacts</h3>
<p>If your project depends on SNAPSHOT dependencies, the POM of your project usually contains <code>version</code> value that ends
-with SNAPSHOT (for example 1.0-SNAPSHOT), still, as we see above, remote repositories do NOT contain such versions,
-but only timestamped ones. Maven snapshots are moving targets, hence, during resolution Maven
+with “SNAPSHOT” (for example “1.0-SNAPSHOT”), still, as we see above, remote repositories do NOT contain such versions,
+but only timestamped ones. Maven snapshots are “moving targets”, hence, during resolution Maven
will use the deployed metadata first, to figure out <code>baseVersion</code> -> <code>version</code> (timestamped) mapping, and only then
will fetch the required files.</p>
<p>In case of consuming snapshot, the following transformation happens:</p>
@@ -187,10 +187,10 @@ will fetch the required files.</p>
<div class="source"><pre class="prettyprint linenums"><code>1.0-SNAPSHOT -> Remote V Level Repository Metadata -> 1.0-YYYYMMDD.HHMMS-X
</code></pre></div>
<p>Due this indirection (the real filename of artifact, the version part) is figured from deployed Maven repository metadata,
-the snapshot artifacts are moving target: each snapshot deployment as above will deploy new metadata, hence, will
+the snapshot artifacts are “moving target”: each snapshot deployment as above will deploy new metadata, hence, will
alter this transformation here (Maven will download different snapshot artifact).</p>
-<p>Note: it is possible to lock down snapshot artifacts, by using timestamped version in version field of a dependency,
-and it will ensure Maven downloads always same artifact (is not moving target anymore), but <strong>Maven will still consider
+<p>Note: it is possible to “lock down” snapshot artifacts, by using timestamped version in version field of a dependency,
+and it will ensure Maven downloads always same artifact (is not “moving target” anymore), but <strong>Maven will still consider
that dependency as snapshot</strong>, and all the fine print applies (for example, release plugin will refuse to release such
a project).</p></section></section></section>
</main>
Modified: maven/website/content/repository-management.html
==============================================================================
--- maven/website/content/repository-management.html (original)
+++ maven/website/content/repository-management.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/repository-management.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repository-management.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Best Practice - Using a Repository Manager</title>
<link rel="stylesheet" href="./css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="./css/site.css" />
@@ -151,7 +151,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section><section>
-<h2><a name="Best_Practice_-_Using_a_Repository_Manager"></a>Best Practice - Using a Repository Manager</h2><!--
+<h2>Best Practice - Using a Repository Manager</h2><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -174,7 +174,7 @@ under the License.
repositories of binary components.</p>
<p>The usage of a repository manager is
considered an essential best practice for any significant usage of Maven.</p><section>
-<h3><a name="Purpose"></a>Purpose</h3>
+<h3>Purpose</h3>
<p>A repository manager serves these essential purposes:</p>
<ul>
@@ -183,7 +183,7 @@ considered an essential best practice fo
<li>provide repositories as a deployment destination for your Maven project
outputs</li>
</ul></section><section>
-<h3><a name="Benefits_and_Features"></a>Benefits and Features</h3>
+<h3>Benefits and Features</h3>
<p>Using a repository manager provides the following benefits and features:</p>
<ul>
@@ -198,7 +198,7 @@ also QA or operations teams or even cust
<li>provides an effective platform for exchanging binary artifacts within
your organization and beyond without the need for building artifact from source</li>
</ul></section><section>
-<h3><a name="Available_Repository_Managers"></a>Available Repository Managers</h3>
+<h3>Available Repository Managers</h3>
<p>The following list (alphabetical order) of open source and commercial repository
managers are known to support the repository format used by Maven. Please refer to the respective linked web sites for further information about repository management in general
and the features provided by these products.</p>
Modified: maven/website/content/repository/central-index.html
==============================================================================
--- maven/website/content/repository/central-index.html (original)
+++ maven/website/content/repository/central-index.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/repository/central-index.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/repository/central-index.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Hervé Boutemy" />
<meta name="date" content="2017-04-23" />
<title>Maven – Central Index</title>
@@ -139,11 +139,11 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Central_Index"></a>Central Index</h1>
+<h1>Central Index</h1>
<p>Central repository provides <a class="externalLink" href="https://repo.maven.apache.org/maven2/.index/">an index</a> that is updated weekly as full (<code>nexus-maven-repository-index.gz</code>) and incremental (<code>nexus-maven-repository-index.<n>.gz</code> + <code>nexus-maven-repository-index.properties</code>).</p>
<p>This index is build using <a href="/maven-indexer/">Maven Indexer</a>: see <a href="/maven-indexer-archives/maven-indexer-LATEST/indexer-core/">LATEST indexer-core documentation</a> for more details on the fields that are available.</p>
<p>You can use <a href="/maven-indexer-archives/maven-indexer-LATEST/indexer-core/apidocs/">Maven Indexer API</a> (see <a href="/maven-indexer-archives/maven-indexer-LATEST/indexer-examples/">examples</a>) to use this index with a dedicated API, or use <a class="externalLink" href="http://lucene.apache.org/">Apache Lucene</a> indexes browsers like <a class="externalLink" href="https://github.com/DmitryKey/luke">Luke</a> or <a class="externalLink" href="https://github.com/flaxsearch/marple">Marple</a> after unpacking the index (see <a href="/maven-indexer-archives/maven-indexer-LATEST/indexer-cli/"><code>-u</code> CLI option</a>).</p><section>
-<h2><a name="Digging_Into_Central_Index_with_Luke"></a>Digging Into Central Index with Luke</h2>
+<h2>Digging Into Central Index with Luke</h2>
<ul>
<li>download <a class="externalLink" href="https://repo.maven.apache.org/maven2/.index/">the Central index: <code>nexus-maven-repository-index.gz</code></a></li>
<li>download <a class="externalLink" href="https://repo.maven.apache.org/maven2/org/apache/maven/indexer/indexer-cli/5.1.1/indexer-cli-5.1.1.jar">Maven Indexer CLI</a> and <a href="/maven-indexer-archives/maven-indexer-LATEST/indexer-cli/">unpack</a> the index to raw Lucene index directory:
Modified: maven/website/content/repository/central-metadata.html
==============================================================================
--- maven/website/content/repository/central-metadata.html (original)
+++ maven/website/content/repository/central-metadata.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/repository/central-metadata.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/repository/central-metadata.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Carlos Sanchez" />
<meta name="date" content="2005-10-31" />
<title>Maven – Guide to Metadata in Central Maven Repository</title>
@@ -139,13 +139,13 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Guide_to_add.2C_improve_or_fix_metadata_in_the_Central_Maven_Repository"></a>Guide to add, improve or fix metadata in the Central Maven Repository</h1><section>
-<h2><a name="POM_Metadata"></a>POM Metadata</h2>
+<h1>Guide to add, improve or fix metadata in the Central Maven Repository</h1><section>
+<h2>POM Metadata</h2>
<p>There are artifacts in the <a href="./">Central Maven repository</a> 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 <i>Maven 1</i> 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.</p>
<p>We don't change dependencies in POMs already in the repository anymore as builds need to be reproducible. Same applies to POMs that don't exist. We can only add a POM with no dependencies, because doing any other way would break previous builds that were using that artifact.</p>
<p>An alternative is to create a new version with the fixes. If the broken artifact is <code>org.foo/bar/1.0</code> you can provide a fixed POM, JAR,... under <code>org.foo/bar/1.0-1</code> (add a comment to the POM explaining what is being fixed and why). See <a href="./guide-central-repository-upload.html">Maven Repository Upload</a> for the instructions to get this new version in the repository.</p>
<p>You need to contact the original publisher of the metadata to make sure in next versions it will be fixed or improved before getting it into the repository.</p></section><section>
-<h2><a name="Other_Issues"></a>Other Issues</h2>
+<h2>Other Issues</h2>
<p>For any other types of issues related to metadata in the repository (POM related, or <a href="/ref/current/maven-repository-metadata/"><code>maven-metadata.xml</code></a>, or anything else), open an issue at <a class="externalLink" href="https://issues.sonatype.org/browse/MVNCENTRAL">MVNCENTRAL</a> with the relevant information and explain the reasons why it is an issue.</p>
<p><b>Important:</b> 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.</p></section></section>
</main>
Modified: maven/website/content/repository/guide-central-repository-upload.html
==============================================================================
--- maven/website/content/repository/guide-central-repository-upload.html (original)
+++ maven/website/content/repository/guide-central-repository-upload.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/repository/guide-central-repository-upload.apt at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/apt/repository/guide-central-repository-upload.apt at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Jason van Zyl
Brian Fox" />
<meta name="date" content="2018-12-31" />
@@ -140,9 +140,9 @@ Brian Fox" />
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Guide_to_uploading_artifacts_to_the_Central_Repository"></a>Guide to uploading artifacts to the Central Repository</h1>
+<h1>Guide to uploading artifacts to the Central Repository</h1>
<p>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 should deploy their artifacts to the <a href="/repository/">Central Repository</a>.</p></section><section>
-<h1><a name="Requirements"></a>Requirements</h1>
+<h1>Requirements</h1>
<ol style="list-style-type: decimal">
<li><b>releases</b>: Only <i>releases</i> 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,</li>
<li><b>javadoc and sources</b> for IDE lookup,</li>
@@ -150,11 +150,11 @@ Brian Fox" />
<li><b>minimum POM information</b>: There are some requirements for the minimal information in the POMs that are in the Central Repository, see <a class="externalLink" href="https://central.sonatype.org/pages/requirements.html#sufficient-metadata">here</a>, </li>
<li><b>coordinates</b>: Picking the appropriate coordinates for your project is important. See the guidelines <a class="externalLink" href="https://central.sonatype.org/pages/choosing-your-coordinates.html">here</a>, particularly on <a class="externalLink" href="https://central.sonatype.org/pages/producers.html#individual-projects-open-source-software-repository-hosting-ossrh">groupId and domain ownership</a>.</li></ol>
<p>The updated list of requirements can be found <b><a class="externalLink" href="https://central.sonatype.org/pages/requirements.html">here</a></b>.</p><section>
-<h2><a name="Explanation"></a>Explanation</h2>
+<h2>Explanation</h2>
<p>Some folks have asked <i>"why do we require all this information in the POM for deployed artifacts?"</i>, so here's a small explanation.</p>
<p>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 Central Repository as part of the process we open up the doors to new ideas that involve unified access to project POMs.</p>
<p>We ask for the license because it is possible that your project's license may change in the course of its lifetime, and we are trying to create tools to help 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.</p></section><section>
-<h2><a name="A_basic_sample:"></a>A basic sample:</h2>
+<h2>A basic sample:</h2>
<div class="source"><pre class="prettyprint linenums">
<project>
<modelVersion>4.0.0</modelVersion>
@@ -195,10 +195,10 @@ Brian Fox" />
-->
</project>
</pre></div></section><section>
-<h2><a name="PGP_Signature"></a>PGP Signature</h2>
+<h2>PGP Signature</h2>
<p>When people download artifacts from the Central Repository, they might want to verify these artifacts' PGP signatures against a public key server. If there are no signatures, then users have no guarantee that they are downloading the original artifact.</p>
<p>To improve the quality of the Central Repository, we require you to provide PGP signatures for all your artifacts (all files except checksums), and distribute your public key to a key server like <a class="externalLink" href="http://pgp.mit.edu">http://pgp.mit.edu</a>. Read <a class="externalLink" href="http://central.sonatype.org/pages/working-with-pgp-signatures.html">Working with PGP Signatures</a> for more information.</p></section><section>
-<h2><a name="FAQ_and_common_mistakes"></a>FAQ and common mistakes</h2>
+<h2>FAQ and common mistakes</h2>
<ul>
<li>I have other <code>repositories</code> or <code>pluginRepositories</code> listed in my POM, is that a problem?
<p>At present, this won't preclude your project from being included, but we do strongly encourage making sure all your dependencies are included in the Central Repository. If you rely on sketchy repositories that have junk in them or disappear, it just creates havok for downstream users. Try to keep your dependencies among reliable repos like Central, Jboss, etc.</p></li>
@@ -208,17 +208,17 @@ Brian Fox" />
<p>When you patch / modify a third party project, that patched version becomes your project and therefore should be distributed under a <code>groupId</code> you control as any project you would have developed, never under <code>com.foo</code>. See above considerations about <code>groupId</code>.</p></li>
<li>My project is hosted at a project hosting service like SourceForge or Github, what should I use as groupId?
<p>If your project name is <code>foo</code> at SourceForge, you can use <code>net.sf.foo</code>. If your username is <code>bar</code> on Github, you can use <code>com.github.bar</code>. You can also use another reversed domain name you control. The group ID does not have to reflect the project host.</p></li></ul></section></section><section>
-<h1><a name="Publishing_your_artifacts_to_the_Central_Repository"></a>Publishing your artifacts to the Central Repository</h1><section>
-<h2><a name="Approved_Repository_Hosting"></a>Approved Repository Hosting</h2>
+<h1>Publishing your artifacts to the Central Repository</h1><section>
+<h2>Approved Repository Hosting</h2>
<p>Instead of maintaining repository rsync feeds for each projects, we now encourage projects to use an approved repository hosting location.</p>
<p>Currently approved repository hosting locations:</p>
<ul>
<li><a class="externalLink" href="https://repository.apache.org/">Apache Software Foundation</a> (for all Apache projects)</li>
<li>see <a class="externalLink" href="https://central.sonatype.org/publish/large-orgs/">the full list</a></li></ul>
<p>Automatic publication will be provided for Forges that provide hosting services for OSS projects and other large project repositories 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, <a class="externalLink" href="https://central.sonatype.org/publish/large-orgs/">contact us</a>.</p></section><section>
-<h2><a name="Other_Projects"></a>Other Projects</h2>
+<h2>Other Projects</h2>
<p>The easiest way to upload another project is to use the <a class="externalLink" href="https://central.sonatype.org/pages/ossrh-guide.html">Open Source Software Repository Hosting (OSSRH)</a>, which is an approved repository provided by Sonatype for <i>any</i> OSS Project that wants to get its artifacts into the Central Repository.</p></section><section>
-<h2><a name="Explanations"></a>Explanations</h2>
+<h2>Explanations</h2>
<p>Having each project maintain its own repository with rsync to the Central Repository was the preferred process until January 2010. However, we are no longer accepting rsync requests on a per project basis.</p>
<p>Over time, we have learned that this process is not scalable. Many of the projects being synced release very infrequently, yet we have to hit hundreds of servers several times a day looking for artifacts that don't change. Additionally, there is no good mechanism currently for validating the incoming data via the rsync, and this leads to bad metadata that affects everyone. </p>
<p>The aggregation of projects into larger feeds allows us to sync faster and more often, and ensuring these locations perform sufficient checks increases the quality of metadata for everyone.</p></section></section>
Modified: maven/website/content/repository/index.html
==============================================================================
--- maven/website/content/repository/index.html (original)
+++ maven/website/content/repository/index.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/xdoc/repository/index.xml at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/xdoc/repository/index.xml at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<meta name="author" content="Brett Porter" />
<meta name="author" content="Hervé Boutemy" />
<title>Maven – Maven Central Repository</title>
@@ -143,7 +143,7 @@
<section>
-<h1><a name="Maven_Central_Repository"></a>Maven Central Repository</h1>
+<h1>Maven Central Repository</h1>
<p>This documentation is for those that need to use or contribute to the Maven <code>central</code> repository. This includes those
@@ -169,8 +169,8 @@
-<p align="center">
- <img src="maven-central-repository.png" border="0" usemap="#map" alt="" />
+<p>
+ <img src="maven-central-repository.png" alt="" />
<map name="map">
<area shape="rect" coords="0,0,189,128" alt="standalone public artifact repositories" href="/guides/introduction/introduction-to-repositories.html" />
Modified: maven/website/content/repository/layout.html
==============================================================================
--- maven/website/content/repository/layout.html (original)
+++ maven/website/content/repository/layout.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/repository/layout.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/repository/layout.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Maven2 Repository Layout</title>
<link rel="stylesheet" href="../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../css/site.css" />
@@ -137,7 +137,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section><section>
-<h2><a name="Maven2_Repository_Layout"></a>Maven2 Repository Layout</h2><!--
+<h2>Maven2 Repository Layout</h2><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -206,7 +206,7 @@ see <a href="/ref/current/maven-core/art
<li><code><classifier></code> is optional, to override default classifier defined by the dependency type.</li>
</ul></li>
</ul></section><section>
-<h2><a name="SNAPSHOT"></a>SNAPSHOT</h2>
+<h2>SNAPSHOT</h2>
<p>In case of a SNAPSHOT version, version directory uses base version, i.e. version ending in <code>-SNAPSHOT</code>, for example <code>3.8.4-SNAPSHOT</code>.</p>
<p>For artifact files, there are 2 options available:</p>
<ol style="list-style-type: decimal">
@@ -214,9 +214,9 @@ see <a href="/ref/current/maven-core/art
<li>unique SNAPSHOT artifacts, using the same base version,</li>
<li>multiple SNAPSHOT artifacts for one base version, each deployment will have an effective version where <code>SNAPSHOT</code> is replaced with <code>YYYYMMDD.HHMMSS-${counter}</code>.</li>
</ol></section><section>
-<h2><a name="Protocol"></a>Protocol</h2>
+<h2>Protocol</h2>
<p>Repository can be accessed through many file-oriented protocols, both for read and write: most classical are <code>file://</code>, <code>http://</code> and <code>https://</code> (<code>GET</code> and <code>PUT</code>).
-Older (now generally unused) protocols are FTP(S), SCP, SSH, </p>
+Older (now generally unused) protocols are FTP(S), SCP, SSH, …</p>
<p>HTTP/HTTPS protocol have 2 specific characteristics:</p>
<ol style="list-style-type: decimal">
Modified: maven/website/content/resource/branding/actioncards.html
==============================================================================
--- maven/website/content/resource/branding/actioncards.html (original)
+++ maven/website/content/resource/branding/actioncards.html Wed Feb 8 20:32:12 2023
@@ -2,14 +2,14 @@
<!--
- | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/resource/branding/actioncards.md at 2023-02-08
+ | Generated by Apache Maven Doxia Site Renderer 2.0.0-M4 from content/markdown/resource/branding/actioncards.md at 2023-02-08
| Rendered using Apache Maven Fluido Skin 1.11.1
-->
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
- <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M4" />
<title>Maven – Action Cards</title>
<link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.1.min.css" />
<link rel="stylesheet" href="../../css/site.css" />
@@ -122,7 +122,7 @@
</header>
<main id="bodyColumn" class="span10" >
<section>
-<h1><a name="Action_Cards"></a>Action Cards</h1><!--
+<h1>Action Cards</h1><!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -182,7 +182,8 @@ under the License.
<li class="span3">
<a href="/images/branding/i_am_a_maven_committer_1.png"><img src="/images/branding/i_am_a_maven_committer_1.png" class="thumbnail" alt="" /></a>
</li>
-</ul></section>
+</ul>
+</section>
</main>
</div>
</div>