This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/maven-project-info-reports-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new d437a9a  Refresh the plugin site and README
d437a9a is described below

commit d437a9a55f08d4d91016abd2c53a9076f18d76a3
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Tue Nov 17 23:47:27 2026 +0000

    Refresh the plugin site and README
---
 README.md                                          | 88 ++++++++--------------
 src/site/markdown/examples/custom-report.md.vm     | 51 ++++---------
 src/site/markdown/examples/individual-reports.md   | 31 --------
 .../markdown/examples/individual-reports.md.vm     | 55 ++++++++++++++
 src/site/markdown/examples/scm-report.md.vm        | 34 +++++----
 src/site/markdown/examples/selective-reports.md.vm |  7 +-
 src/site/markdown/faq.md                           | 12 ++-
 src/site/markdown/index.md                         | 86 ++++++++++++---------
 8 files changed, 189 insertions(+), 175 deletions(-)

diff --git a/README.md b/README.md
index 438ef70..6715de9 100644
--- a/README.md
+++ b/README.md
@@ -14,70 +14,48 @@
  See the License for the specific language governing permissions and
  limitations under the License.
 -->
-Contributing to [Apache Maven Project Info Reports 
Plugin](https://maven.apache.org/plugins/maven-project-info-reports-plugin/)
-======================
 
-[![Apache License, Version 2.0, January 
2004](https://img.shields.io/github/license/apache/maven.svg?label=License)][license]
-[![Maven 
Central](https://img.shields.io/maven-central/v/org.apache.maven.plugins/maven-project-info-reports-plugin.svg?label=Maven%20Central)](https://search.maven.org/artifact/org.apache.maven.plugins/maven-project-info-reports-plugin)
+# Apache Maven Project Info Reports Plugin
+
+[![Apache License, Version 2.0, January 
2004](https://img.shields.io/github/license/apache/maven.svg?label=License)](https://www.apache.org/licenses/LICENSE-2.0)
+[![Maven 
Central](https://img.shields.io/maven-central/v/org.apache.maven.plugins/maven-project-info-reports-plugin.svg?label=Maven%20Central)](https://central.sonatype.com/artifact/org.apache.maven.plugins/maven-project-info-reports-plugin)
 [![Reproducible 
Builds](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/jvm-repo-rebuild/reproducible-central/master/content/org/apache/maven/plugins/maven-project-info-reports-plugin/badge.json)](https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/plugins/maven-project-info-reports-plugin/README.md)
-[![Jenkins 
Status](https://img.shields.io/jenkins/s/https/ci-maven.apache.org/job/Maven/job/maven-box/job/maven-project-info-reports-plugin/job/master.svg?)][build]
-[![Jenkins 
tests](https://img.shields.io/jenkins/t/https/ci-maven.apache.org/job/Maven/job/maven-box/job/maven-project-info-reports-plugin/job/master.svg?)][test-results]
+[![Verify](https://github.com/apache/maven-project-info-reports-plugin/actions/workflows/maven-verify.yml/badge.svg)](https://github.com/apache/maven-project-info-reports-plugin/actions/workflows/maven-verify.yml)
+
+Generates the "Project Information" pages of a Maven site from what the POM 
declares:
+dependencies, Maven coordinates, team, licenses, mailing lists, source 
repository, issue
+tracker, CI, distribution management, plugins and modules. The
+[Maven Site Plugin](https://maven.apache.org/plugins/maven-site-plugin/) runs 
these reports
+during `mvn site`; each one can also run on its own, for example
+`mvn project-info-reports:dependencies`.
 
+The plugin requires Maven 3.9.0 or later and Java 8 or later.
 
-You have found a bug, or you have an idea for a cool new feature? Contributing
-code is a great way to give something back to the open source community. Before
-you dig right into the code, there are a few guidelines that we need
-contributors to follow so that we can have a chance of keeping on top of
-things.
+- Documentation: 
<https://maven.apache.org/plugins/maven-project-info-reports-plugin/>
+- Issues: <https://github.com/apache/maven-project-info-reports-plugin/issues>
+- Release notes: 
<https://github.com/apache/maven-project-info-reports-plugin/releases>
 
-Getting Started
----------------
+## Build
 
-+ Make sure you have a [GitHub account](https://github.com/signup/free).
-+ If you're planning to implement a new feature, it makes sense to discuss 
your changes 
-  on the [dev list][ml-list] first. 
-  This way you can make sure you're not wasting your time on something that 
isn't 
-  considered to be in Apache Maven's scope.
-+ Submit a ticket for your issue, assuming one does not already exist.
-  + Clearly describe the issue, including steps to reproduce when it is a bug.
-  + Make sure you fill in the earliest version that you know has the issue.
-+ Fork the repository on GitHub.
+```shell
+mvn verify
+```
 
-Making and Submitting Changes
---------------
+Run the integration tests in `src/it` with the `run-its` profile:
 
-We accept Pull Requests via GitHub. The [developer mailing list][ml-list] is 
the
-main channel of communication for contributors.  
-There are some guidelines which will make applying PRs easier for us:
-+ Create a topic branch from where you want to base your work (this is usually 
the master branch).
-  Push your changes to a topic branch in your fork of the repository.
-+ Make commits of logical units.
-+ Respect the original code style: by using the same [codestyle][code-style],
-  patches should only highlight the actual difference, not being disturbed by 
any formatting issues:
-  + Only use spaces for indentation.
-  + Create minimal diffs - disable on save actions like reformat source code 
or organize imports. 
-    If you feel the source code should be reformatted, create a separate PR 
for this change.
-  + Check for unnecessary whitespace with `git diff --check` before committing.
-+ Make sure you have added the necessary tests (JUnit/IT) for your changes.
-+ Run all the tests with `mvn -Prun-its verify` to assure nothing else was 
accidentally broken.
-+ Submit a pull request to the repository in the Apache organization.
+```shell
+mvn -Prun-its verify
+```
 
-If you plan to contribute on a regular basis, please consider filing a 
[contributor license agreement][cla].
+Build the plugin site, including the goal pages, with:
 
-Additional Resources
---------------------
+```shell
+mvn -Preporting site
+```
 
-+ [Contributing 
patches](https://maven.apache.org/guides/development/guide-maven-development.html#Creating_and_submitting_a_patch)
-+ [Apache Maven Project Info Reports JIRA project page][jira]
-+ [Contributor License Agreement][cla]
-+ [General GitHub documentation](https://help.github.com/)
-+ [GitHub pull request 
documentation](https://help.github.com/send-pull-requests/)
-+ [Apache Maven Twitter Account](https://twitter.com/ASFMavenProject)
+## Contributing
 
-[license]: https://www.apache.org/licenses/LICENSE-2.0
-[ml-list]: https://maven.apache.org/mailing-lists.html
-[code-style]: https://maven.apache.org/developers/conventions/code.html
-[cla]: https://www.apache.org/licenses/#clas
-[maven-wiki]: https://cwiki.apache.org/confluence/display/MAVEN/Index
-[test-results]: 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-project-info-reports-plugin/job/master/lastCompletedBuild/testReport/
-[build]: 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-project-info-reports-plugin/job/master/
+Open an issue or a pull request against `master`. Code style is enforced by 
Spotless:
+run `mvn spotless:apply` before pushing. The
+[Maven development 
guide](https://maven.apache.org/guides/development/guide-helping.html)
+covers the rest.
diff --git a/src/site/markdown/examples/custom-report.md.vm 
b/src/site/markdown/examples/custom-report.md.vm
index 54f355f..b092234 100644
--- a/src/site/markdown/examples/custom-report.md.vm
+++ b/src/site/markdown/examples/custom-report.md.vm
@@ -26,7 +26,9 @@ under the License.
 
 # Customize the Text Reports
 
-Currently, all reports have a static renderer, only texts could be changed.
+The layout of every report is fixed, but its texts come from a resource bundle 
that you can override.
+Put the keys you want to change in a properties file. The plugin reads
+`src/site/custom/project-info-reports.properties` by default; set 
`customBundle` to use another path:
 
 ```xml
 <project>
@@ -38,7 +40,7 @@ Currently, all reports have a static renderer, only texts 
could be changed.
         <artifactId>maven-project-info-reports-plugin</artifactId>
         <version>${project.version}</version>
         <configuration>
-          <!-- By default -->
+          <!-- this is the default value -->
           
<customBundle>${esc.d}{project.basedir}/src/site/custom/project-info-reports.properties</customBundle>
         </configuration>
       </plugin>
@@ -49,47 +51,26 @@ Currently, all reports have a static renderer, only texts 
could be changed.
 </project>
 ```
 
-To change texts in the reports, you should import the default Project Info 
report bundles from 
[https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/](https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/)
 and edit them. For example, if you want to modify the Mailing Lists 
introduction, you should edit the `report.mailing-lists.intro` property.
-
-Extract of the default bundle 
[project-info-reports.properties](https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/project-info-reports.properties):
+Look up the keys in the default bundle
+[project-info-reports.properties](https://github.com/apache/maven-project-info-reports-plugin/blob/master/src/main/resources/project-info-reports.properties)
+(translations sit next to it in
+[src/main/resources](https://github.com/apache/maven-project-info-reports-plugin/tree/master/src/main/resources)).
+For example, the introduction of the Mailing Lists report is 
`report.mailing-lists.intro`:
 
 ```properties
 report.mailing-lists.intro = These are the mailing lists that have been 
established for this project. For each list, there is a subscribe, unsubscribe, 
and an archive link.
 ```
 
-Extract of a custom bundle 
`${esc.d}{project.basedir}/src/site/custom/project-info-reports.properties` for 
the Apache Commons project:
+A custom bundle that changes this introduction and renames two reports in the 
site menu:
 
 ```properties
-
-report.mailing-lists.intro = These are the mailing lists that have been 
established for this project. For each list, there is a subscribe, unsubscribe, 
and an archive link.\
-        <p>\
-            Questions related to the usage of Commons components should be 
posted to the\
-            <a href="https://mail-archives.apache.org/mod_mbox/commons-user/"; 
class="externalLink">User List</a>.\
-            <br>\
-            The <a 
href="https://mail-archives.apache.org/mod_mbox/commons-dev/"; 
class="externalLink">Developer List</a>\
-            is for questions and discussion related to the development of 
Commons components.\
-            <br>\
-            Please do not cross-post; developers are also subscribed to the 
user list.\
-            Read the archives first in case your question has already been 
answered.\
-            If not, then subscribe to the appropriate list and post your 
question.\
-        </p>\
-        <p>\
-            <strong>Note:</strong> please don't send patches or attachments to 
any of the mailing lists.\
-            Patches are best handled via the <i>Issue Tracking</i> system.\
-            Otherwise, please upload the file to a public server and include 
the URL in the mail.\
-        </p>\
-        <p>\
-            Please read the <a 
href="http://www.apache.org/foundation/public-archives.html"; 
class="externalLink">Public Forum Archive Policy</a>\
-            and <a href="http://www.apache.org/dev/contrib-email-tips.html"; 
class="externalLink">Tips for email contributors</a>.\
-            <br>\
-            For further information on Apache mailing lists please read\
-            <a href="http://www.apache.org/foundation/mailinglists.html"; 
class="externalLink">General mailing list information</a>\
-            in particular the section entitled\
-            <a 
href="http://www.apache.org/foundation/mailinglists.html#subscribe"; 
class="externalLink">Subscribing and Unsubscribing</a>\
-        </p>
+report.mailing-lists.intro = Ask usage questions on the Users list of 
${esc.d}{project.name}.
+report.dependency-info.name = How to Depend on It
+report.dependencies.name = Third-Party Libraries
 ```
 
 **Notes:**
 
-1. You could also use Maven properties (i.e. `${esc.d}{project.artifactId}`) 
in the messages.
-1. If a bundle property is not defined in your custom bundle, the default will 
be displayed.
+1. Messages can use Maven properties such as `${esc.d}{project.artifactId}`.
+1. A key that is not in your custom bundle keeps its default text.
+1. A report's `name` key sets its label in the site menu.
diff --git a/src/site/markdown/examples/individual-reports.md 
b/src/site/markdown/examples/individual-reports.md
deleted file mode 100644
index da85985..0000000
--- a/src/site/markdown/examples/individual-reports.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Run Individual Reports
-author: 
-  - Johnny R. Ruiz III, Pete Marvin King
-date: 2008-07-24
----
-
-<!--
-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
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Run Individual Reports
-
-Each individual report can be generated without configuring anything in the 
`pom.xml`. Check the table in [Goals](../plugin-info.html) for the complete 
list of goals.
-
-**Note:** The reports generated using this method does not contain any 
navigational links. Also, the locale used is the JVM locale.
diff --git a/src/site/markdown/examples/individual-reports.md.vm 
b/src/site/markdown/examples/individual-reports.md.vm
new file mode 100644
index 0000000..f341a8c
--- /dev/null
+++ b/src/site/markdown/examples/individual-reports.md.vm
@@ -0,0 +1,55 @@
+---
+title: Run Individual Reports
+author: 
+  - Johnny R. Ruiz III, Pete Marvin King
+date: 2008-07-24
+---
+
+<!--
+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
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# Run Individual Reports
+
+Every report goal can run on its own, without configuring anything in the POM 
and without building
+the whole site. For example, to generate only the Dependencies report:
+
+```shell
+mvn project-info-reports:dependencies
+```
+
+The report is written to `target/reports/dependencies.html`; set 
`outputDirectory` to change the directory.
+See [Plugin Documentation](../plugin-info.html) for the complete list of goals.
+
+A report generated this way has no site navigation, and its texts are in the 
locale given by the
+`locale` parameter, not the JVM locale. Configure the parameter in the 
`<build>` section of the POM:
+
+```xml
+<build>
+  <plugins>
+    <plugin>
+      <groupId>org.apache.maven.plugins</groupId>
+      <artifactId>maven-project-info-reports-plugin</artifactId>
+      <version>${project.version}</version>
+      <configuration>
+        <locale>de</locale>
+      </configuration>
+    </plugin>
+  </plugins>
+</build>
+```
diff --git a/src/site/markdown/examples/scm-report.md.vm 
b/src/site/markdown/examples/scm-report.md.vm
index 82dffcc..b109fd8 100644
--- a/src/site/markdown/examples/scm-report.md.vm
+++ b/src/site/markdown/examples/scm-report.md.vm
@@ -26,17 +26,20 @@ under the License.
 
 # Customize the SCM Report
 
-By default, the SCM Report uses the information configured (or inherited) in 
the `<scm>` element of `pom.xml`. To override these values, you can configure 
the `webAccessUrl`, `anonymousConnection` and `developerConnection` properties.
+By default, the SCM report uses the `<scm>` element of the POM, including one 
inherited from a parent.
+To override these values, configure the `webAccessUrl`, `anonymousConnection` 
and `developerConnection`
+parameters of the [scm goal](../scm-mojo.html).
 
-This feature is useful when the project website is stored in a separate 
module, and you want the SCM report to give instructions for checking out the 
project trunk.
+This helps when the site is built from a module whose `<scm>` points to a 
subdirectory, and the
+report should tell readers how to check out the whole repository:
 
 ```xml
 <project>
   ...
   <scm>
-    
<connection>scm:svn:http://svn.example.org/repo/project/trunk/site</connection>
-    
<developerConnection>scm:svn:https://svn.example.org/repo/project/trunk/site</developerConnection>
-    <url>http://svn.example.org/viewvc/project/trunk/site</url>
+    <connection>scm:git:https://github.com/example/project.git</connection>
+    
<developerConnection>scm:git:ssh://[email protected]/example/project.git</developerConnection>
+    <url>https://github.com/example/project/tree/main/site</url>
   </scm>
   ...
   <reporting>
@@ -46,9 +49,9 @@ This feature is useful when the project website is stored in 
a separate module,
         <artifactId>maven-project-info-reports-plugin</artifactId>
         <version>${project.version}</version>
         <configuration>
-          
<webAccessUrl>http://svn.example.org/viewvc/project/trunk</webAccessUrl>
-          
<anonymousConnection>scm:svn:http://svn.example.org/repo/project/trunk</anonymousConnection>
-          
<developerConnection>scm:svn:https://svn.example.org/repo/project/trunk</developerConnection>
+          <webAccessUrl>https://github.com/example/project</webAccessUrl>
+          
<anonymousConnection>scm:git:https://github.com/example/project.git</anonymousConnection>
+          
<developerConnection>scm:git:ssh://[email protected]/example/project.git</developerConnection>
         </configuration>
       </plugin>
       ...
@@ -58,20 +61,23 @@ This feature is useful when the project website is stored 
in a separate module,
 </project>
 ```
 
-# How to exclude SCM anonymous access info?
+<a id="How_to_exclude_SCM_anonymous_access_info"></a>
 
-Just do not specify the `<connection/>` tag in the `<scm/>` tag. For instance, 
you could have:
+${esc.h}${esc.h} How to exclude SCM anonymous access info?
+
+Leave out `<connection>` in the `<scm>` element. The report then has no 
Anonymous Access section:
 
 ```xml
 <project>
   ...
   <scm>
-    <!-- Unspecified <connection/> tag -->
-    
<developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin/</developerConnection>
-    
<url>https://svn.apache.org/viewvc/maven/plugins/trunk/maven-project-info-reports-plugin/</url>
+    <!-- no <connection> -->
+    
<developerConnection>scm:git:ssh://[email protected]/example/project.git</developerConnection>
+    <url>https://github.com/example/project</url>
   </scm>
   ...
 </project>
 ```
 
-**Note**: Due to [Plexus](https://codehaus-plexus.github.io/) design, it is 
not possible to specify an empty value using the `<anonymousConnection/>` 
configuration element.
+**Note:** an empty `<anonymousConnection/>` in the plugin configuration does 
not remove the section:
+Maven treats an empty parameter as unset and falls back to 
`${esc.d}{project.scm.connection}`.
diff --git a/src/site/markdown/examples/selective-reports.md.vm 
b/src/site/markdown/examples/selective-reports.md.vm
index c5dbe4e..07a5e07 100644
--- a/src/site/markdown/examples/selective-reports.md.vm
+++ b/src/site/markdown/examples/selective-reports.md.vm
@@ -26,7 +26,9 @@ under the License.
 
 # Run Selective Reports
 
-To run the reports selectively, you can configure it to include only the 
reports that you prefer. Use `mvn site` to generate the selected reports.
+Without `<reportSets>`, `mvn site` runs the plugin's default set of reports. 
To build only some of them,
+list them in a `<reportSet>`; each `<report>` is a goal name from [Plugin 
Documentation](../plugin-info.html).
+Then run `mvn site` as usual.
 
 ```xml
 <project>
@@ -57,3 +59,6 @@ To run the reports selectively, you can configure it to 
include only the reports
   ...
 </project>
 ```
+
+A report whose POM section is empty, such as `ci-management` without 
`<ciManagement>`, is skipped even
+when it is listed. Set `skipEmptyReport` to `false` to generate it anyway.
diff --git a/src/site/markdown/faq.md b/src/site/markdown/faq.md
index 7ea4186..94f926c 100644
--- a/src/site/markdown/faq.md
+++ b/src/site/markdown/faq.md
@@ -35,7 +35,9 @@ under the License.
 
 ### Is it possible to customize the labels of the Project Reports Menu?
 
-Not yet. See the related issue: 
[MPIR-35](https://issues.apache.org/jira/browse/MPIR-35)
+Yes. The menu shows each report's name, which comes from the report's text 
bundle. Override the
+`report.<report>.name` key in a [custom 
bundle](./examples/custom-report.html), for example
+`report.dependencies.name = Third-Party Libraries`.
 
 <a id="How_to_exclude_SCM_anonymous_access_info"></a>
 
@@ -44,17 +46,19 @@ Not yet. See the related issue: 
[MPIR-35](https://issues.apache.org/jira/browse/
 See the [SCM report 
documentation](examples/scm-report.html#How_to_exclude_SCM_anonymous_access_info).
 
 <a id="How_to_use_developer.2Fcontributor_time_zone"></a>
+<a id="How_to_use_developercontributor_time_zone"></a>
 
 ### How to use developer/contributor time zone?
 
-Please refer to the [developer 
section](http://maven.apache.org/pom.html#Developers) of the POM reference.
+Set `<timezone>` on each `<developer>` or `<contributor>` in the POM, for 
example
+`<timezone>Europe/Berlin</timezone>`; the Team report adds a Time Zone column 
with the value. See the [developers 
section](https://maven.apache.org/pom.html#Developers) of the POM reference.
 
 <a id="Is_it_possible_to_customize_the_reports_rendering"></a>
 
 ### Is it possible to customize the reports rendering?
 
-Not yet, but 
[patches](https://github.com/apache/maven-project-info-reports-plugin/issues/) 
are always welcome!
-You could only [customize](./examples/custom-report.html) the texts in the 
reports.
+No. The layout of each report is fixed in the plugin; you can only 
[customize](./examples/custom-report.html)
+the texts. Proposals are welcome in the [issue 
tracker](https://github.com/apache/maven-project-info-reports-plugin/issues).
 
 <a 
id="Why_does_the_Licenses_report_link_to_my_license_instead_of_showing_its_text"></a>
 
diff --git a/src/site/markdown/index.md b/src/site/markdown/index.md
index 7d5c232..95bbbc0 100644
--- a/src/site/markdown/index.md
+++ b/src/site/markdown/index.md
@@ -26,54 +26,70 @@ under the License.
 -->
 
 # Apache Maven Project Info Reports Plugin
-The Maven Project Info Reports plugin is used to generate reports information 
about the project.
+
+The Project Info Reports Plugin turns what your POM declares into the "Project 
Information"
+pages of a Maven site: dependencies, Maven coordinates, team, licenses, 
mailing lists, source
+repository, issue tracker, continuous integration, distribution management, 
plugins and modules.
+
+The plugin requires Maven 3.9.0 or later and Java 8 or later.
+
+Most users come for one of these tasks:
+
+- Generate all project information pages with the rest of the site: run `mvn 
site` and open
+  `target/site/project-info.html`. See the [usage page](./usage.html).
+- Generate one report without building the site, for example the dependency 
list:
+  `mvn project-info-reports:dependencies` writes 
`target/reports/dependencies.html`.
+  See [Run Individual Reports](./examples/individual-reports.html).
+- Choose which reports the site contains: see [Run Selective 
Reports](./examples/selective-reports.html).
+- Change the texts or menu labels of the reports: see [Customize Text 
Reports](./examples/custom-report.html).
 
 ## Goals Overview
 
-The Project Info Reports Plugin has the following goals:
-
-- [project-info-reports:ci-management](./ci-management-mojo.html) is used to 
generate the Project Continuous Integration Management report.
-- [project-info-reports:dependencies](./dependencies-mojo.html) is used to 
generate the Project Dependencies report.
-- 
[project-info-reports:dependency-convergence](./dependency-convergence-mojo.html)
 is used to generate the Project Dependency Convergence report for (reactor) 
builds.
-- [project-info-reports:dependency-info](./dependency-info-mojo.html) is used 
to generate code snippets of the Maven coordinates to be added to build tools.
-- 
[project-info-reports:dependency-management](./dependency-management-mojo.html) 
is used to generate the Project Dependency Management report.
-- 
[project-info-reports:distribution-management](./distribution-management-mojo.html)
 is used to generate the Project Distribution Management report.
-- [project-info-reports:help](./help-mojo.html) is used to display help 
information on the Project Info Reports Plugin.
-- [project-info-reports:index](./index-mojo.html) is used to generate the 
Project index page.
-- [project-info-reports:issue-management](./issue-management-mojo.html) is 
used to generate the Project Issue Management report.
-- [project-info-reports:licenses](./licenses-mojo.html) is used to generate 
the Project Licenses report.
-- [project-info-reports:mailing-lists](./mailing-lists-mojo.html) is used to 
generate the Project Mailing Lists report.
-- [project-info-reports:modules](./modules-mojo.html) is used to generate the 
Project Modules report.
-- [project-info-reports:plugin-management](./plugin-management-mojo.html) is 
used to generate the Project Plugin Management report.
-- [project-info-reports:plugins](./plugins-mojo.html) is used to generate the 
Project Plugins report.
-- [project-info-reports:team](./team-mojo.html) is used to generate the 
Project Team report.
-- [project-info-reports:scm](./scm-mojo.html) is used to generate the Project 
Source Code Management report.
-- [project-info-reports:summary](./summary-mojo.html) is used to generate the 
Project Summary report.
-## Upcoming Incompatibility Notice
-
-With a future version mojos and output filenames will change for consistency 
alignment. See the following table for the upcoming changes:
-
-|Goal Name|New Goal Name|Output name|New Output Name|
-|:---:|:---:|:---:|:---:|
-|`dependency-info`|`maven-coordinates`|`dependency-info.html`|`maven-coordinates.html`|
+The plugin has the following goals. Each report goal can run inside `mvn site` 
or on its own.
+
+- [project-info-reports:ci-management](./ci-management-mojo.html) generates 
the CI Management report.
+- [project-info-reports:dependencies](./dependencies-mojo.html) generates the 
Dependencies report.
+- 
[project-info-reports:dependency-convergence](./dependency-convergence-mojo.html)
 generates the Dependency Convergence report for a single project or a reactor 
build.
+- [project-info-reports:dependency-info](./dependency-info-mojo.html) 
generates the Maven Coordinates report: snippets for declaring the project as a 
dependency in Maven, Ivy, Grape, Gradle, SBT and Leiningen; for a project with 
`maven-plugin` packaging, the plugin declaration.
+- 
[project-info-reports:dependency-management](./dependency-management-mojo.html) 
generates the Dependency Management report.
+- 
[project-info-reports:distribution-management](./distribution-management-mojo.html)
 generates the Distribution Management report.
+- [project-info-reports:help](./help-mojo.html) displays help information on 
the plugin.
+- [project-info-reports:index](./index-mojo.html) generates the About page of 
the project.
+- [project-info-reports:issue-management](./issue-management-mojo.html) 
generates the Issue Management report.
+- [project-info-reports:licenses](./licenses-mojo.html) generates the Licenses 
report.
+- [project-info-reports:mailing-lists](./mailing-lists-mojo.html) generates 
the Mailing Lists report.
+- [project-info-reports:modules](./modules-mojo.html) generates the Project 
Modules report.
+- [project-info-reports:plugin-management](./plugin-management-mojo.html) 
generates the Plugin Management report.
+- [project-info-reports:plugins](./plugins-mojo.html) generates the Plugins 
report.
+- [project-info-reports:scm](./scm-mojo.html) generates the Source Code 
Management report.
+- [project-info-reports:summary](./summary-mojo.html) generates the Summary 
report.
+- [project-info-reports:team](./team-mojo.html) generates the Team report.
+
+<a id="Upcoming_Incompatibility_Notice"></a>
+Since version 3.6.0 the `dependency-info` report is titled Maven Coordinates; 
the goal and its
+output file `dependency-info.html` keep their names.
 
 ## Usage
 
-General instructions on how to use the Project Info Reports Plugin can be 
found on the [usage page](./usage.html). Some more specific use cases are 
described in the examples given below.
-
-In case you still have questions regarding the plugin's usage, please have a 
look at the [FAQ](./faq.html) and feel free to contact the [user mailing 
list](./mailing-lists.html). The posts to the mailing list are archived and 
could already contain the answer to your question as part of an older thread. 
Hence, it is also worth browsing/searching the [mail 
archive](./mailing-lists.html).
+General instructions are on the [usage page](./usage.html), and the 
[FAQ](./faq.html) answers
+common questions. This plugin's own [project information 
pages](./project-info.html) show what
+each report looks like.
 
-If you feel like the plugin is missing a feature or has a defect, you can fill 
a feature request or bug report in our [issue 
tracker](./issue-management.html). When creating a new issue, please provide a 
comprehensive description of your concern. Especially for fixing bugs it is 
crucial that the developers can reproduce your problem. For this reason, entire 
debug logs, POMs or most preferably little demo projects attached to the issue 
are very much appreciated. Of course, patches are wel [...]
+Ask questions on the [user mailing list](./mailing-lists.html), and report a 
defect or request a
+feature in the [issue tracker](./issue-management.html). For a defect, a small 
project that
+reproduces it helps most. To contribute a fix, see the [source 
repository](./scm.html) and the
+[guide to helping with 
Maven](https://maven.apache.org/guides/development/guide-helping.html).
 
 ## Examples
 
-To provide you with better understanding on some usages of the Maven Project 
Info Reports Plugin, you can take a look into the following examples:
+The following examples cover common configurations:
 
 - [Run Selective Reports](./examples/selective-reports.html)
 - [Run Individual Reports](./examples/individual-reports.html)
 - [Customize the SCM Report](./examples/scm-report.html)
-- [Overview of the reports generated for this plugin](./project-info.html)
+- [Customize Text Reports](./examples/custom-report.html)
+
 ## Related Links
 
-- [Localization of Plugins](http://maven.apache.org/plugins/localization.html)
-- [Create a layout 
(skin))](http://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html)
+- [Localization of plugins](https://maven.apache.org/plugins/localization.html)
+- [Creating a site 
skin](https://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html)

Reply via email to