jvm-dependency-conflict-resolution

jvm-dependency-conflict-resolution copied to clipboard

- Appendix B is generated based on the `CapabilityDefinition` enum and contains **all** capabilities (and looks a bit crappy) - Appendix C is manually maintained and contains **only logging** capabilities...

jjohannes

Discussions are not enabled for this repo so I open an issue for that, sorry. I'm wondering about [patching metadata of published components](https://github.com/gradlex-org/jvm-dependency-conflict-resolution/blob/e7ba421270ccc0247e186634eb5e85bee033b1e4/src/docs/asciidoc/parts/resolution.adoc#patch-metadata-of-published-components). Especially the `removeDependency` - how is that...

boris-petrov

I have ``` jvmDependencyConflicts { conflictResolution { select(CapabilityDefinition.JAVAX_ACTIVATION_API, "jakarta.activation:jakarta.activation-api") } } ``` but still I get ``` > Could not resolve all files for configuration ':cli:funTestCompileClasspath'. > Could not resolve...

sschuberth

See: * ljacomet/logging-capabilities#16

ljacomet

See: * ljacomet/logging-capabilities#17

ljacomet

See: * ljacomet/logging-capabilities#2

ljacomet

See: * ljacomet/logging-capabilities#32

ljacomet

See: * ljacomet/logging-capabilities#35 Might relate to: * #119

ljacomet

See: * ljacomet/logging-capabilities#39

ljacomet

Clarify on preferred way to configure conflict resolutions

2

The docs both mention ``` configurations.all { resolutionStrategy.capabilitiesResolution { withCapability("javax.mail:mail") { // Capability for which to make the decision select("com.sun.mail:jakarta.mail:0") // The component to select } } } ``` and...

sschuberth