Modified: maven/website/content/reference/maven-classloading.html ============================================================================== --- maven/website/content/reference/maven-classloading.html (original) +++ maven/website/content/reference/maven-classloading.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/reference/maven-classloading.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/reference/maven-classloading.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – Maven classloading</title> <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="../css/site.css" /> @@ -121,7 +121,8 @@ </div> </header> <main id="bodyColumn" class="span10" > -<h1>Maven classloading</h1><!-- +<section> +<h1><a name="Maven_classloading"></a>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 @@ -145,7 +146,7 @@ under the License. <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> +<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> <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> @@ -167,7 +168,7 @@ under the License. <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> <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> +<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 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> @@ -183,7 +184,7 @@ under the License. <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 class="externalLink" href="https://issues.apache.org/jira/browse/MNG-4747";>MNG-4747</a>).</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> <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> @@ -204,7 +205,7 @@ under the License. <exportedArtifact>org.company:myextension</exportedArtifact> </exportedArtifacts> </extension> -</code></pre></div></section> +</code></pre></div></section></section> </main> </div> </div>
Modified: maven/website/content/release-notes-all.html ============================================================================== --- maven/website/content/release-notes-all.html (original) +++ maven/website/content/release-notes-all.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/release-notes-all.md.vm at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/release-notes-all.md.vm at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – Release Notes</title> <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="./css/site.css" /> @@ -121,7 +121,8 @@ </div> </header> <main id="bodyColumn" class="span10" > -<h1>Release Notes</h1><!-- +<section> +<h1><a name="Release_Notes"></a>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 @@ -199,7 +200,7 @@ under the License. <li><a href="docs/2.0.2/release-notes.html">Release notes for Maven 2.0.2</a></li> <li><a href="docs/2.0.1/release-notes.html">Release notes for Maven 2.0.1</a></li> <li><a href="docs/2.0/release-notes.html">Release notes for Maven 2.0</a></li> -</ul> +</ul></section> </main> </div> </div> Modified: maven/website/content/repository-management.html ============================================================================== --- maven/website/content/repository-management.html (original) +++ maven/website/content/repository-management.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/repository-management.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/repository-management.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – Best Practice - Using a Repository Manager</title> <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="./css/site.css" /> @@ -150,7 +150,7 @@ </div> </header> <main id="bodyColumn" class="span10" > -<section> +<section><section> <h2><a name="Best_Practice_-_Using_a_Repository_Manager"></a>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 @@ -204,21 +204,21 @@ managers are known to support the reposi and the features provided by these products.</p> <ul> -<li><a class="externalLink" href="https://archiva.apache.org/"; target="_blank">Apache Archiva</a> (open source)</li> -<li><a class="externalLink" href="https://bytesafe.dev/"; target="_blank">Bytesafe</a> (commercial)</li> -<li><a class="externalLink" href="https://www.cloudrepo.io"; target="_blank">CloudRepo</a> (commercial)</li> -<li><a class="externalLink" href="https://www.cloudsmith.io"; target="_blank">Cloudsmith Package</a> (commercial)</li> -<li><a class="externalLink" href="https://www.dist.cloud"; target="_blank">Dist</a> (commercial)</li> -<li><a class="externalLink" href="https://docs.gitea.io/en-us/packages/maven/"; target="_blank">Gitea</a> (open source)</li> -<li><a class="externalLink" href="https://inedo.com/proget"; target="_blank">Inedo ProGet</a> (commercial)</li> -<li><a class="externalLink" href="https://www.jfrog.com/open-source"; target="_blank">JFrog Artifactory Open Source</a> (open source)</li> -<li><a class="externalLink" href="https://www.jfrog.com/artifactory/"; target="_blank">JFrog Artifactory Pro</a> (commercial)</li> -<li><a class="externalLink" href="https://www.myget.org"; target="_blank">MyGet</a> (commercial)</li> -<li><a class="externalLink" href="https://www.sonatype.org/nexus/go/"; target="_blank">Sonatype Nexus OSS</a> (open source)</li> -<li><a class="externalLink" href="https://links.sonatype.com/products/nexus/pro/home"; target="_blank">Sonatype Nexus Pro</a> (commercial)</li> -<li><a class="externalLink" href="https://packagecloud.io"; target="_blank">packagecloud.io</a> (commercial)</li> -<li><a class="externalLink" href="https://reposilite.com"; target="_blank">Reposilite</a> (open source)</li> -</ul></section></section> +<li><a href="https://archiva.apache.org/"; target="_blank" class="externalLink">Apache Archiva</a> (open source)</li> +<li><a href="https://bytesafe.dev/"; target="_blank" class="externalLink">Bytesafe</a> (commercial)</li> +<li><a href="https://www.cloudrepo.io"; target="_blank" class="externalLink">CloudRepo</a> (commercial)</li> +<li><a href="https://www.cloudsmith.io"; target="_blank" class="externalLink">Cloudsmith Package</a> (commercial)</li> +<li><a href="https://www.dist.cloud"; target="_blank" class="externalLink">Dist</a> (commercial)</li> +<li><a href="https://docs.gitea.io/en-us/packages/maven/"; target="_blank" class="externalLink">Gitea</a> (open source)</li> +<li><a href="https://inedo.com/proget"; target="_blank" class="externalLink">Inedo ProGet</a> (commercial)</li> +<li><a href="https://www.jfrog.com/open-source"; target="_blank" class="externalLink">JFrog Artifactory Open Source</a> (open source)</li> +<li><a href="https://www.jfrog.com/artifactory/"; target="_blank" class="externalLink">JFrog Artifactory Pro</a> (commercial)</li> +<li><a href="https://www.myget.org"; target="_blank" class="externalLink">MyGet</a> (commercial)</li> +<li><a href="https://www.sonatype.org/nexus/go/"; target="_blank" class="externalLink">Sonatype Nexus OSS</a> (open source)</li> +<li><a href="https://links.sonatype.com/products/nexus/pro/home"; target="_blank" class="externalLink">Sonatype Nexus Pro</a> (commercial)</li> +<li><a href="https://packagecloud.io"; target="_blank" class="externalLink">packagecloud.io</a> (commercial)</li> +<li><a href="https://reposilite.com"; target="_blank" class="externalLink">Reposilite</a> (open source)</li> +</ul></section></section></section> </main> </div> </div> Modified: maven/website/content/repository/central-index.html ============================================================================== --- maven/website/content/repository/central-index.html (original) +++ maven/website/content/repository/central-index.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/repository/central-index.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/repository/central-index.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Hervé Boutemy" /> <meta name="date" content="2017-04-23" /> <title>Maven – Central Index</title> @@ -131,11 +131,11 @@ </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Central_Index"></a>Central Index</h2> +<h1><a name="Central_Index"></a>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> -<h3><a name="Digging_Into_Central_Index_with_Luke"></a>Digging Into Central Index with Luke</h3> +<h2><a name="Digging_Into_Central_Index_with_Luke"></a>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 Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/repository/central-metadata.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/repository/central-metadata.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Carlos Sanchez" /> <meta name="date" content="2005-10-31" /> <title>Maven – Guide to Metadata in Central Maven Repository</title> @@ -131,13 +131,13 @@ </header> <main id="bodyColumn" class="span10" > <section> -<h2><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</h2><section> -<h3><a name="POM_Metadata"></a>POM Metadata</h3> +<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> <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> -<h3><a name="Other_Issues"></a>Other Issues</h3> +<h2><a name="Other_Issues"></a>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 Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/repository/guide-central-repository-upload.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/repository/guide-central-repository-upload.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Jason van Zyl Brian Fox" /> <meta name="date" content="2018-12-31" /> @@ -132,9 +132,9 @@ Brian Fox" /> </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Guide_to_uploading_artifacts_to_the_Central_Repository"></a>Guide to uploading artifacts to the Central Repository</h2> +<h1><a name="Guide_to_uploading_artifacts_to_the_Central_Repository"></a>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> -<h2><a name="Requirements"></a>Requirements</h2> +<h1><a name="Requirements"></a>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> @@ -142,11 +142,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> -<h3><a name="Explanation"></a>Explanation</h3> +<h2><a name="Explanation"></a>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> -<h3><a name="A_basic_sample:"></a>A basic sample:</h3> +<h2><a name="A_basic_sample:"></a>A basic sample:</h2> <div class="source"><pre class="prettyprint linenums"> <project> <modelVersion>4.0.0</modelVersion> @@ -187,10 +187,10 @@ Brian Fox" /> --> </project> </pre></div></section><section> -<h3><a name="PGP_Signature"></a>PGP Signature</h3> +<h2><a name="PGP_Signature"></a>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> -<h3><a name="FAQ_and_common_mistakes"></a>FAQ and common mistakes</h3> +<h2><a name="FAQ_and_common_mistakes"></a>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> @@ -200,17 +200,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> -<h2><a name="Publishing_your_artifacts_to_the_Central_Repository"></a>Publishing your artifacts to the Central Repository</h2><section> -<h3><a name="Approved_Repository_Hosting"></a>Approved Repository Hosting</h3> +<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> <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> -<h3><a name="Other_Projects"></a>Other Projects</h3> +<h2><a name="Other_Projects"></a>Other Projects</h2> <p>The easiest way to upload another project is to use the <a class="externalLink" href="http://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 want to get their artifacts into the Central Repository.</p></section><section> -<h3><a name="Explanations"></a>Explanations</h3> +<h2><a name="Explanations"></a>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 Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/xdoc/repository/index.xml at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/xdoc/repository/index.xml at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Brett Porter" /> <meta name="author" content="Hervé Boutemy" /> <title>Maven – Maven Central Repository</title> @@ -135,7 +135,7 @@ <section> -<h2><a name="Maven_Central_Repository"></a>Maven Central Repository</h2> +<h1><a name="Maven_Central_Repository"></a>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 @@ -144,8 +144,8 @@ <p><img src="../images/icon_warning_sml.gif" alt="" /> - <a class="externalLink" href="https://central.sonatype.org/faq/tls-info/";><b>Discontinuing support for TLSv1.1</b> and below as of <b>June 15th 2018</b></a> - and <a class="externalLink" href="https://central.sonatype.org/news/20190715_http_deprecation_update/";><b>Discontinuing support for HTTP</b> as of <b>January 15th 2020</b></a></p> + <a href="https://central.sonatype.org/faq/tls-info/"; class="externalLink"><b>Discontinuing support for TLSv1.1</b> and below as of <b>June 15th 2018</b></a> + and <a href="https://central.sonatype.org/news/20190715_http_deprecation_update/"; class="externalLink"><b>Discontinuing support for HTTP</b> as of <b>January 15th 2020</b></a></p> <ul> Modified: maven/website/content/repository/layout.html ============================================================================== --- maven/website/content/repository/layout.html (original) +++ maven/website/content/repository/layout.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/repository/layout.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/repository/layout.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – Maven2 Repository Layout</title> <link rel="stylesheet" href="../css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="../css/site.css" /> @@ -128,7 +128,7 @@ </div> </header> <main id="bodyColumn" class="span10" > -<section> +<section><section> <h2><a name="Maven2_Repository_Layout"></a>Maven2 Repository Layout</h2><!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file @@ -148,7 +148,7 @@ specific language governing permissions under the License. --> -<p>Maven2 repository layout format is the default layout used since Maven 2 (see <a class="externalLink" href="https://cwiki.apache.org/confluence/display/MAVENOLD/Repository+Layout+-+Final";>Repository Layout- Final</a> in <a class="externalLink" href="https://cwiki.apache.org/confluence/display/MAVENOLD/Maven+2.0+Design+Documents";>Maven 2.0 Design Documents</a>), superceding old Maven 1 layout:</p> +<p>Maven2 repository layout format is the default layout used since Maven 2 (see <a href="https://cwiki.apache.org/confluence/display/MAVENOLD/Repository+Layout+-+Final"; class="externalLink">Repository Layout- Final</a> in <a href="https://cwiki.apache.org/confluence/display/MAVENOLD/Maven+2.0+Design+Documents"; class="externalLink">Maven 2.0 Design Documents</a>), superceding old Maven 1 layout:</p> <div class="source"><pre class="prettyprint linenums"><code>Repository root `-- ${groupId as directory}/ @@ -181,26 +181,22 @@ under the License. <p><code>maven-metadata.xml</code> file format is defined in <a href="/ref/current/maven-repository-metadata/">Maven Repository Metadata Model</a>.</p> <p><code>.asc</code> file is optional (may be required in some repositories, like Central Repository) and is a PGP detached signature file.</p> <p>Obviously, <code>${groupId}</code>, <code>${artifactId}</code> and <code>${version}</code> are defined in <code>pom.xml</code>. But what about <code>${classifier}</code> and <code>${extension}</code>, how are they defined?</p> -<p>Classifier and extension definition is completely different at artifact <i>publication</i> and <i>usage</i> times:</p> +<p>Classifier and extension definition is completely different at artifact <em>publication</em> and <em>usage</em> times:</p> <ul> <li> - -<p><b>At artifact publication time</b>: Extension and classifier are defined by plugins that create the artifacts and attach them for publication.<br /> +<p><strong>At artifact publication time</strong>: Extension and classifier are defined by plugins that create the artifacts and attach them for publication.<br /> Some plugins provide configuration parameters to be able to override default values. For example, <a href="/plugins/maven-jar-plugin/jar-mojo.html">Maven JAR Plugin's <code>jar:jar</code> goal</a> produces by default an artifact with <code>jar</code> extension and empty classifier. -The <code>classifier</code> goal parameter can be used to define a classifier (there is no parameter to override extension).</p> -</li> +The <code>classifier</code> goal parameter can be used to define a classifier (there is no parameter to override extension).</p></li> <li> - -<p><b>At artifact usage time</b>: Extension and classifier are defined by <a href="/ref/current/maven-model/maven.html#class_dependency"><code><dependency></code>'s <code><type></code> and <code><classifier></code></a> definition in <code>pom.xml</code>:</p> +<p><strong>At artifact usage time</strong>: Extension and classifier are defined by <a href="/ref/current/maven-model/maven.html#class_dependency"><code><dependency></code>'s <code><type></code> and <code><classifier></code></a> definition in <code>pom.xml</code>:</p> <ul> <li><code><type></code> (<code>jar</code> by default) defines the extension and default classifier: <br /> see <a href="/ref/current/maven-core/artifact-handlers.html">default artifact handlers</a> to see default types and corresponding extension and default classifier. <br /></li> <li><code><classifier></code> is optional, to override default classifier defined by the dependency type.</li> -</ul> -</li> +</ul></li> </ul></section><section> <h2><a name="SNAPSHOT"></a>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> @@ -212,20 +208,16 @@ see <a href="/ref/current/maven-core/art </ol></section><section> <h2><a name="Protocol"></a>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"> <li> - -<p>there is no directory listing feature: Maven does not need to list files in a directory, a remote directory does have not provide any directory listing feature,</p> -</li> +<p>there is no directory listing feature: Maven does not need to list files in a directory, a remote directory does have not provide any directory listing feature,</p></li> <li> - -<p><a class="externalLink" href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html";>HTTP/1.1 Reason-Phrase</a> is used to provide extended message when artifact access is rejected by remote repository. -This usage of Reason-Phrase is nowadays legacy and is removed in HTTP/2, <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6795";>MNG-6795</a> is open to create a replacement.</p> -</li> -</ol></section> +<p><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html"; class="externalLink">HTTP/1.1 Reason-Phrase</a> is used to provide extended message when artifact access is rejected by remote repository. +This usage of Reason-Phrase is nowadays legacy and is removed in HTTP/2, <a href="https://issues.apache.org/jira/browse/MNG-6795"; class="externalLink">MNG-6795</a> is open to create a replacement.</p></li> +</ol></section></section> </main> </div> </div> Modified: maven/website/content/resource/branding/actioncards.html ============================================================================== --- maven/website/content/resource/branding/actioncards.html (original) +++ maven/website/content/resource/branding/actioncards.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/resource/branding/actioncards.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/resource/branding/actioncards.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – Action Cards</title> <link rel="stylesheet" href="../../css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="../../css/site.css" /> @@ -121,7 +121,8 @@ </div> </header> <main id="bodyColumn" class="span10" > -<h1>Action Cards</h1><!-- +<section> +<h1><a name="Action_Cards"></a>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 @@ -181,7 +182,7 @@ 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> +</ul></section> </main> </div> </div> Modified: maven/website/content/run-maven/index.html ============================================================================== --- maven/website/content/run-maven/index.html (original) +++ maven/website/content/run-maven/index.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/apt/run-maven/index.apt at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/apt/run-maven/index.apt at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <meta name="author" content="Brett Porter" /> <meta name="date" content="2006-11-03" /> <title>Maven – Running Maven</title> @@ -138,7 +138,7 @@ </header> <main id="bodyColumn" class="span10" > <section> -<h2><a name="Building_a_Project_with_Maven"></a>Building a Project with Maven</h2> +<h1><a name="Building_a_Project_with_Maven"></a>Building a Project with Maven</h1> <p>The vast majority of Maven-built projects can be built with the following command:</p> <div> <pre>mvn verify</pre></div> @@ -146,11 +146,11 @@ <p>That's it! If you look in the <code>target</code> subdirectory, you should find the build output and the final library or application that was being built.</p> <p><b>Note:</b> Some projects have multiple modules, so the library or application you are looking for may be in a module subdirectory.</p> <p>While this will build most projects and Maven encourages this standard convention, builds can be customisable. If this does not suffice, please consult the project's documentation.</p><section> -<h3><a name="More_than_just_the_Build"></a>More than just the Build</h3> +<h2><a name="More_than_just_the_Build"></a>More than just the Build</h2> <p>Maven can do more than just build software - it can assist with testing, run web applications and produce reports on projects, as well as any number of other tasks provided by plug-ins.</p></section><section> -<h3><a name="When_Things_go_Wrong"></a>When Things go Wrong</h3> +<h2><a name="When_Things_go_Wrong"></a>When Things go Wrong</h2> <p>The following are some common problems when building with Maven, and how to resolve them.</p><section> -<h4><a name="Missing_Dependencies"></a>Missing Dependencies</h4> +<h3><a name="Missing_Dependencies"></a>Missing Dependencies</h3> <p>A missing dependency presents with an error like the following:</p> <div> <pre>[INFO] Failed to resolve artifact. @@ -180,7 +180,7 @@ from the specified remote repositories: <p>To resolve this issue, it depends on what the dependency is and why it is missing. The most common cause is because it can not be redistributed from the repository and must be manually installed using the instructions given in the message. This is most common with some older JARs from Sun (usually <code>javax.*</code> group IDs), and is further documented in the <a href="../guides/mini/guide-coping-with-sun-jars.html"> Guide to Coping with Sun JARs</a>.</p> <p>You can check the list of repositories at the end of the error to ensure that the expected ones are listed - it may be that the project requires an alternative repository that has not been declared properly or is not accessible with your Maven configuration.</p> <p>In other cases, it may be an incorrectly declared dependency (like the typo in the example above) which the project would need to fix, like a compilation error.</p></section><section> -<h4><a name="Inconsistent_output"></a>Inconsistent output</h4> +<h3><a name="Inconsistent_output"></a>Inconsistent output</h3> <p>Most plugins are optimized to know if they have to execute their task. In some cases, the output can be polluted from a previous build and the end result is not what you expected. In such rare situations, you can call the <code>clean</code> phase which means: remove the output directory. You can also call it as <code>mvn clean verify</code> which means: first clean up the output directory, next build the project and verify the outcome.</p></section></section></section> </main> </div> Modified: maven/website/content/run.html ============================================================================== --- maven/website/content/run.html (original) +++ maven/website/content/run.html Sat Aug 20 12:41:42 2022 @@ -2,14 +2,14 @@ <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from content/markdown/run.md at 2022-08-20 + | Generated by Apache Maven Doxia Site Renderer 2.0.0-M3 from content/markdown/run.md at 2022-08-20 | Rendered using Apache Maven Fluido Skin 1.11.0 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> - <meta name="generator" content="Apache Maven Doxia Site Renderer 1.11.1" /> + <meta name="generator" content="Apache Maven Doxia Site Renderer 2.0.0-M3" /> <title>Maven – Running Apache Maven</title> <link rel="stylesheet" href="./css/apache-maven-fluido-1.11.0.min.css" /> <link rel="stylesheet" href="./css/site.css" /> @@ -128,7 +128,8 @@ </div> </header> <main id="bodyColumn" class="span10" > -<h1>Running Apache Maven</h1><!-- +<section> +<h1><a name="Running_Apache_Maven"></a>Running Apache Maven</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 @@ -163,21 +164,15 @@ under the License. <ul> <li> - -<p>clean - pre-clean, clean, post-clean</p> -</li> +<p>clean - pre-clean, clean, post-clean</p></li> <li> - <p>default - validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, -verify, install, deploy</p> -</li> +verify, install, deploy</p></li> <li> - -<p>site - pre-site, site, post-site, site-deploy</p> -</li> +<p>site - pre-site, site, post-site, site-deploy</p></li> </ul> <p>A fresh build of a project generating all packaged outputs and the documentation site and deploying it to a repository manager could be done with</p> @@ -190,7 +185,7 @@ and deploying it to a repository manager </code></pre></div> <p>This is the most common build invocation for a Maven project.</p> <p>When not working with a project, and in some other use cases, you might want to invoke -a specific task implemented by a part of Maven - this is called a <b>goal</b> of a plugin. +a specific task implemented by a part of Maven - this is called a <strong>goal</strong> of a plugin. E.g.:</p> <div class="source"><pre class="prettyprint linenums"><code>mvn archetype:generate @@ -204,7 +199,7 @@ E.g.:</p> <ul> <li><a href="./run-maven/index.html">Building a Project with Maven</a></li> -</ul> +</ul></section> </main> </div> </div>
