+1 Use version suffixes, and think about deploying Gradle Module Metadata so Gradle users can see them as variants of one another and more accurately pick a version: https://docs.gradle.org/current/userguide/publishing_gradle_module_metadata.html and e.g. https://github.com/google/guava/pull/3683
Le lun. 21 sept. 2020 à 23:18, Jörg Schaible <[email protected]> a écrit : > Hi Alan, > > On Sonday, 20. September 2020, 23:50:21 CEST Alan Snyder wrote: > > I’ve posted a question on StackOverflow that has not yet been answered. > > Perhaps someone here has an answer? > > > > https://stackoverflow.com/q/63906798/1652984?sem=2 > > <https://stackoverflow.com/q/63906798/1652984?sem=2> > > If it is A or B exclusively, use the alternatives as part of the version > string. See > - postgres (https://search.maven.org/artifact/org.postgresql/postgresql[1] > ) > - xstream ( > https://search.maven.org/artifact/com.thoughtworks.xstream/xstream[2] ) > > Bouncycaste uses the alternative as part of the artifactId: > - https://search.maven.org/search?q=g:org.bouncycastle[3] > > However, I have often to "manage" 3rd party libraries manually that > reference one of the > BC artifacts that should not be used together by using exclusions. > > Using a classifier is worse, because exclusions do not work on classifiers. > > Regards, > Jörg > > -------- > [1] https://search.maven.org/artifact/org.postgresql/postgresql > [2] https://search.maven.org/artifact/com.thoughtworks.xstream/xstream > [3] https://search.maven.org/search?q=g:org.bouncycastle >
