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 2021/12/02 20:29:29 UTC
svn commit: r1895505 [1/14] - in /maven/website/content: ./ apache-resource-bundles/ archives/maven-2.x/ background/ css/ developers/ developers/conventions/ developers/release/ developers/website/ docs/ docs/2.0.1/ docs/2.0.10/ docs/2.0.11/ docs/2.0.2...
Author: svn-site-role
Date: Thu Dec 2 20:29:27 2021
New Revision: 1895505
Log:
Site checkin for project Apache Maven Site
Added:
maven/website/content/apache-maven.pdf (with props)
maven/website/content/css/apache-maven-fluido-1.10.0.min.css
maven/website/content/js/apache-maven-fluido-1.10.0.min.js
Removed:
maven/website/content/css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css
maven/website/content/js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js
Modified:
maven/website/content/about.html
maven/website/content/aether.html
maven/website/content/apache-resource-bundles/index.html
maven/website/content/archives/maven-2.x/index.html
maven/website/content/archives/maven-2.x/maven-2.1-architectural-goals.html
maven/website/content/articles.html
maven/website/content/background/history-of-maven.html
maven/website/content/background/philosophy-of-maven.html
maven/website/content/ci-management.html
maven/website/content/code-quality-management.html
maven/website/content/community.html
maven/website/content/configure.html
maven/website/content/developers/committer-environment.html
maven/website/content/developers/committer-settings.html
maven/website/content/developers/compatibility-plan.html
maven/website/content/developers/conventions/code.html
maven/website/content/developers/conventions/git.html
maven/website/content/developers/conventions/jira.html
maven/website/content/developers/dependency-policies.html
maven/website/content/developers/index.html
maven/website/content/developers/mojo-api-specification.html
maven/website/content/developers/release/index.html
maven/website/content/developers/release/maven-core-release.html
maven/website/content/developers/release/maven-project-release-procedure.html
maven/website/content/developers/release/parent-pom-release.html
maven/website/content/developers/release/pmc-gpg-keys.html
maven/website/content/developers/retirement-plan-plugins.html
maven/website/content/developers/website/component-reference-documentation-helper.html
maven/website/content/developers/website/deploy-component-reference-documentation.html
maven/website/content/developers/website/deploy-maven-website.html
maven/website/content/developers/website/index.html
maven/website/content/developers/website/website-overview.html
maven/website/content/developers/welcome-to-new-committers.html
maven/website/content/docs/2.0.1/release-notes.html
maven/website/content/docs/2.0.10/release-notes.html
maven/website/content/docs/2.0.11/release-notes.html
maven/website/content/docs/2.0.2/release-notes.html
maven/website/content/docs/2.0.3/release-notes.html
maven/website/content/docs/2.0.4/release-notes.html
maven/website/content/docs/2.0.5/release-notes.html
maven/website/content/docs/2.0.6/release-notes.html
maven/website/content/docs/2.0.7/release-notes.html
maven/website/content/docs/2.0.8/release-notes.html
maven/website/content/docs/2.0.9/release-notes.html
maven/website/content/docs/2.0/release-notes.html
maven/website/content/docs/2.1.0/release-notes.html
maven/website/content/docs/2.2.0/release-notes.html
maven/website/content/docs/2.2.1/release-notes.html
maven/website/content/docs/3.0-alpha-3/release-notes.html
maven/website/content/docs/3.0-alpha-4/release-notes.html
maven/website/content/docs/3.0-alpha-5/release-notes.html
maven/website/content/docs/3.0-alpha-6/release-notes.html
maven/website/content/docs/3.0-alpha-7/release-notes.html
maven/website/content/docs/3.0-beta-1/release-notes.html
maven/website/content/docs/3.0-beta-2/release-notes.html
maven/website/content/docs/3.0-beta-3/release-notes.html
maven/website/content/docs/3.0.1/release-notes.html
maven/website/content/docs/3.0.2/release-notes.html
maven/website/content/docs/3.0.3/release-notes.html
maven/website/content/docs/3.0.4/release-notes.html
maven/website/content/docs/3.0.5/release-notes.html
maven/website/content/docs/3.0/release-notes.html
maven/website/content/docs/3.1.0-alpha-1/release-notes.html
maven/website/content/docs/3.1.0/release-notes.html
maven/website/content/docs/3.1.1/release-notes.html
maven/website/content/docs/3.2.1/release-notes.html
maven/website/content/docs/3.2.2/release-notes.html
maven/website/content/docs/3.2.3/release-notes.html
maven/website/content/docs/3.2.5/release-notes.html
maven/website/content/docs/3.3.1/release-notes.html
maven/website/content/docs/3.3.3/release-notes.html
maven/website/content/docs/3.3.9/release-notes.html
maven/website/content/docs/3.5.0-alpha-1/release-notes.html
maven/website/content/docs/3.5.0-beta-1/release-notes.html
maven/website/content/docs/3.5.0/release-notes.html
maven/website/content/docs/3.5.2/release-notes.html
maven/website/content/docs/3.5.3/release-notes.html
maven/website/content/docs/3.5.4/release-notes.html
maven/website/content/docs/3.6.0/release-notes.html
maven/website/content/docs/3.6.1/release-notes.html
maven/website/content/docs/3.6.2/release-notes.html
maven/website/content/docs/3.6.3/release-notes.html
maven/website/content/docs/3.8.1/release-notes.html
maven/website/content/docs/3.8.2/release-notes.html
maven/website/content/docs/3.8.3/release-notes.html
maven/website/content/docs/3.8.4/release-notes.html
maven/website/content/docs/history.html
maven/website/content/download.html
maven/website/content/errors/404.html
maven/website/content/examples/index.html
maven/website/content/examples/injecting-properties-via-settings.html
maven/website/content/examples/maven-3-lifecycle-extensions.html
maven/website/content/extensions/index.html
maven/website/content/faq-unoffical.html
maven/website/content/general.html
maven/website/content/glossary.html
maven/website/content/guides/development/guide-building-maven.html
maven/website/content/guides/development/guide-committer-school.html
maven/website/content/guides/development/guide-documentation-style.html
maven/website/content/guides/development/guide-helping.html
maven/website/content/guides/development/guide-maven-development.html
maven/website/content/guides/development/guide-plugin-documentation.html
maven/website/content/guides/development/guide-testing-development-plugins.html
maven/website/content/guides/development/guide-testing-releases.html
maven/website/content/guides/getting-started/index.html
maven/website/content/guides/getting-started/maven-in-five-minutes.html
maven/website/content/guides/getting-started/windows-prerequisites.html
maven/website/content/guides/index.html
maven/website/content/guides/introduction/introduction-to-archetypes.html
maven/website/content/guides/introduction/introduction-to-dependency-mechanism.html
maven/website/content/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
maven/website/content/guides/introduction/introduction-to-plugin-prefix-mapping.html
maven/website/content/guides/introduction/introduction-to-plugins.html
maven/website/content/guides/introduction/introduction-to-profiles.html
maven/website/content/guides/introduction/introduction-to-repositories.html
maven/website/content/guides/introduction/introduction-to-the-lifecycle.html
maven/website/content/guides/introduction/introduction-to-the-pom.html
maven/website/content/guides/introduction/introduction-to-the-standard-directory-layout.html
maven/website/content/guides/mini/guide-3rd-party-jars-local.html
maven/website/content/guides/mini/guide-3rd-party-jars-remote.html
maven/website/content/guides/mini/guide-archive-configuration.html
maven/website/content/guides/mini/guide-assemblies.html
maven/website/content/guides/mini/guide-attached-tests.html
maven/website/content/guides/mini/guide-bash-m2-completion.html
maven/website/content/guides/mini/guide-building-for-different-environments.html
maven/website/content/guides/mini/guide-configuring-maven.html
maven/website/content/guides/mini/guide-configuring-plugins.html
maven/website/content/guides/mini/guide-creating-archetypes.html
maven/website/content/guides/mini/guide-default-execution-ids.html
maven/website/content/guides/mini/guide-deployment-security-settings.html
maven/website/content/guides/mini/guide-encryption.html
maven/website/content/guides/mini/guide-generating-sources.html
maven/website/content/guides/mini/guide-http-settings.html
maven/website/content/guides/mini/guide-large-scale-centralized-deployments.html
maven/website/content/guides/mini/guide-manifest.html
maven/website/content/guides/mini/guide-maven-classloading.html
maven/website/content/guides/mini/guide-mirror-settings.html
maven/website/content/guides/mini/guide-multiple-modules-4.html
maven/website/content/guides/mini/guide-multiple-modules.html
maven/website/content/guides/mini/guide-multiple-repositories.html
maven/website/content/guides/mini/guide-naming-conventions.html
maven/website/content/guides/mini/guide-new-committers.html
maven/website/content/guides/mini/guide-proxies.html
maven/website/content/guides/mini/guide-releasing.html
maven/website/content/guides/mini/guide-relocation.html
maven/website/content/guides/mini/guide-repository-ssl.html
maven/website/content/guides/mini/guide-reproducible-builds.html
maven/website/content/guides/mini/guide-site.html
maven/website/content/guides/mini/guide-snippet-macro.html
maven/website/content/guides/mini/guide-using-ant.html
maven/website/content/guides/mini/guide-using-extensions.html
maven/website/content/guides/mini/guide-using-modello.html
maven/website/content/guides/mini/guide-using-one-source-directory.html
maven/website/content/guides/mini/guide-using-toolchains.html
maven/website/content/guides/mini/guide-wagon-providers.html
maven/website/content/guides/mini/index.html
maven/website/content/guides/plugin/guide-java-plugin-development.html
maven/website/content/guides/plugin/guide-java-report-plugin-development.html
maven/website/content/ide.html
maven/website/content/index.html
maven/website/content/install.html
maven/website/content/issue-management.html
maven/website/content/mailing-lists.html
maven/website/content/maven-1.x-eol.html
maven/website/content/maven-2.x-eol.html
maven/website/content/maven-ci-friendly.html
maven/website/content/maven-conventions.html
maven/website/content/maven-features.html
maven/website/content/maven-jsr330.html
maven/website/content/maven-logging.html
maven/website/content/maven-site-1.0-site.jar
maven/website/content/plugin-developers/common-bugs.html
maven/website/content/plugin-developers/cookbook/add-build-time-to-manifest.html
maven/website/content/plugin-developers/cookbook/add-svn-revision-to-manifest.html
maven/website/content/plugin-developers/cookbook/attach-source-javadoc-artifacts.html
maven/website/content/plugin-developers/cookbook/generate-assembly.html
maven/website/content/plugin-developers/cookbook/index.html
maven/website/content/plugin-developers/cookbook/plexus-plugin-upgrade.html
maven/website/content/plugin-developers/index.html
maven/website/content/plugin-developers/plugin-documenting.html
maven/website/content/plugin-developers/plugin-testing.html
maven/website/content/plugins/index.html
maven/website/content/plugins/localization.html
maven/website/content/pom.html
maven/website/content/pom/index.html
maven/website/content/privacy-policy.html
maven/website/content/project-faq.html
maven/website/content/project-info.html
maven/website/content/project-roles.html
maven/website/content/reference/maven-classloading.html
maven/website/content/release-notes-all.html
maven/website/content/repository-management.html
maven/website/content/repository/central-index.html
maven/website/content/repository/central-metadata.html
maven/website/content/repository/guide-central-repository-upload.html
maven/website/content/repository/index.html
maven/website/content/resource/branding/actioncards.html
maven/website/content/run-maven/index.html
maven/website/content/run.html
maven/website/content/scm.html
maven/website/content/security-plexus-archiver.html
maven/website/content/security.html
maven/website/content/settings.html
maven/website/content/shared/index.html
maven/website/content/skins/index.html
maven/website/content/support-and-training.html
maven/website/content/team.html
maven/website/content/testimonials.html
maven/website/content/users/getting-help.html
maven/website/content/users/index.html
maven/website/content/what-is-maven.html
maven/website/content/xsd/settings-1.2.0.xsd
Modified: maven/website/content/about.html
==============================================================================
--- maven/website/content/about.html (original)
+++ maven/website/content/about.html Thu Dec 2 20:29:27 2021
@@ -1,18 +1,18 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/fml/about.fml at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/fml/about.fml at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<title>Maven – About Maven</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="./js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
Modified: maven/website/content/aether.html
==============================================================================
--- maven/website/content/aether.html (original)
+++ maven/website/content/aether.html Thu Dec 2 20:29:27 2021
@@ -1,18 +1,18 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/markdown/aether.md at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/markdown/aether.md at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<title>Maven – Aether import plan to Maven</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="./js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
@@ -141,7 +141,8 @@ under the License.
-->
<section>
<h2><a name="IP_Clearance"></a>IP Clearance</h2>
-<p>Tracked on <a class="externalLink" href="http://incubator.apache.org/ip-clearance/maven-aether.html">Incubator IP Clearance</a> and through <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6007">MNG-6007</a>.</p></section><section>
+<p>Tracked on <a class="externalLink" href="http://incubator.apache.org/ip-clearance/maven-aether.html">Incubator IP Clearance</a>
+and through <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6007">MNG-6007</a>.</p></section><section>
<h2><a name="Code_integration"></a>Code integration</h2>
<table border="0" class="table table-striped">
<thead>
@@ -153,59 +154,59 @@ under the License.
</thead><tbody>
<tr class="b">
-<td><b>Name</b></td>
+<td align="left"><b>Name</b></td>
<td>Aether</td>
<td>Maven Artifact Resolver</td></tr>
<tr class="a">
-<td><b>Name</b></td>
+<td align="left"><b>Name</b></td>
<td><a class="externalLink" href="https://projects.eclipse.org/projects/technology.aether">https://projects.eclipse.org/projects/technology.aether</a></td>
<td><a class="externalLink" href="https://maven.apache.org/resolver/">https://maven.apache.org/resolver/</a><br /><a class="externalLink" href="https://maven.apache.org/resolver-archives/">https://maven.apache.org/resolver-archives/</a></td></tr>
<tr class="b">
-<td><b>SCM repo</b></td>
+<td align="left"><b>SCM repo</b></td>
<td><a class="externalLink" href="http://git.eclipse.org/c/aether/aether-core.git/aether.html">aether-core.git</a><br /><a class="externalLink" href="http://git.eclipse.org/c/aether/aether-ant.git/aether.html">aether-ant.git</a><br /><a class="externalLink" href="http://git.eclipse.org/c/aether/aether-demo.git/aether.html">aether-demo.git</a></td>
<td><a class="externalLink" href="https://gitbox.apache.org/repos/asf?p=maven-resolver.git">https://gitbox.apache.org/repos/asf?p=maven-resolver.git</a><br />(<a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-6008">MNG-6008</a>)<br />one unique git repo with 3 independant <b>master</b>, <b>ant-tasks</b> and <b>demo</b> branches</td></tr>
<tr class="a">
-<td><b>central groupId</b></td>
+<td align="left"><b>central groupId</b></td>
<td><a class="externalLink" href="https://repo.maven.apache.org/maven2/org/eclipse/aether/">org.eclipse.aether</a></td>
<td><a class="externalLink" href="https://repo.maven.apache.org/maven2/org/apache/maven/resolver/">org.apache.maven.resolver</a></td></tr>
<tr class="b">
-<td><b>artifactIds</b></td>
+<td align="left"><b>artifactIds</b></td>
<td>aether<br />aether-api<br />aether-impl<br />aether-spi<br />aether-util<br />aether-transport-*</td>
<td>maven-resolver<br />maven-resolver-api<br />maven-resolver-impl<br />maven-resolver-spi<br />maven-resolver-util<br />maven-resolver-transport-*</td></tr>
<tr class="a">
-<td><b>OSGi Bundles</b></td>
+<td align="left"><b>OSGi Bundles</b></td>
<td>org.eclipse.aether.api<br />org.eclipse.aether.impl<br />org.eclipse.aether….</td>
<td>no OSGi bundles in Apache Maven</td></tr>
<tr class="b">
-<td><b>P2 repo</b></td>
+<td align="left"><b>P2 repo</b></td>
<td><a class="externalLink" href="http://download.eclipse.org/aether/aether-core/releases/">http://download.eclipse.org/aether/aether-core/releases/</a><br /><a class="externalLink" href="http://download.eclipse.org/aether/maven-aether-provider/releases/">http://download.eclipse.org/aether/maven-aether-provider/releases/</a></td>
<td>no P2 repo</td></tr>
<tr class="a">
-<td><b>API java packages</b></td>
+<td align="left"><b>API java packages</b></td>
<td>org.eclipse.aether…</td>
<td><b>Keep packages in Maven 3.x to maintain compatibility for some plugins or extensions using Aether API.</b></td></tr>
<tr class="b">
-<td><b>Impl java packages</b></td>
+<td align="left"><b>Impl java packages</b></td>
<td>org.eclipse.aether.impl.*<br />org.eclipse.aether.internal.*</td>
<td>Same as API, even if nobody should rely on impl…</td></tr>
<tr class="a">
-<td><b>SPI java packages</b></td>
+<td align="left"><b>SPI java packages</b></td>
<td>org.eclipse.aether.spi.*</td>
<td>Same as API (is it really used outside?)</td></tr>
<tr class="b">
-<td><b>Util java packages</b></td>
+<td align="left"><b>Util java packages</b></td>
<td>org.eclipse.aether.util.*</td>
<td>Same as API (is it really used outside?)</td></tr>
<tr class="a">
-<td><b>Transport java packages</b></td>
+<td align="left"><b>Transport java packages</b></td>
<td>org.eclipse.aether.transport.*</td>
<td>Same as API (is it really used outside?)</td></tr>
<tr class="b">
-<td><b>Ant Tasks</b></td>
+<td align="left"><b>Ant Tasks</b></td>
<td>Aether Ant Tasks</td>
<td>Maven Artifact Resolver Ant Tasks</td></tr>
<tr class="a">
-<td><b>Maven Provider (in core)</b></td>
+<td align="left"><b>Maven Provider (in core)</b></td>
<td><a class="externalLink" href="http://maven.apache.org/ref/3.3.9/maven-aether-provider/">Maven Aether Provider</a></td>
<td><a class="externalLink" href="https://maven.apache.org/ref/3.6.1/maven-resolver-provider/">Maven Resolver Provider</a></td></tr>
</tbody>
@@ -220,31 +221,31 @@ under the License.
</thead><tbody>
<tr class="b">
-<td>Sonatype Aether 1.2</td>
+<td align="left">Sonatype Aether 1.2</td>
<td>2010-09-02 <a class="externalLink" href="https://repo.maven.apache.org/maven2/org/apache/maven/maven-aether-provider/3.0-beta-3/">3.0-beta-3</a></td></tr>
<tr class="a">
-<td>Sonatype Aether 1.7</td>
+<td align="left">Sonatype Aether 1.7</td>
<td>2010-10-08 <a class="externalLink" href="http://maven.apache.org/ref/3.0/apache-maven/dependencies.html">3.0</a></td></tr>
<tr class="b">
-<td>Sonatype Aether 1.8</td>
+<td align="left">Sonatype Aether 1.8</td>
<td>2010-11-26 <a class="externalLink" href="http://maven.apache.org/ref/3.0.1/apache-maven/dependencies.html">3.0.1</a></td></tr>
<tr class="a">
-<td>Sonatype Aether 1.9</td>
+<td align="left">Sonatype Aether 1.9</td>
<td>2011-01-12 <a class="externalLink" href="http://maven.apache.org/ref/3.0.2/apache-maven/dependencies.html">3.0.2</a>]</td></tr>
<tr class="b">
-<td>Sonatype Aether 1.11</td>
+<td align="left">Sonatype Aether 1.11</td>
<td>2011-03-04 <a class="externalLink" href="http://maven.apache.org/ref/3.0.3/apache-maven/dependencies.html">3.0.3</a>]</td></tr>
<tr class="a">
-<td>Sonatype Aether 1.13.1</td>
+<td align="left">Sonatype Aether 1.13.1</td>
<td>2012-01-20 <a class="externalLink" href="http://maven.apache.org/ref/3.0.4/apache-maven/dependencies.html">3.0.4</a><br />2013-02-23 <a class="externalLink" href="http://maven.apache.org/ref/3.0.5/apache-maven/dependencies.html">3.0.5</a></td></tr>
<tr class="b">
-<td>Eclipse Aether 0.9.0.M2</td>
+<td align="left">Eclipse Aether 0.9.0.M2</td>
<td>2013-07-15 <a class="externalLink" href="http://maven.apache.org/ref/3.1.0/apache-maven/dependencies.html">3.1.0</a><br />2013-10-04 <a class="externalLink" href="http://maven.apache.org/ref/3.1.1/apache-maven/dependencies.html">3.1.1</a><br />2014-02-21 <a class="externalLink" href="http://maven.apache.org/ref/3.2.1/apache-maven/dependencies.html">3.2.1</a><br />2014-06-26 <a class="externalLink" href="http://maven.apache.org/ref/3.2.2/apache-maven/dependencies.html">3.2.2</a><br />2014-08-17 <a class="externalLink" href="http://maven.apache.org/ref/3.2.3/apache-maven/dependencies.html">3.2.3</a></td></tr>
<tr class="a">
-<td>Eclipse Aether 1.0.0.v20140518</td>
+<td align="left">Eclipse Aether 1.0.0.v20140518</td>
<td>2014-12-20 <a class="externalLink" href="http://maven.apache.org/ref/3.2.5/apache-maven/dependencies.html">3.2.5</a></td></tr>
<tr class="b">
-<td>Eclipse Aether 1.0.2.v20150114</td>
+<td align="left">Eclipse Aether 1.0.2.v20150114</td>
<td>2015-03-18 <a class="externalLink" href="http://maven.apache.org/ref/3.3.1/apache-maven/dependencies.html">3.3.1</a><br />2015-04-28 <a class="externalLink" href="http://maven.apache.org/ref/3.3.3/apache-maven/dependencies.html">3.3.3</a><br />2015-11-14 <a class="externalLink" href="http://maven.apache.org/ref/3.3.9/apache-maven/dependencies.html">3.3.9</a></td></tr>
</tbody>
</table></section>
Added: maven/website/content/apache-maven.pdf
==============================================================================
Binary file - no diff available.
Propchange: maven/website/content/apache-maven.pdf
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: maven/website/content/apache-resource-bundles/index.html
==============================================================================
--- maven/website/content/apache-resource-bundles/index.html (original)
+++ maven/website/content/apache-resource-bundles/index.html Thu Dec 2 20:29:27 2021
@@ -1,19 +1,19 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/xdoc/apache-resource-bundles/index.xml at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/xdoc/apache-resource-bundles/index.xml at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<meta name="author" content="Olivier Lamy" />
<title>Maven – Apache Resource Bundles</title>
- <link rel="stylesheet" href="../css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="../css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
- <script src="../js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="../js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
Modified: maven/website/content/archives/maven-2.x/index.html
==============================================================================
--- maven/website/content/archives/maven-2.x/index.html (original)
+++ maven/website/content/archives/maven-2.x/index.html Thu Dec 2 20:29:27 2021
@@ -1,20 +1,20 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/apt/archives/maven-2.x/index.apt at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/apt/archives/maven-2.x/index.apt at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<meta name="author" content="Karl-Heinz Marbaise" />
<meta name="date" content="2014-03-22" />
<title>Maven – Maven 2 Graveyard</title>
- <link rel="stylesheet" href="../../css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="../../css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="../../css/site.css" />
<link rel="stylesheet" href="../../css/print.css" media="print" />
- <script src="../../js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="../../js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
Modified: maven/website/content/archives/maven-2.x/maven-2.1-architectural-goals.html
==============================================================================
--- maven/website/content/archives/maven-2.x/maven-2.1-architectural-goals.html (original)
+++ maven/website/content/archives/maven-2.x/maven-2.1-architectural-goals.html Thu Dec 2 20:29:27 2021
@@ -1,18 +1,18 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/apt/archives/maven-2.x/maven-2.1-architectural-goals.apt at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/apt/archives/maven-2.x/maven-2.1-architectural-goals.apt at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<title>Maven – </title>
- <link rel="stylesheet" href="../../css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="../../css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="../../css/site.css" />
<link rel="stylesheet" href="../../css/print.css" media="print" />
- <script src="../../js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="../../js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
Modified: maven/website/content/articles.html
==============================================================================
--- maven/website/content/articles.html (original)
+++ maven/website/content/articles.html Thu Dec 2 20:29:27 2021
@@ -1,20 +1,20 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/xdoc/articles.xml at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/xdoc/articles.xml at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<meta name="author" content="Brett Porter" />
<meta name="author" content="Vincent Massol" />
<title>Maven – External Resources on Maven</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="./js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
@@ -227,7 +227,7 @@
<tr class="b">
-<td><a class="externalLink" href="https://maarten.mulders.it/2021/03/introduction-to-maven-toolchains/">Introduction to Maven Toolchains</a></td>
+<td align="left"><a class="externalLink" href="https://maarten.mulders.it/2021/03/introduction-to-maven-toolchains/">Introduction to Maven Toolchains</a></td>
<td></td>
@@ -238,7 +238,7 @@
<tr class="a">
-<td><a class="externalLink" href="https://maarten.mulders.it/2020/01/customise-the-maven-release-process/">Customise the Maven Release process</a></td>
+<td align="left"><a class="externalLink" href="https://maarten.mulders.it/2020/01/customise-the-maven-release-process/">Customise the Maven Release process</a></td>
<td></td>
@@ -249,7 +249,7 @@
<tr class="b">
-<td><a class="externalLink" href="http://www.sonatype.com/people/2009/08/create-a-customized-build-process-in-maven/">Create a Customized Build Process in Maven</a></td>
+<td align="left"><a class="externalLink" href="http://www.sonatype.com/people/2009/08/create-a-customized-build-process-in-maven/">Create a Customized Build Process in Maven</a></td>
<td></td>
@@ -260,7 +260,7 @@
<tr class="a">
-<td><a class="externalLink" href="http://www.manuelrecena.com/docs/maven_090625.pdf">Maven: mas que una herramienta de construccion (in Spanish)</a></td>
+<td align="left"><a class="externalLink" href="http://www.manuelrecena.com/docs/maven_090625.pdf">Maven: mas que una herramienta de construccion (in Spanish)</a></td>
<td></td>
@@ -271,7 +271,7 @@
<tr class="b">
-<td><a class="externalLink" href="http://www.theserverside.com/tt/articles/article.tss?l=Introductiontom2eclipse">Introduction to m2eclipse</a></td>
+<td align="left"><a class="externalLink" href="http://www.theserverside.com/tt/articles/article.tss?l=Introductiontom2eclipse">Introduction to m2eclipse</a></td>
<td>TheServerSide</td>
@@ -282,7 +282,7 @@
<tr class="a">
-<td><a class="externalLink" href="http://msaitozen.googlepages.com/maven2.x_dokuman.pdf">Maven 2.x (in Turkish)</a></td>
+<td align="left"><a class="externalLink" href="http://msaitozen.googlepages.com/maven2.x_dokuman.pdf">Maven 2.x (in Turkish)</a></td>
<td>Anadolu Üniversitesi</td>
@@ -293,7 +293,7 @@
<tr class="b">
-<td><a class="externalLink" href="http://www.theserverside.com/tt/articles/article.tss?l=SettingUpMavenRepository">Setting up the Internal Repository</a></td>
+<td align="left"><a class="externalLink" href="http://www.theserverside.com/tt/articles/article.tss?l=SettingUpMavenRepository">Setting up the Internal Repository</a></td>
<td>The Server Side</td>
@@ -304,7 +304,7 @@
<tr class="a">
-<td><a class="externalLink" href="http://www.manuelrecena.com/docs/maven_061106.pdf">Maven - Menos mal que has venido (in Spanish)</a></td>
+<td align="left"><a class="externalLink" href="http://www.manuelrecena.com/docs/maven_061106.pdf">Maven - Menos mal que has venido (in Spanish)</a></td>
<td>Universidad de Sevilla</td>
@@ -315,7 +315,7 @@
<tr class="b">
-<td><a class="externalLink" href="http://java.developpez.com/faq/maven/">FAQ for Maven and Continuum (in French)</a></td>
+<td align="left"><a class="externalLink" href="http://java.developpez.com/faq/maven/">FAQ for Maven and Continuum (in French)</a></td>
<td>Developpez.com</td>
@@ -326,7 +326,7 @@
<tr class="a">
-<td><a class="externalLink" href="http://www.javaposse.com/index.php?post_id=112128">Java Posse #070 - Interview with Brett Porter of Maven</a></td>
+<td align="left"><a class="externalLink" href="http://www.javaposse.com/index.php?post_id=112128">Java Posse #070 - Interview with Brett Porter of Maven</a></td>
<td>Java Posse</td>
@@ -337,7 +337,7 @@
<tr class="b">
-<td><a class="externalLink" href="https://www.javaworld.com/javaworld/jw-05-2006/jw-0529-maven.html">The Maven 2 POM demystified</a></td>
+<td align="left"><a class="externalLink" href="https://www.javaworld.com/javaworld/jw-05-2006/jw-0529-maven.html">The Maven 2 POM demystified</a></td>
<td>JavaWorld</td>
@@ -348,7 +348,7 @@
<tr class="a">
-<td><a class="externalLink" href="https://www.drdobbs.com/architecture-and-design/maven-building-complex-systems/186100398">Maven: Building Complex Systems</a></td>
+<td align="left"><a class="externalLink" href="https://www.drdobbs.com/architecture-and-design/maven-building-complex-systems/186100398">Maven: Building Complex Systems</a></td>
<td>Dr.Dobb's</td>
@@ -359,7 +359,7 @@
<tr class="b">
-<td><a class="externalLink" href="https://www.javaworld.com/javaworld/jw-02-2006/jw-0227-maven.html">Get the most out of Maven site generation</a></td>
+<td align="left"><a class="externalLink" href="https://www.javaworld.com/javaworld/jw-02-2006/jw-0227-maven.html">Get the most out of Maven site generation</a></td>
<td>JavaWorld</td>
@@ -370,7 +370,7 @@
<tr class="a">
-<td><a class="externalLink" href="https://www.javaworld.com/javaworld/jw-12-2005/jw-1205-maven.html?lsrc=maven-users">An introduction to Maven 2</a></td>
+<td align="left"><a class="externalLink" href="https://www.javaworld.com/javaworld/jw-12-2005/jw-1205-maven.html?lsrc=maven-users">An introduction to Maven 2</a></td>
<td>JavaWorld</td>
@@ -381,7 +381,7 @@
<tr class="b">
-<td><a class="externalLink" href="https://web.archive.org/web/20051228123436/http://www.onjava.com/pub/a/onjava/2005/09/07/maven.html">Building J2EE Projects with Maven</a></td>
+<td align="left"><a class="externalLink" href="https://web.archive.org/web/20051228123436/http://www.onjava.com/pub/a/onjava/2005/09/07/maven.html">Building J2EE Projects with Maven</a></td>
<td>OnJava</td>
@@ -392,7 +392,7 @@
<tr class="a">
-<td><a class="externalLink" href="https://web.archive.org/web/20041217085616/http://www.oracle.com/technology/pub/articles/masterj2ee/j2ee_wk2.html">Master and Commander by Julien Dubois</a></td>
+<td align="left"><a class="externalLink" href="https://web.archive.org/web/20041217085616/http://www.oracle.com/technology/pub/articles/masterj2ee/j2ee_wk2.html">Master and Commander by Julien Dubois</a></td>
<td>Oracle</td>
@@ -403,7 +403,7 @@
<tr class="b">
-<td><a class="externalLink" href="http://www.internetnews.com/dev-news/article.php/3381841">Apache's Maven Comes of Age</a> (Coverage of the release of Maven 1.0)</td>
+<td align="left"><a class="externalLink" href="http://www.internetnews.com/dev-news/article.php/3381841">Apache's Maven Comes of Age</a> (Coverage of the release of Maven 1.0)</td>
<td>internetnews.com</td>
Modified: maven/website/content/background/history-of-maven.html
==============================================================================
--- maven/website/content/background/history-of-maven.html (original)
+++ maven/website/content/background/history-of-maven.html Thu Dec 2 20:29:27 2021
@@ -1,18 +1,18 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/markdown/background/history-of-maven.md at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/markdown/background/history-of-maven.md at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<title>Maven – History of Maven</title>
- <link rel="stylesheet" href="../css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="../css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
- <script src="../js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="../js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
@@ -146,23 +146,75 @@ under the License.
-->
<section>
<h2><a name="History_of_Maven_by_Jason_van_Zyl"></a>History of Maven by Jason van Zyl</h2>
-<p>Maven began its life in the <a class="externalLink" href="http://jakarta.apache.org">Jakarta</a> <a class="externalLink" href="http://jakarta.apache.org/alexandria/legacy/">Alexandria</a> project. The Alexandria project is now defunct but was the breeding ground for not only Maven, but for the <a class="externalLink" href="http://gump.apache.org">Gump</a> and <a class="externalLink" href="http://forrest.apache.org">Forrest</a> projects as well. The first import of prototype sources happened in <a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/jakarta-alexandria-dev/200108.mbox/%3c20010827163505.53005.qmail@icarus.apache.org%3e">August 2001</a>. As of the date of this document (October 2005) Maven was <a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/jakarta-alexandria-dev/200202.mbox/%3c20020202153719.50163.qmail@icarus.apache.org%3e">removed</a> from Alexandria about 3 years, 7 months ago making Maven about 4 years old! Maven spent about
5 months as part of the Alexandria before moving on to its next home in the <a class="externalLink" href="http://turbine.apache.org/">Turbine</a> project.</p>
-<p>Though Maven started in Alexandria the test bed for its use was the Turbine project. Turbine was in the process of decoupling its persistence layer, services layer and web layer into separate builds and I got very tired of having to maintain several different builds which were essentially the same. There was no way to easy template Ant builds in those days and every ant build appeared to be different and I found this incredibly frustrating and futile. I figured who really cares how the build works so long as it works and is easy to use. The infrastructure of a project is incredibly important but the value of a project lies in the application being developed. As such the build is generally neglected and tends to fall apart when you need it to work most like when you need to prepare a release or when more then a couple of people are working on the project. In Jakarta land four years ago it was rare that a Ant build worked out of the box. Mind you many Turbine developers suffered as
I tried to get Maven working which is something I regret, but I figure how do new projects start and survive if someone doesn’t suffer. I figured it was for their own good (I’ve been known to have an opinion or two) and after much gnashing of teeth I think Maven has finally come of age. It reminds me of one of my favourite quotes from Ralph Johnson and Don Roberts in Patterns for Evolving Frameworks:</p>
+<p>Maven began its life in the <a class="externalLink" href="http://jakarta.apache.org">Jakarta</a> <a class="externalLink" href="http://jakarta.apache.org/alexandria/legacy/">Alexandria</a> project. The Alexandria project is now defunct but was the breeding ground for not only Maven, but for the <a class="externalLink" href="http://gump.apache.org">Gump</a> and <a class="externalLink" href="http://forrest.apache.org">Forrest</a> projects as well. The first import of prototype sources happened in
+<a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/jakarta-alexandria-dev/200108.mbox/%3c20010827163505.53005.qmail@icarus.apache.org%3e">August 2001</a>. As of the date of this document (October 2005) Maven was <a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/jakarta-alexandria-dev/200202.mbox/%3c20020202153719.50163.qmail@icarus.apache.org%3e">removed</a> from Alexandria about 3 years, 7 months ago making Maven about 4 years old! Maven spent about 5 months as part of the Alexandria before moving on to its next home in the <a class="externalLink" href="http://turbine.apache.org/">Turbine</a> project.</p>
+<p>Though Maven started in Alexandria the test bed for its use was the Turbine project. Turbine was in the process of
+decoupling its persistence layer, services layer and web layer into separate builds and I got very tired of having
+to maintain several different builds which were essentially the same. There was no way to easy template Ant builds
+in those days and every ant build appeared to be different and I found this incredibly frustrating and futile. I figured
+who really cares how the build works so long as it works and is easy to use. The infrastructure of a project is
+incredibly important but the value of a project lies in the application being developed. As such the build is
+generally neglected and tends to fall apart when you need it to work most like when you need to prepare a release or when
+more then a couple of people are working on the project. In Jakarta land four years ago it was rare that a Ant build
+worked out of the box. Mind you many Turbine developers suffered as I tried to get Maven working which is something I regret,
+but I figure how do new projects start and survive if someone doesn't suffer. I figured it was for their own good
+(I've been known to have an opinion or two) and after much gnashing of teeth I think Maven has finally come of age.
+It reminds me of one of my favourite quotes from Ralph Johnson and Don Roberts in Patterns for Evolving Frameworks:</p>
<blockquote>
-<p>People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a reusable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be.</p>
+<p>People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction
+on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a
+reusable design, so you develop it by looking at the things it is supposed to be a design of. The more examples
+you look at, the more general your framework will be.</p>
</blockquote>
-<p>I didn’t really know what the final result would look like I just knew there had to be a better way. But to start with I know I wanted:</p>
+<p>I didn't really know what the final result would look like I just knew there had to be a better way.
+But to start with I know I wanted:</p>
<ul>
<li>A model for a project so you could look in one place for everything that pertained to the project</li>
-<li>A standard directory structure so you didn’t have to go fishing around for libraries, sources and documentation</li>
+<li>A standard directory structure so you didn't have to go fishing around for libraries, sources and documentation</li>
</ul>
-<p>So started using a model with a simple XML representation and picked what I thought were some decent standards for a directory structure and that’s how it started. I was still using Ant under the covers but I had some standard targets that could be used in each of the Turbine builds and that made me happy.</p>
-<p>As noted above one of the projects in Alexandria at the time was Gump. Sam Ruby tried to convince me that using the Gump model would be a good idea so I took a look. After taking a look at the descriptors I noted that Gump pretty much allowed any project to do whatever it wanted in terms of directory structure, use of JARs in CVS, multiple artifacts per project, documentation splayed everywhere, and several other things that made no sense to me as Gump was not trying to standardize anything at the time but trying to continuously integrate anything it could get its hands on. My goals were different and I wanted to make an <a class="externalLink" href="http://www.oreillynet.com/pub/a/network/2005/08/30/ruby-rails-david-heinemeier-hansson.html">opinionated</a> piece of software and I preferred the notion of convention over configuration. I wanted a project’s infrastructure to look the same and work the same so I continued to pursue my own model for a project and decided to di
sagree with Gump’s particular tact at project modeling which I thought was too flexible. I wanted to save people time by being able to find things in the same place. Again the value in a project is the final result: how it is constructed and built predictable and easy. I fully admit some warts in Maven 1.x sometimes made things harder but that is par for the course with first generation tools.</p>
-<p>The next thing I noticed were all the JARs that we were depending on were stored in CVS. We had many copies of Xerces laying around which is a waste of space, every time the version of Xerces changed I had to update the copies of Xerces in each of the projects, but more importantly without some declarative statement of your dependencies there is no way you could perform any analysis. People tend to miss the point entirely regarding a declarative dependency use. People say it’s so easy just to store their dependencies in an SCM but try decomposing your big crappy build into components to encourage reuse and ease of maintenance, or try to analyze what you might need at runtime between all your different apps with commons dependencies in the graph and you’re shit out of luck. The true power of declarative dependencies lies not in the fact that you can save a few bytes of disk space, though it can really add up if you’re not careful, but in the analysis that can
be performed. Once you have a decent graph all sorts of things are possible. Back to history: so now that declarative dependencies existed it needed to be easier …</p>
-<p>This is when I decided to employ standard Java-like inheritance in the model used and find a way to create a repository for things you need to build. So I hacked in some inheritance goop and now it was time for the repository. I asked around Apache to see if it would be possible to host a repository and soon found out that it was not possible to host non-Apache-like artifacts. So LGPL and GPL artifacts were out which didn’t really make for a useful repository. After a little hunting I found <a class="externalLink" href="http://www.ibiblio.org">Ibiblio</a> which is a vast archive of all sorts of neat stuff including tons of free software. One of the mandates of Ibiblio is to aid in the dispersal of free software. Sounded perfect to me so I got in contact with John Reuning at Ibiblio and the rest is history. Working with the folks at Ibiblio has been a pleasure, the admins there are an amazingly helpful and talented bunch. They let us store whatever free software we want, pr
ovide great stats, and will let us host any software we want. Ibiblio is very cool.</p>
-<p>Many people had some problems with Maven 1.x but it generally worked and all tools in their first generation suffer from many short comings and the only way to overcome that is to forge ahead and try to create something better the next time around. With all the feed back the Maven developers have received from 1.x users and during the betas of 2.0 we think we’ve finally got something to build on. The first version of Maven was written by myself with lots of help from Bob McWhirter</p></section>
+<p>So started using a model with a simple XML representation and picked what I thought were some decent standards for
+a directory structure and that's how it started. I was still using Ant under the covers but I had some standard targets
+that could be used in each of the Turbine builds and that made me happy.</p>
+<p>As noted above one of the projects in Alexandria at the time was Gump. Sam Ruby tried to convince me that using
+the Gump model would be a good idea so I took a look. After taking a look at the descriptors I noted that Gump
+pretty much allowed any project to do whatever it wanted in terms of directory structure, use of JARs in CVS,
+multiple artifacts per project, documentation splayed everywhere, and several other things that made no sense to me
+as Gump was not trying to standardize anything at the time but trying to continuously integrate anything it could
+get its hands on. My goals were different and I wanted to make an
+<a class="externalLink" href="http://www.oreillynet.com/pub/a/network/2005/08/30/ruby-rails-david-heinemeier-hansson.html">opinionated</a> piece of software and I preferred the notion of convention over configuration. I wanted a project's infrastructure to
+look the same and work the same so I continued to pursue my own model for a project and decided to disagree with
+Gump's particular tact at project modeling which I thought was too flexible. I wanted to save people time by being
+able to find things in the same place. Again the value in a project is the final result: how it is constructed
+and built predictable and easy. I fully admit some warts in Maven 1.x sometimes made things harder but that is
+par for the course with first generation tools.</p>
+<p>The next thing I noticed were all the JARs that we were depending on were stored in CVS. We had many copies
+of Xerces laying around which is a waste of space, every time the version of Xerces changed
+I had to update the copies of Xerces in each of the projects, but more importantly without some declarative statement of
+your dependencies there is no way you could perform any analysis. People tend to miss the point entirely regarding
+a declarative dependency use. People say it's so easy just to store their dependencies in an SCM but try decomposing
+your big crappy build into components to encourage reuse and ease of maintenance, or try to analyze what you might
+need at runtime between all your different apps with commons dependencies in the graph and you're shit out of luck.
+The true power of declarative dependencies lies not in the fact that you can save a few bytes of disk space, though
+it can really add up if you're not careful, but in the analysis that can be performed. Once you have a decent graph
+all sorts of things are possible. Back to history: so now that declarative dependencies existed it needed to
+be easier …</p>
+<p>This is when I decided to employ standard Java-like inheritance in the model used and find a way to create a repository
+for things you need to build. So I hacked in some inheritance goop and now it was time for the repository. I asked
+around Apache to see if it would be possible to host a repository and soon found out that it was not possible to
+host non-Apache-like artifacts. So LGPL and GPL artifacts were out which didn't really make for a useful repository.
+After a little hunting I found <a class="externalLink" href="http://www.ibiblio.org">Ibiblio</a> which is a vast archive of all sorts of neat
+stuff including tons of free software. One of the mandates of Ibiblio is to aid in the dispersal of free software.
+Sounded perfect to me so I got in contact with John Reuning at Ibiblio and the rest is history. Working with the
+folks at Ibiblio has been a pleasure, the admins there are an amazingly helpful and talented bunch. They let us
+store whatever free software we want, provide great stats, and will let us host any software we want. Ibiblio
+is very cool.</p>
+<p>Many people had some problems with Maven 1.x but it generally worked and all tools in their first generation
+suffer from many short comings and the only way to overcome that is to forge ahead and try to create something
+better the next time around. With all the feed back the Maven developers have received from 1.x users
+and during the betas of 2.0 we think we've finally got something to build on. The first version of Maven
+was written by myself with lots of help from Bob McWhirter</p></section>
</main>
</div>
</div>
Modified: maven/website/content/background/philosophy-of-maven.html
==============================================================================
--- maven/website/content/background/philosophy-of-maven.html (original)
+++ maven/website/content/background/philosophy-of-maven.html Thu Dec 2 20:29:27 2021
@@ -1,18 +1,18 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/markdown/background/philosophy-of-maven.md at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/markdown/background/philosophy-of-maven.md at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<title>Maven – Philosophy of Maven</title>
- <link rel="stylesheet" href="../css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="../css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
- <script src="../js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="../js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
@@ -145,9 +145,30 @@ under the License.
12 October 2005
-->
-<p>Maven is generally considered by many to be a build tool. Many people who come to Maven initially are familiar with Ant so it’s a natural association but Maven is not just a build tool, and not just a replacement for Ant. Maven is an entirely different creature from Ant. Ant is simply a toolbox whereas Maven is about the application of patterns in order to achieve an infrastructure which displays the characteristics of visibility, reusability, maintainability, and comprehensibility.</p>
-<p>Without these characteristics it is highly improbable that multiple individuals will work productively together on a project. Without visibility it is unlikely an individual will know what another has accomplished and as such there is a very good chance useful code will not be reused. When code is not reused it is very hard to create a maintainable system. When everyone is constantly rooting around trying to figure out where all these different bits and pieces are that make up your project there is very little chance anyone is going to comprehend the project as a whole. As a result you end up with the silo effect, a decay of shared knowledge along with the commensurate degree of frustration among team members. A natural effect when processes don’t work in the same way for everyone.</p>
-<p>Maven was born of the very practical desire to make several projects at Apache work in the same way. So that developers could freely move between these projects, knowing clearly how they all worked by understanding how one of them worked. If a developer spent time understanding how one project built it was intended that they would not have to go through this process again when they moved on to the next project. The same idea extends to testing, generating documentation, generating metrics and reports, testing and deploying. All projects share enough of the same characteristics, an understanding of which Maven tries to harness in its general approach to project management. On a very high level all projects need to be built, tested, packaged, documented and deployed. Of course there is infinite variation in each of the above mentioned steps, but this variation still occurs within the confines of a well defined path and it is this path that Maven attempts to present to everyone in a
clear way. The easiest way to make a path clear is to provide people with a set of patterns that can be shared by anyone involved in a project.</p>
+<p>Maven is generally considered by many to be a build tool. Many people who come to Maven initially are familiar
+with Ant so it's a natural association but Maven is not just a build tool, and not just a replacement for Ant.
+Maven is an entirely different creature from Ant. Ant is simply a toolbox whereas Maven is about the
+application of patterns in order to achieve an infrastructure which displays the characteristics of
+visibility, reusability, maintainability, and comprehensibility.</p>
+<p>Without these characteristics it is highly improbable that multiple individuals will work productively together
+on a project. Without visibility it is unlikely an individual will know what another has accomplished and as such
+there is a very good chance useful code will not be reused. When code is not reused it is very hard to create
+a maintainable system. When everyone is constantly rooting around trying to figure out where all these different
+bits and pieces are that make up your project there is very little chance anyone is going to comprehend the
+project as a whole. As a result you end up with the silo effect, a decay of shared knowledge along with
+the commensurate degree of frustration among team members. A natural effect when processes don't work
+in the same way for everyone.</p>
+<p>Maven was born of the very practical desire to make several projects at Apache work in the same way. So that developers
+could freely move between these projects, knowing clearly how they all worked by understanding how one of them
+worked. If a developer spent time understanding how one project built it was intended that they would not have
+to go through this process again when they moved on to the next project. The same idea extends to testing,
+generating documentation, generating metrics and reports, testing and deploying. All projects share
+enough of the same characteristics, an understanding of which Maven tries to harness in its general approach
+to project management. On a very high level all projects need to be built, tested, packaged, documented
+and deployed. Of course there is infinite variation in each of the above mentioned steps, but this variation
+still occurs within the confines of a well defined path and it is this path that Maven attempts to present to
+everyone in a clear way. The easiest way to make a path clear is to provide people with a set of patterns that
+can be shared by anyone involved in a project.</p>
</main>
</div>
</div>
Modified: maven/website/content/ci-management.html
==============================================================================
--- maven/website/content/ci-management.html (original)
+++ maven/website/content/ci-management.html Thu Dec 2 20:29:27 2021
@@ -1,18 +1,18 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.1.2:ci-management at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from org.apache.maven.plugins:maven-project-info-reports-plugin:3.1.2:ci-management at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<title>Maven – CI Management</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="./js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
@@ -143,7 +143,7 @@
<th>Address</th>
<th>Configuration</th></tr>
<tr class="b">
-<td>mail</td>
+<td align="left">mail</td>
<td>-</td>
<td>address=notifications@maven.apache.org</td></tr></table></section>
</main>
Modified: maven/website/content/code-quality-management.html
==============================================================================
--- maven/website/content/code-quality-management.html (original)
+++ maven/website/content/code-quality-management.html Thu Dec 2 20:29:27 2021
@@ -1,18 +1,18 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/markdown/code-quality-management.md at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/markdown/code-quality-management.md at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<title>Maven – Code Quality Management</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="./js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
@@ -140,13 +140,14 @@ KIND, either express or implied. See th
specific language governing permissions and limitations
under the License.
-->
-Some existing Maven plugins use code analysis technologies (like
-[Checkstyle][Checkstyle], [PMD][PMD], [JDepend][JDepend], ...) to generate various quality reports. This
+
+<p>Some existing Maven plugins use code analysis technologies (like
+<a class="externalLink" href="https://maven.apache.org/plugins/maven-checkstyle-plugin/">Checkstyle</a>, <a class="externalLink" href="https://maven.apache.org/plugins/maven-pmd-plugin/">PMD</a>, <a class="externalLink" href="https://mojohaus.org/jdepend-maven-plugin/">JDepend</a>, …) to generate various quality reports. This
page lists technologies and platforms that know how to aggregate all
-this information to offer enhanced quality management functionalities.
-<section>
+this information to offer enhanced quality management functionalities.</p><section>
<h3><a name="Quality_management_technologies_and_platforms"></a>Quality management technologies and platforms</h3>
-<p>Following is an alphabetical list of those we’ve heard mentioned around the Maven community:</p>
+<p>Following is an alphabetical list of those we've heard mentioned around
+the Maven community:</p>
<ul>
<li><a class="externalLink" href="https://hudson-ci.org">Hudson</a></li>
Modified: maven/website/content/community.html
==============================================================================
--- maven/website/content/community.html (original)
+++ maven/website/content/community.html Thu Dec 2 20:29:27 2021
@@ -1,18 +1,18 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/markdown/community.md at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/markdown/community.md at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<title>Maven – The Maven Community</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="./js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
@@ -140,33 +140,60 @@ KIND, either express or implied. See th
specific language governing permissions and limitations
under the License.
-->
-Maven, like any other open source project, relies heavily on the efforts
+
+<p>Maven, like any other open source project, relies heavily on the efforts
of the entire user community to contribute improvements,
report defects, communicate use cases, write documentation,
and assist other users in need. This is a quick guide outlining
what members of the Maven community can do to make the system work
-better for everyone.
-<section>
+better for everyone.</p><section>
<h3><a name="Helping_With_Maven"></a>Helping With Maven</h3>
-<p>There is already a comprehensive <a href="./guides/development/guide-helping.html">Guide to Helping With Maven</a>. That guide focuses upon beginning as a supporter, with information on how to help the coding effort.</p><section>
+<p>There is already a comprehensive <a href="./guides/development/guide-helping.html">Guide to Helping With
+Maven</a>. That guide focuses upon
+beginning as a supporter, with information on how to help the coding
+effort.</p><section>
<h4><a name="Commit_Questions_or_Answers_to_the_Maven_User_FAQ"></a>Commit Questions or Answers to the Maven User FAQ</h4>
-<p>If you find things which are not correct or could be explained in a better way or you simply miss things do not hesitate to contact the maven community via the users mailing list and tell us about it.</p></section><section>
+<p>If you find things which are not correct or could be
+explained in a better way or you simply miss things
+do not hesitate to contact the maven community via
+the users mailing list and tell us about it.</p></section><section>
<h4><a name="Help_Log_Defects_in_JIRA"></a>Help Log Defects in JIRA</h4>
-<p>Just as any other healthy project requires a quick turn-around on defects, and a transparent method of users to have their wishes heard, so too does Maven need your help. Refer to the <a href="./issue-management.html">Issue Management</a> page.</p></section><section>
+<p>Just as any other healthy project requires a quick turn-around on
+defects, and a transparent method of users to have their wishes heard,
+so too does Maven need your help. Refer to the <a href="./issue-management.html">Issue
+Management</a> page.</p></section><section>
<h4><a name="Developers"></a>Developers</h4>
-<p>For Maven developers, committers, PMC: there is a <a href="./developers/index.html">Developers Guide</a>.</p></section></section><section>
+<p>For Maven developers, committers, PMC: there is a <a href="./developers/index.html">Developers
+Guide</a>.</p></section></section><section>
<h3><a name="Being_a_Good_Maven_Citizen"></a>Being a Good Maven Citizen</h3>
-<p>The concept of a public repository built into the core architecture of Maven makes it necessarily community-centric. There are a few simple things that Maven users may do to help keep that community thriving.</p><section>
+<p>The concept of a public repository built into the core architecture of
+Maven makes it necessarily community-centric. There are a few simple
+things that Maven users may do to help keep that community thriving.</p><section>
<h4><a name="Be_a_Kind_Public_Repository_User"></a>Be a Kind Public Repository User</h4>
-<p>The best thing that a user can do is to set up their own remote repository mirror containing the projects needed: this is called a <a href=".//repository-management.html">repository manager</a>. This reduces strain on the Maven central repository, and allows new users to get acquainted with Maven easier and quicker. This is especially important for power-users and corporations. The incentive behind this is, controlling your own servers can give you desired level of security and more control over uptime, resulting in a better experience for your users. With that said, keep the following sentiment in mind:</p>
+<p>The best thing that a user can do is to set up their own remote
+repository mirror containing the projects needed: this is called a
+<a href=".//repository-management.html">repository manager</a>. This reduces strain
+on the Maven central repository, and allows new users to get acquainted
+with Maven easier and quicker. This is especially important for
+power-users and corporations. The incentive behind this is, controlling
+your own servers can give you desired level of security and more control
+over uptime, resulting in a better experience for your users. With that
+said, keep the following sentiment in mind:</p>
<p><i>DO NOT wget THE ENTIRE REPOSITORY!</i></p>
-<p>Please take only the jars you need. We understand this is may entail more work, but grabbing more than 1,7 TiB of binaries really kills our servers.</p></section></section><section>
+<p>Please take only the jars you need. We understand this is may entail
+more work, but grabbing more than 1,7 TiB of binaries really kills our
+servers.</p></section></section><section>
<h3><a name="User_Gathering_Spots"></a>User Gathering Spots</h3>
-<p>These are a few of the watering holes around which Maven users tend to gather.</p><section>
+<p>These are a few of the watering holes around which Maven users tend to
+gather.</p><section>
<h4><a name="Mailing_Lists"></a>Mailing Lists</h4>
-<p>Maven has a number of <a href="./mailing-lists.html">Mailing Lists</a>, and the Maven User List is specifically dedicated to answering questions about all Maven things.</p></section><section>
+<p>Maven has a number of <a href="./mailing-lists.html">Mailing Lists</a>, and the Maven
+User List is specifically dedicated to answering questions about all
+Maven things.</p></section><section>
<h4><a name="Slack"></a>Slack</h4>
-<p>For people actively contributing to Maven, especially committers, there is <a class="externalLink" href="https://infra.apache.org">the ASF Slack workspace</a> available to discuss issues, solve problems and build community in real-time.</p></section></section></section>
+<p>For people actively contributing to Maven, especially committers, there
+is <a class="externalLink" href="https://infra.apache.org">the ASF Slack workspace</a> available to discuss
+issues, solve problems and build community in real-time.</p></section></section></section>
</main>
</div>
</div>
Modified: maven/website/content/configure.html
==============================================================================
--- maven/website/content/configure.html (original)
+++ maven/website/content/configure.html Thu Dec 2 20:29:27 2021
@@ -1,18 +1,18 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/markdown/configure.md at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/markdown/configure.md at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<title>Maven – Configuring Apache Maven</title>
- <link rel="stylesheet" href="./css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="./css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="./css/site.css" />
<link rel="stylesheet" href="./css/print.css" media="print" />
- <script src="./js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="./js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
@@ -146,22 +146,29 @@ KIND, either express or implied. See th
specific language governing permissions and limitations
under the License.
-->
-The configuration for Apache Maven usage itself and projects built with resides
-in a number of places:
-<section>
+
+<p>The configuration for Apache Maven usage itself and projects built with resides
+in a number of places:</p><section>
<h2><a name="MAVEN_OPTS_environment_variable:"></a><code>MAVEN_OPTS</code> environment variable:</h2>
-<p>This variable contains parameters used to start up the JVM running Maven and can be used to supply additional options to it. E.g. JVM memory settings could be defined with the value <code>-Xms256m -Xmx512m</code>.</p></section><section>
+<p>This variable contains parameters used to start up the JVM running Maven and
+can be used to supply additional options to it. E.g. JVM memory
+settings could be defined with the value <code>-Xms256m -Xmx512m</code>.</p></section><section>
<h2><a name="settings.xml_file:"></a><code>settings.xml</code> file:</h2>
-<p>Located in USER_HOME/.m2 the settings files is designed to contain any configuration for Maven usage across projects.</p></section><section>
+<p>Located in USER_HOME/.m2 the settings files is designed to contain any
+configuration for Maven usage across projects.</p></section><section>
<h2><a name="a.mvn_directory:"></a><code>.mvn</code> directory:</h2>
-<p>Located within the project’s top level directory, the files <code>maven.config</code>, <code>jvm.config</code>, and <code>extensions.xml</code> contain project specific configuration for running Maven.</p>
+<p>Located within the project's top level directory, the files <code>maven.config</code>, <code>jvm.config</code>, and <code>extensions.xml</code>
+contain project specific configuration for running Maven.</p>
<p>This directory is part of the project and may be checked in into your version control.</p><section>
<h3><a name="a.mvn.2Fextensions.xml_file:"></a><code>.mvn/extensions.xml</code> file:</h3>
-<p>The old way (up to Maven 3.2.5) was to create a jar (must be shaded if you have other dependencies) which contains the extension and put it manually into the <code>${MAVEN_HOME}/lib/ext</code> directory. This means you had to change the Maven installation. The consequence was that everyone who likes to use this needed to change it’s installation and makes the on-boarding for a developer much more inconvenient. The other option was to give the path to the jar on command line via <code>mvn -Dmaven.ext.class.path=extension.jar</code>. This has the drawback giving those options to your Maven build every time you are calling Maven. Not very convenient as well.</p>
+<p>The old way (up to Maven 3.2.5) was to create a jar (must be shaded if you have other dependencies) which contains the extension and put
+it manually into the <code>${MAVEN_HOME}/lib/ext</code> directory. This means you had to change the Maven installation. The consequence was that everyone
+who likes to use this needed to change it’s installation and makes the on-boarding for a developer much more inconvenient. The other
+option was to give the path to the jar on command line via <code>mvn -Dmaven.ext.class.path=extension.jar</code>. This has the drawback giving those
+options to your Maven build every time you are calling Maven. Not very convenient as well.</p>
<p>From now on this can be done much more simpler and in a more Maven like way. So you can define an <code>${maven.projectBasedir}/.mvn/extensions.xml</code> file which looks like the following:</p>
-<div class="source">
-<div class="source"><pre class="prettyprint linenums"><extensions xmlns="http://maven.apache.org/EXTENSIONS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+<div class="source"><pre class="prettyprint linenums"><code class="language-xml"><extensions xmlns="http://maven.apache.org/EXTENSIONS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0 http://maven.apache.org/xsd/core-extensions-1.0.0.xsd">
<extension>
<groupId/>
@@ -169,20 +176,21 @@ in a number of places:
<version/>
</extension>
</extensions>
-</pre></div></div>
-
+</code></pre></div>
<p>Now you can simply use an extension by defining the usual maven coordinates groupId, artifactId, version as any other artifact. Furthermore all transitive dependencies of those extensions will automatically being downloaded from your repository. So no need to create a shaded artifact anymore.</p></section><section>
<h3><a name="a.mvn.2Fmaven.config_file:"></a><code>.mvn/maven.config</code> file:</h3>
-<p>It’s really hard to define a general set of options for calling the maven command line. Starting with Maven 3.3.1+, this can be solved by putting this options to a script but this can now simple being done by defining <code>${maven.projectBasedir}/.mvn/maven.config</code> file which contains the configuration options for the <code>mvn</code> command line.</p>
-<p>For example things like <code>-T3 -U --fail-at-end</code>. So you only have to call Maven just by using <code>mvn clean package</code> instead of <code>mvn -T3 -U --fail-at-end clean package</code> and not to miss the <code>-T3 -U --fail-at-end</code> options on every call. The <code>${maven.projectBasedir}/.mvn/maven.config</code> is located in the <code>${maven.projectBasedir}/.mvn/</code> directory; also works if in the root of a multi module build.</p></section><section>
+<p>It’s really hard to define a general set of options for calling the maven command line. Starting with Maven 3.3.1+, this can be solved by
+putting this
+options to a script but this can now simple being done by defining <code>${maven.projectBasedir}/.mvn/maven.config</code> file which contains the
+configuration options for the <code>mvn</code> command line.</p>
+<p>For example things like <code>-T3 -U --fail-at-end</code>. So you only have to call Maven just by using <code>mvn clean package</code> instead of <code>mvn -T3 -U --fail-at-end clean package</code> and not to miss the <code>-T3 -U --fail-at-end</code> options on every call. The
+<code>${maven.projectBasedir}/.mvn/maven.config</code> is located in the <code>${maven.projectBasedir}/.mvn/</code> directory; also works if in the root of a multi module build.</p></section><section>
<h3><a name="a.mvn.2Fjvm.config_file:"></a><code>.mvn/jvm.config</code> file:</h3>
<p>Starting with Maven 3.3.1+ you can define JVM configuration via <code>${maven.projectBasedir}/.mvn/jvm.config</code> file which means you can define the options for your build on a per project base. This file will become part of your project and will be checked in along with your project. So no need anymore for <code>MAVEN_OPTS</code>, <code>.mavenrc</code> files. So for example if you put the following JVM options into the <code>${maven.projectBasedir}/.mvn/jvm.config</code> file</p>
-<div class="source">
-<div class="source"><pre class="prettyprint linenums"> -Xmx2048m -Xms1024m -XX:MaxPermSize=512m -Djava.awt.headless=true
-</pre></div></div>
-
-<p>You don’t need to use these options in <code>MAVEN_OPTS</code> or switch between different configurations.</p></section></section><section>
+<div class="source"><pre class="prettyprint linenums"><code> -Xmx2048m -Xms1024m -XX:MaxPermSize=512m -Djava.awt.headless=true
+</code></pre></div>
+<p>You don't need to use these options in <code>MAVEN_OPTS</code> or switch between different configurations.</p></section></section><section>
<h2><a name="Other_guides"></a>Other guides</h2>
<p>The following guides contain further information to specific configuration aspects:</p>
<ul>
Added: maven/website/content/css/apache-maven-fluido-1.10.0.min.css
==============================================================================
--- maven/website/content/css/apache-maven-fluido-1.10.0.min.css (added)
+++ maven/website/content/css/apache-maven-fluido-1.10.0.min.css Thu Dec 2 20:29:27 2021
@@ -0,0 +1,17 @@
+/*!
+ * Bootstrap v2.3.2
+ *
+ * Copyright 2013 Twitter, Inc
+ * Licensed under the Apache License v2.0
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Designed and built with all the love in the world by @mdo and @fat.
[... 11 lines stripped ...]
Modified: maven/website/content/developers/committer-environment.html
==============================================================================
--- maven/website/content/developers/committer-environment.html (original)
+++ maven/website/content/developers/committer-environment.html Thu Dec 2 20:29:27 2021
@@ -1,20 +1,20 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/apt/developers/committer-environment.apt at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/apt/developers/committer-environment.apt at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<meta name="author" content="Vincent Siveton" />
<meta name="date" content="2006-10-01" />
<title>Maven – Developers centre - Committer Environment</title>
- <link rel="stylesheet" href="../css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="../css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
- <script src="../js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="../js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
Modified: maven/website/content/developers/committer-settings.html
==============================================================================
--- maven/website/content/developers/committer-settings.html (original)
+++ maven/website/content/developers/committer-settings.html Thu Dec 2 20:29:27 2021
@@ -1,21 +1,21 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from content/apt/developers/committer-settings.apt at 2021-12-02
- | Rendered using Apache Maven Fluido Skin 1.9.1-SNAPSHOT
+ | Generated by Apache Maven Doxia Site Renderer 1.10 from content/apt/developers/committer-settings.apt at 2021-12-02
+ | Rendered using Apache Maven Fluido Skin 1.10.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.9.2" />
+ <meta name="generator" content="Apache Maven Doxia Site Renderer 1.10" />
<meta name="author" content="Vincent Siveton
Dennis Lundberg" />
<meta name="date" content="2011-05-23" />
<title>Maven – Developers centre - Committer Settings</title>
- <link rel="stylesheet" href="../css/apache-maven-fluido-1.9.1-SNAPSHOT.min.css" />
+ <link rel="stylesheet" href="../css/apache-maven-fluido-1.10.0.min.css" />
<link rel="stylesheet" href="../css/site.css" />
<link rel="stylesheet" href="../css/print.css" media="print" />
- <script src="../js/apache-maven-fluido-1.9.1-SNAPSHOT.min.js"></script>
+ <script src="../js/apache-maven-fluido-1.10.0.min.js"></script>
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){