Vampire commented on issue #11442: URL: https://github.com/apache/maven/issues/11442#issuecomment-3536648833
> So far my experience with provided was provided servlet-api:servlet-api while in practice the runtime was weblogic.jar :) That's quite possible, but not different to other cases like `org.codehaus.groovy:groovy` vs. `org.apache.groovy:groovy`. Or also `javax.activation:activation`, `jakarta.activation:jakarta.activation-api`, `javax.activation:javax.activation-api`, `com.sun.activation:javax.activation`, and `com.sun.activation:jakarta.activation` which all contain the classes for the Activation API. See also https://github.com/gradlex-org/jvm-dependency-conflict-resolution/blob/dc82f98dd33433906571d96dd1c9f9652d101f42/src/main/java/org/gradlex/jvm/dependency/conflict/detection/rules/CapabilityDefinition.java for other popular examples. So yes, you cannot directly reason from provided coordinates to a jar. But in some cases it matches. In others you could have a manual mapping wich jar provides the classes of which other dependency. In yet other cases you could get the provided dependency, list all classes in there, list all classes in the runtime classpath and check whether the first is a subset of the second. There are many ways to use this information in a good way. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
