This message was deleted.

have you tried this? the first for is for an external dependency; the second is for a project dependency. Providing invalid dependency notation (or an invalid project path) will fail.

it is not failing it works,

If the group is not set for the project the coordinates are correct and it will be substituted by the project dependeny automatically

thx @Vampire, The group is set only on the root project (and not set on all the other subprojects) also can you explain on the difference between the two forms ?

I did

It’s as I described - it just happens to “coincidentally” work as there is no group, so ’:projY` matches the dependency coordinates for that project and is resolved as a dependency

First form is just usual

group:artifact:version

notation with empty group and no version. Which is then automatically substituted by the project dependency that builds the artifact with those coordinates

thank you