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

slachiewicz pushed a commit to branch maven-resolver-1.9.x
in repository https://gitbox.apache.org/repos/asf/maven-resolver.git


The following commit(s) were added to refs/heads/maven-resolver-1.9.x by this 
push:
     new 2603328e0 Point 1.9.x readers at the Resolver 2.x upgrade guide
2603328e0 is described below

commit 2603328e086e4ba74027557e179bdc56104449f6
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Sat Nov 7 22:55:15 2026 +0100

    Point 1.9.x readers at the Resolver 2.x upgrade guide
---
 src/site/markdown/api-compatibility.md        | 4 ++--
 src/site/markdown/third-party-integrations.md | 5 +++--
 src/site/xdoc/index.xml                       | 4 +++-
 3 files changed, 8 insertions(+), 5 deletions(-)

diff --git a/src/site/markdown/api-compatibility.md 
b/src/site/markdown/api-compatibility.md
index 14290f1d3..fbb54ff32 100644
--- a/src/site/markdown/api-compatibility.md
+++ b/src/site/markdown/api-compatibility.md
@@ -57,7 +57,7 @@ If a Java package contains following names:
 That Java package is meant as "internal" and does NOT offer guarantees of 
compatibility as API is. You
 may use classes from these packages, but again, you are on your own to deal 
with (binary or source)
 breakages. If you think a class from such package should be "pulled out" and 
made part of SPI or
-maybe API, better inform us via 
[JIRA](https://issues.apache.org/jira/projects/MRESOLVER): create a
+maybe API, better inform us via 
[GitHub](https://github.com/apache/maven-resolver/issues): create a
 ticket and let's discuss.
 
 As a side note, the count of those names in Java package is directly 
proportional to possibility of 
@@ -73,7 +73,7 @@ semantics:
 * On minor version change, we TRY to keep backward compatibility for those 
"exposed" 3 modules: 
   API, SPI and Util. Still, there are examples when we failed to do so, 
usually driven by new 
   features.
-* On minor version change, we ENSURE backward compatibility for those 
"exposed" 3 modules: API, 
+* On patch version change, we ENSURE backward compatibility for those 
"exposed" 3 modules: API, 
   SPI and Util.
 
 In any of three version changes above, in areas where we do not offer 
guarantees, everything
diff --git a/src/site/markdown/third-party-integrations.md 
b/src/site/markdown/third-party-integrations.md
index 9a96771c9..d083a2562 100644
--- a/src/site/markdown/third-party-integrations.md
+++ b/src/site/markdown/third-party-integrations.md
@@ -22,13 +22,14 @@ Maven was the Plexus DI container, that had its own 
limitations: no constructor
 among others. Hence, the two was somewhat aligned with each other. Today, with 
Sisu DI, 
 this is not true anymore: we want to use constructor injection for components, 
but
 SL is always getting into our way forcing us to always add default constructor 
to components.
-Hence, decision was made, and SL was deprecated while ago, and is about to be 
-dropped in Resolver 2.0.0 release.
+Hence, decision was made, and SL was deprecated while ago, and was
+dropped in the Resolver 2.0.0 release.
 
 Resolver does provide alternative solution for those third-party integrations, 
where the
 (recommended) Sisu DI is not available or cannot be used for some reason. All 
the
 resolver integrations starting with release 1.9.15 can start migrating off the 
SL
 to current solution described below.
+In Resolver 2.x the module below is named `maven-resolver-supplier-mvn3`; the 
class and its use are the same.
 
 ## Maven Resolver Supplier
 
diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml
index 311dfc8cc..fd1d88c6e 100644
--- a/src/site/xdoc/index.xml
+++ b/src/site/xdoc/index.xml
@@ -29,7 +29,9 @@
   <body>
 
     <section name="Apache Maven Artifact Resolver">
-      <p style="font-size: 14pt; font-style: bold">Since version 1.7.0 Maven 
Resolver requires Java 8 to run. For a Maven 3.8.x compatible version read <a 
href="./maven-3.8.x.html">here</a>.</p>
+      <p style="font-size: 14pt; font-style: bold">This is the documentation 
of the Maven Resolver 1.9.x maintenance line, the line that Maven 3.9.x bundles.
+        Maven 4 bundles Resolver 2.x; its documentation, including the <a 
href="https://maven.apache.org/resolver/upgrading-resolver.html";>guide for 
upgrading from 1.x to 2.x</a>, is at <a 
href="https://maven.apache.org/resolver/";>maven.apache.org/resolver</a>.</p>
+      <p>Since version 1.7.0 Maven Resolver requires Java 8 to run. For a 
Maven 3.8.x compatible version read <a href="./maven-3.8.x.html">here</a>.</p>
       <p>Apache Maven Artifact Resolver is a library for working with artifact 
repositories and dependency resolution.</p>
       <p>Maven Artifact Resolver deals with the specification of local 
repository, remote repository, developer workspaces, artifact transports, and 
artifact resolution. It is expected to be extended by a concrete repository 
implementation, such as
         <a href="/ref/current/maven-resolver-provider/">Maven Artifact 
Resolver Provider</a> for Maven repositories

Reply via email to