Author: svn-site-role
Date: Fri Sep 22 11:26:23 2023
New Revision: 1912481
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/docs/3.9.0/release-notes.html
maven/website/content/docs/3.9.1/release-notes.html
maven/website/content/docs/3.9.2/release-notes.html
maven/website/content/docs/3.9.3/release-notes.html
maven/website/content/docs/3.9.4/release-notes.html
maven/website/content/maven-site-1.0-site.jar
Modified: maven/website/content/docs/3.9.0/release-notes.html
==============================================================================
--- maven/website/content/docs/3.9.0/release-notes.html (original)
+++ maven/website/content/docs/3.9.0/release-notes.html Fri Sep 22 11:26:23 2023
@@ -177,6 +177,7 @@
<li>Maven 2.x was auto-injecting an ancient version of
<code>plexus-utils</code> dependency into the plugin classpath, and Maven 3.x
continued doing this to preserve backward compatibility. Starting with Maven
3.9, it does not happen anymore. This change may lead to plugin breakage. The
fix for affected plugin maintainers is to explicitly declare a dependency on
<code>plexus-utils</code>. The workaround for affected plugin users is to add
this dependency to plugin dependencies until issue is fixed by the affected
plugin maintainer. See <a href="https://issues.apache.org/jira/browse/MNG-6965";
class="externalLink">MNG-6965</a>.</li>
<li>Mojos are prevented to boostrap new instance of
<code>RepositorySystem</code> (for example by using deprecated
<code>ServiceLocator</code>), they should reuse <code>RepositorySystem</code>
instance provided by Maven instead. See <a
href="https://issues.apache.org/jira/browse/MNG-7471";
class="externalLink">MNG-7471</a>.</li>
<li>Each line in <code>.mvn/maven.config</code> is now interpreted as a single
argument. That is, if the file contains multiple arguments, these must now be
placed on separate lines, see <a
href="https://issues.apache.org/jira/browse/MNG-7684";
class="externalLink">MNG-7684</a>.</li>
+<li>System and user properties handling cleanup, see <a
href="https://issues.apache.org/jira/browse/MNG-7556";
class="externalLink">MNG-7556</a>. As a consequence, this may introduce
breakage in environments where the user properties were used to set system
properties or other way around, for example see <a
href="https://issues.apache.org/jira/projects/MNG/issues/MNG-7887";
class="externalLink">MNG-7887</a>.</li>
</ul></section><section>
<h3>Notable Core Improvements</h3>
<ul>
Modified: maven/website/content/docs/3.9.1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.9.1/release-notes.html (original)
+++ maven/website/content/docs/3.9.1/release-notes.html Fri Sep 22 11:26:23 2023
@@ -174,6 +174,7 @@
<li>Maven 2.x was auto-injecting an ancient version of
<code>plexus-utils</code> dependency into the plugin classpath, and Maven 3.x
continued doing this to preserve backward compatibility. Starting with Maven
3.9, it does not happen anymore. This change may lead to plugin breakage. The
fix for affected plugin maintainers is to explicitly declare a dependency on
<code>plexus-utils</code>. The workaround for affected plugin users is to add
this dependency to plugin dependencies until issue is fixed by the affected
plugin maintainer. See <a href="https://issues.apache.org/jira/browse/MNG-6965";
class="externalLink">MNG-6965</a>.</li>
<li>Mojos are prevented to boostrap new instance of
<code>RepositorySystem</code> (for example by using deprecated
<code>ServiceLocator</code>), they should reuse <code>RepositorySystem</code>
instance provided by Maven instead. See <a
href="https://issues.apache.org/jira/browse/MNG-7471";
class="externalLink">MNG-7471</a>.</li>
<li>Each line in <code>.mvn/maven.config</code> is now interpreted as a single
argument. That is, if the file contains multiple arguments, these must now be
placed on separate lines, see <a
href="https://issues.apache.org/jira/browse/MNG-7684";
class="externalLink">MNG-7684</a>.</li>
+<li>System and user properties handling cleanup, see <a
href="https://issues.apache.org/jira/browse/MNG-7556";
class="externalLink">MNG-7556</a>. As a consequence, this may introduce
breakage in environments where the user properties were used to set system
properties or other way around, for example see <a
href="https://issues.apache.org/jira/projects/MNG/issues/MNG-7887";
class="externalLink">MNG-7887</a>.</li>
</ul></section></section><section>
<h2>Known Issues</h2>
<p>None.</p></section><section>
Modified: maven/website/content/docs/3.9.2/release-notes.html
==============================================================================
--- maven/website/content/docs/3.9.2/release-notes.html (original)
+++ maven/website/content/docs/3.9.2/release-notes.html Fri Sep 22 11:26:23 2023
@@ -193,6 +193,7 @@ plugin versions. For non-ASF plugins, co
<li>Maven 2.x was auto-injecting an ancient version of
<code>plexus-utils</code> dependency into the plugin classpath, and Maven 3.x
continued doing this to preserve backward compatibility. Starting with Maven
3.9, it does not happen anymore. This change may lead to plugin breakage. The
fix for affected plugin maintainers is to explicitly declare a dependency on
<code>plexus-utils</code>. The workaround for affected plugin users is to add
this dependency to plugin dependencies until issue is fixed by the affected
plugin maintainer. See <a href="https://issues.apache.org/jira/browse/MNG-6965";
class="externalLink">MNG-6965</a>.</li>
<li>Mojos are prevented to boostrap new instance of
<code>RepositorySystem</code> (for example by using deprecated
<code>ServiceLocator</code>), they should reuse <code>RepositorySystem</code>
instance provided by Maven instead. See <a
href="https://issues.apache.org/jira/browse/MNG-7471";
class="externalLink">MNG-7471</a>.</li>
<li>Each line in <code>.mvn/maven.config</code> is now interpreted as a single
argument. That is, if the file contains multiple arguments, these must now be
placed on separate lines, see <a
href="https://issues.apache.org/jira/browse/MNG-7684";
class="externalLink">MNG-7684</a>.</li>
+<li>System and user properties handling cleanup, see <a
href="https://issues.apache.org/jira/browse/MNG-7556";
class="externalLink">MNG-7556</a>. As a consequence, this may introduce
breakage in environments where the user properties were used to set system
properties or other way around, for example see <a
href="https://issues.apache.org/jira/projects/MNG/issues/MNG-7887";
class="externalLink">MNG-7887</a>.</li>
</ul></section></section><section>
<h2>Known Issues</h2>
<p>None.</p></section><section>
Modified: maven/website/content/docs/3.9.3/release-notes.html
==============================================================================
--- maven/website/content/docs/3.9.3/release-notes.html (original)
+++ maven/website/content/docs/3.9.3/release-notes.html Fri Sep 22 11:26:23 2023
@@ -191,6 +191,7 @@ pages for more.</li>
<li>Maven 2.x was auto-injecting an ancient version of
<code>plexus-utils</code> dependency into the plugin classpath, and Maven 3.x
continued doing this to preserve backward compatibility. Starting with Maven
3.9, it does not happen anymore. This change may lead to plugin breakage. The
fix for affected plugin maintainers is to explicitly declare a dependency on
<code>plexus-utils</code>. The workaround for affected plugin users is to add
this dependency to plugin dependencies until issue is fixed by the affected
plugin maintainer. See <a href="https://issues.apache.org/jira/browse/MNG-6965";
class="externalLink">MNG-6965</a>.</li>
<li>Mojos are prevented to bootstrap new instance of
<code>RepositorySystem</code> (for example by using deprecated
<code>ServiceLocator</code>), they should reuse <code>RepositorySystem</code>
instance provided by Maven instead. See <a
href="https://issues.apache.org/jira/browse/MNG-7471";
class="externalLink">MNG-7471</a>.</li>
<li>Each line in <code>.mvn/maven.config</code> is now interpreted as a single
argument. That is, if the file contains multiple arguments, these must now be
placed on separate lines, see <a
href="https://issues.apache.org/jira/browse/MNG-7684";
class="externalLink">MNG-7684</a>.</li>
+<li>System and user properties handling cleanup, see <a
href="https://issues.apache.org/jira/browse/MNG-7556";
class="externalLink">MNG-7556</a>. As a consequence, this may introduce
breakage in environments where the user properties were used to set system
properties or other way around, for example see <a
href="https://issues.apache.org/jira/projects/MNG/issues/MNG-7887";
class="externalLink">MNG-7887</a>.</li>
</ul></section></section><section>
<h2>Known Issues</h2>
<ul>
Modified: maven/website/content/docs/3.9.4/release-notes.html
==============================================================================
--- maven/website/content/docs/3.9.4/release-notes.html (original)
+++ maven/website/content/docs/3.9.4/release-notes.html Fri Sep 22 11:26:23 2023
@@ -172,6 +172,7 @@
<li>Maven 2.x was auto-injecting an ancient version of
<code>plexus-utils</code> dependency into the plugin classpath, and Maven 3.x
continued doing this to preserve backward compatibility. Starting with Maven
3.9, it does not happen anymore. This change may lead to plugin breakage. The
fix for affected plugin maintainers is to explicitly declare a dependency on
<code>plexus-utils</code>. The workaround for affected plugin users is to add
this dependency to plugin dependencies until issue is fixed by the affected
plugin maintainer. See <a href="https://issues.apache.org/jira/browse/MNG-6965";
class="externalLink">MNG-6965</a>.</li>
<li>Mojos are prevented to bootstrap new instance of
<code>RepositorySystem</code> (for example by using deprecated
<code>ServiceLocator</code>), they should reuse <code>RepositorySystem</code>
instance provided by Maven instead. See <a
href="https://issues.apache.org/jira/browse/MNG-7471";
class="externalLink">MNG-7471</a>.</li>
<li>Each line in <code>.mvn/maven.config</code> is now interpreted as a single
argument. That is, if the file contains multiple arguments, these must now be
placed on separate lines, see <a
href="https://issues.apache.org/jira/browse/MNG-7684";
class="externalLink">MNG-7684</a>.</li>
+<li>System and user properties handling cleanup, see <a
href="https://issues.apache.org/jira/browse/MNG-7556";
class="externalLink">MNG-7556</a>. As a consequence, this may introduce
breakage in environments where the user properties were used to set system
properties or other way around, for example see <a
href="https://issues.apache.org/jira/projects/MNG/issues/MNG-7887";
class="externalLink">MNG-7887</a>.</li>
</ul></section></section><section>
<h2>Complete Release Notes</h2>
<p>See <a href="../../docs/history.html">complete release notes for all
versions</a></p></section></section>
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
