In order not to force vavr on consumers of this fine library, it'd be good, that vavr Types are replace from the API and replaced by their JDK counterparts.
If vavr is still used internally, maybe it is a good practice to shade & relocate the dependency, so that consumers can use their own version of vavr without conflict if they choose to.
In order not to force vavr on consumers of this fine library, it'd be good, that vavr Types are replace from the API and replaced by their JDK counterparts. If vavr is still used internally, maybe it is a good practice to shade & relocate the dependency, so that consumers can use their own version of vavr without conflict if they choose to.
https://maven.apache.org/plugins/maven-shade-plugin/examples/class-relocation.html