Re: How should I represent a library with two configurations in Maven Central?

On behalf of all ignorant people, thank you for explaining yourself. > On Sep 22, 2020, at 3:00 PM, Jörg Schaible wrote: > > On Tuesday, 22. September 2020, 23:05:12 CEST Alan Snyder wrote: >> I know that. But you also can’t exclude a dependency based on its version. >> >> So, what comparison a

Re: How should I represent a library with two configurations in Maven Central?

I know that. But you also can’t exclude a dependency based on its version. So, what comparison are you making? > On Sep 22, 2020, at 1:28 PM, Jörg Schaible wrote: > > On Tuesday, 22. September 2020, 01:13:11 CEST Alan Snyder wrote: >> I would still like to understand what you meant when you sai

Re: How should I represent a library with two configurations in Maven Central?

On Tuesday, 22. September 2020, 23:05:12 CEST Alan Snyder wrote: > I know that. But you also can’t exclude a dependency based on its version. > > So, what comparison are you making? You don't have to exclude a dependency based on its version, this does not make sense. Maybe you should make your

Re: How should I represent a library with two configurations in Maven Central?

You cannot exclude a dependency based on its classifier. Good point, never thought about that. One downside of "flavors" / "configurations" in the version is that you cannot filter them out properly with dependabot, e.g.: https://github.com/quarkusio/quarkus/pull/11961 ---

Re: How should I represent a library with two configurations in Maven Central?

On Tuesday, 22. September 2020, 01:13:11 CEST Alan Snyder wrote: > I would still like to understand what you meant when you said that > classifiers are worse then versions. You cannot exclude a dependency based on its classifier. Regards, Jörg --

Re: How should I represent a library with two configurations in Maven Central?

I would still like to understand what you meant when you said that classifiers are worse then versions. > On Sep 21, 2020, at 4:09 PM, Jörg Schaible wrote: > > > You won't have to exclude something. A user of your library will just add a > dependencyManagement section to his/her build and sel

Re: How should I represent a library with two configurations in Maven Central?

By implication, exclusions can work on versions? I have not seen any documentation that says this. Or are you talking about Gradle? > On Sep 21, 2020, at 2:19 PM, Jörg Schaible wrote: > > Using a classifier is worse, because exclusions do not work on classifiers. >

Re: How should I represent a library with two configurations in Maven Central?

You won't have to exclude something. A user of your library will just add a dependencyManagement section to his/her build and select there the version (with A or B) he/she wants. That will select the wanted version even if your lib is a transitive dependency. Am Dienstag, 22. September 2020,

Re: How should I represent a library with two configurations in Maven Central?

+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

Re: How should I represent a library with two configurations in Maven Central?

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 > I

How should I represent a library with two configurations in Maven Central?

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