This message was deleted.
# community-supports
Slackbot
06/29/2022, 2:49 PMThis message was deleted.
d
Don谩t Csik贸s
06/29/2022, 3:01 PMHi! 馃憢 I see Louis responded faster than me.
e
Eugen Mayer
06/29/2022, 3:02 PMNot a lot though 馃檪
d
Don谩t Csik贸s
06/29/2022, 3:03 PMI can only say the same thing. I understand the problem, but chances are, there are particular things in your project that cause the issue. Without a reproducer the time spent on just recreating the issue could be huge.
e
Eugen Mayer
06/29/2022, 3:04 PMWell let's put it this way, we do include 1 project with 5 subprojects. 4 subprojects cannot be resolved using the gradle configuration (group-id/project name), but one can.
Eugen Mayer
06/29/2022, 3:05 PMLooking at the substitution, 1 is not substituted, 4 are. Changing the sub-project-name of the not substituted to something else, so the project-name no longer matches the artifact-id instantly solved the issue. This aspect has been seen in 2 different main-project that include this library-project
Eugen Mayer
06/29/2022, 3:06 PMSo i would say, that one is fairly sure no longer a project configuration issue or a local issue, that one is for sure a gradle bug. Considering the scenario it broke (1 of 5) and it could be fixed with the exact same idea.
v
Vampire
06/29/2022, 3:15 PMI don't think Don谩t wanted to imply it is not a Gradle bug.
Just that your setup trips some edge-case to trigger the bug.
And that you should provide a reproducer with which they can investigate the issue, as otherwise it is not too clear how to reproduce the issue. 馃槈
馃憤 1
2 Views