[ 
https://issues.apache.org/jira/browse/MRESOLVER-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784124#comment-17784124
 ] 

ASF GitHub Bot commented on MRESOLVER-302:
------------------------------------------

cstamas commented on code in PR #357:
URL: https://github.com/apache/maven-resolver/pull/357#discussion_r1386903268


##########
maven-resolver-api/src/main/java/org/eclipse/aether/RepositorySystem.java:
##########
@@ -304,8 +314,26 @@ List<RemoteRepository> newResolutionRepositories(
      * When shutdown happens, all the registered on-close handlers will be 
invoked (even if some throws), and at end
      * of operation a {@link MultiRuntimeException} may be thrown, signaling 
that some handler(s) failed. This exception
      * may be ignored, is at the discretion of caller.
+     * <p>
+     * Note: this method actually just calls {@link #close()}.
      *
      * @since 1.9.0
+     * @deprecated Use {@link #close()} instead.
      */
+    @Deprecated
     void shutdown();
+
+    /**
+     * Signals to repository system to shut down. Shut down instance is not 
usable anymore.
+     * <p>
+     * Repository system may perform some resource cleanup, if applicable. Not 
using this method may cause leaks or
+     * unclean shutdown of some subsystem.
+     * <p>
+     * When shutdown happens, all the registered on-close handlers will be 
invoked (even if some throws), and at end
+     * of operation a {@link MultiRuntimeException} may be thrown, signaling 
that some handler(s) failed. This exception
+     * may be ignored, is at the discretion of caller.
+     *
+     * @since TBD
+     */
+    void close();

Review Comment:
   well, stop a bit: look at interface top and also read this: 
https://maven.apache.org/resolver/api-compatibility.html
   
   In short: no client is EVER intended to extend or implement this interface. 
IF someone shoots in his leg afterwards all these warnings, let it be, but is 
not our fault.



##########
maven-resolver-api/src/main/java/org/eclipse/aether/RepositorySystem.java:
##########
@@ -304,8 +314,26 @@ List<RemoteRepository> newResolutionRepositories(
      * When shutdown happens, all the registered on-close handlers will be 
invoked (even if some throws), and at end
      * of operation a {@link MultiRuntimeException} may be thrown, signaling 
that some handler(s) failed. This exception
      * may be ignored, is at the discretion of caller.
+     * <p>
+     * Note: this method actually just calls {@link #close()}.
      *
      * @since 1.9.0
+     * @deprecated Use {@link #close()} instead.
      */
+    @Deprecated
     void shutdown();
+
+    /**
+     * Signals to repository system to shut down. Shut down instance is not 
usable anymore.
+     * <p>
+     * Repository system may perform some resource cleanup, if applicable. Not 
using this method may cause leaks or
+     * unclean shutdown of some subsystem.
+     * <p>
+     * When shutdown happens, all the registered on-close handlers will be 
invoked (even if some throws), and at end
+     * of operation a {@link MultiRuntimeException} may be thrown, signaling 
that some handler(s) failed. This exception
+     * may be ignored, is at the discretion of caller.
+     *
+     * @since TBD
+     */
+    void close();

Review Comment:
   well, stop for a bit: look at interface top and also read this: 
https://maven.apache.org/resolver/api-compatibility.html
   
   In short: no client is EVER intended to extend or implement this interface. 
IF someone shoots in his leg afterwards all these warnings, let it be, but is 
not our fault.





> Introduce onSession close
> -------------------------
>
>                 Key: MRESOLVER-302
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-302
>             Project: Maven Resolver
>          Issue Type: Improvement
>          Components: Resolver
>            Reporter: Tamas Cservenak
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 2.0.0
>
>
> The on session close callback, revisited.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to