[GitHub] [maven-resolver] gnodet commented on pull request #230: MRESOLVER-307 - Support listing of workspace artifacts

[GitBox <gi...@apache.org>]

gnodet commented on PR #230:
URL: https://github.com/apache/maven-resolver/pull/230#issuecomment-1352742772

   > It is a bit japicm as well, see here [siom79/japicmp#201](https://github.com/siom79/japicmp/issues/201)
   > 
   > But presence of "indirection" in form of support class allows us:
   > 
   > * to move iface from source to binary only compat check (then build would not fail)
   > * implement any newly added methods in support class, to retain source compatibility
   >   I bet there are cases like in Maven as well, but somewhere we have to start 😄
   
   I don't buy the argument that using a class solves the incompatibility problem.  If you add this class to the API, the exact same problem happens with the class.  You still have a possible source incompatibility.  I do think classes with default methods are useless, but for specific reasons (like you usually only want to implement a single method among a lot of methods, such as a listener interface).  For a more common interface, where you usually want to implement all methods, there's no benefit imho.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org