Oleg Nenashev
04/05/2024, 1:59 PMbenedikt
04/05/2024, 2:06 PMbenedikt
04/05/2024, 2:07 PMbenedikt
04/05/2024, 2:11 PMbenedikt
04/09/2024, 7:14 AMjvm-dependency-conflict-resolution
. Are you up for trying to write up a PR for them?Thomas Broyer
04/09/2024, 3:07 PMThomas Broyer
04/09/2024, 3:11 PMOleg Nenashev
04/12/2024, 7:56 AMbenedikt
04/16/2024, 8:56 AMbenedikt
04/17/2024, 7:01 AMJendrik Johannes
04/25/2024, 2:23 PMorg.gradlex.gradlebuild.
. IIRC you introduced this pattern and I started to adopt that in other projects as well. E.g. if my project hast the namespace org.example
, I would use org.example.gradlebuild
.
Someone suggested to just use org.example.gradle
instead of org.example.gradlebuild
as the previous is shorter and the latter does not really add to it (gradle
is the build tool after all). Are there good arguments for using gradlebuild
instead of just gradle
?
(I think in the GradleX project it may make sense as there are so many things called Gradle, but what about other software projects?)