This message was deleted Gradle Community #community-support

Join Slack

This message was deleted.

# community-support

Slackbot

05/03/2023, 7:56 PM

This message was deleted.

Clayton Walker

05/03/2023, 7:58 PM

Additionally, adding a full number in front

Copy code

implementation("com.mycompany", "mylib", "1.release-125")

then we can get gradle to throw a resolution error

Copy code

> Could not find com.mycompany:my-lib:1.release-125.

Clayton Walker

05/03/2023, 7:59 PM

Are there different resolution/failure rules for when an version is number formatted vs alphabetically formatted?

ephemient

05/03/2023, 8:00 PM

https://docs.gradle.org/current/userguide/single_versions.html#version_ordering

ephemient

05/03/2023, 8:04 PM

although what you have is an empty base version with a

release-*

qualifier, which is quite confusing

ephemient

05/03/2023, 8:05 PM

actually I'm not sure if that's how it's parsed, hmm

Vampire

05/03/2023, 9:10 PM

Gradle does not interpret versions as semver. In that version

release

is the "major" version and

and

are the "minor" versions. It just splits versions at

, and

and additonally at the change between non-numeric and numeric, then the parts are compared. So

release-87

release-124

release-125

Vampire

05/03/2023, 9:11 PM

That 87 is picked when 125 is also requested, or that 125 is picked if 124 is requested and 125 not at all both make little sense to me and would need an MCVE

Clayton Walker

05/03/2023, 9:32 PM

I was able to reproduce it.

missing-dep-resolution.zip

Clayton Walker

05/03/2023, 9:32 PM

Copy code

gradle mylib1:pTML mylib2:pTML

will create 2 publications (published to ~/.m2) these will have 2 versions of the same artifact (release-124 and release-87)

Clayton Walker

05/03/2023, 9:33 PM

run

gradle :myconsumer:run

to see the output

Clayton Walker

05/03/2023, 9:33 PM

change the dependency version and the other jar will be picked up.

Vampire

05/03/2023, 9:49 PM

If that setup is comparable to your setup, I guess you have other problems. You should not have two projects that produce the same artifact coordinates. And if the consumer is in the same build too, I think the published artifacts are not used anyway, but the project dependencies directly.

Clayton Walker

05/03/2023, 9:51 PM

This in no way mirrors our setup, other than our versions being named

release-<build-number>

Clayton Walker

05/03/2023, 9:52 PM

And us being confused about the resolution rules wrt

Copy code

// why is release-125 completely ignored
implementation("com.mycompany", "mylib", "release-125")
implementation("com.mycompany", "mylib", "release-87")

Clayton Walker

05/03/2023, 9:55 PM

Basically

myconsumer

is the only part comparable to our setup. If you change

release-125

1.release-125

(for example) it’ll throw a dependency resolution error.

Vampire

05/03/2023, 10:04 PM

Actually, right away this does not make much sense to me and I'd tend to say it is a bug.

Vampire

05/03/2023, 10:07 PM

It seems, that at least for local directory repositories non-existing versions are ignored which seems to be wrong

Clayton Walker

05/03/2023, 10:13 PM

This is reproducible in remote repositories as well (I’ve verified release-125 is absent in our artifactory instance)

Vampire

05/03/2023, 10:19 PM

Hm, I guess it is too late for me to think properly, maybe @ephemient is fit enough to see more

Clayton Walker

05/03/2023, 10:20 PM

@Vampire I appreciate your insight and help.

👌 1

6 Views

Open in Slack

Previous Next