cstamas commented on PR #374:
URL: https://github.com/apache/maven-resolver/pull/374#issuecomment-1828652443

   I disagree with you, as MJAR in _this case_ is transparently handled by JDK 
classloader, as "Maven as resolver using code" in this case is completely 
oblivious (and should be oblivious) what is "changed" when running on different 
JDK versions. Moreover, the superiority of pattern that this PR replaced is 
visible in Central as well: 
   https://repo.maven.apache.org/maven2/org/apache/maven/resolver/
   
   Basically, each "constituent" JAR (along with proper bytecode) is deployed 
to Central, along with the `-jdk` MR one. This means, that consumer has a 
choice: to consume MR JAR or go directly for Java 11 without any fuss. IMHO, 
for libraries meant for downstream consumption, this is the cleanest and most 
"maven way" solution (and works in IDEs as well).


-- 
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-unsubscr...@maven.apache.org

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

Reply via email to