This message was deleted.
# community-support
s
This message was deleted.
šŸ™Œ 1
z
I’m not sure of the question
but just make a
:buildSource
folder and include it
e
The article I read recommends against a
buildSrc
directory, and the GitHub project does not use it either. The question is, "in light of the two references, do people still recommend
buildSrc
and why?" It's more of an opinion question than right or wrong question.
🚱 1
m
I don't think anyone recommends
buildSrc
these days
ā˜ļø 2
āœ… 1
e
Thanks, @Martin, I am taking Tom Gregory's Gradle course, so it may be a little outdated, or I have just not gotten to the end of the course yet.
m
I don't know this specific course but yeah things change fast. There are still occurrences in the Gradle doc too
e
Oh, yea... one of my central problems is how rapidly Gradle evolves and how much out-of-date documentation Google search finds... šŸ™„
m
Official doc is good but yea lagging a bit sometimes in terms of best practices
https://youtube.com/playlist?list=PLWQK2ZdV4Yl2k2OmC_gsjDpdIBTN0qqkE is my source of truth these days for best practices
šŸ™Œ 1
āœ… 1
e
I am playing with Gradle 8.0, and trying to learn from that documentation. Already I can see the improvements in that documentation.
c
This doc is probably the first one people see when googling convention plugins in gradle, and it still uses buildSrc
šŸ™„ 1
šŸ‘ 1
e
Yup, that is how I started using
buildSrc
and it's still there in 8.0 documentation...
m
@Clayton Walker yea, that's a pain. I wanted to make a PR at some point but I don't think the docs are open source:-(
e
I am documenting what I am learning in a
GRADLE-CONVENTIONS.md
file in my project.
e
You can contribute to the docs here. šŸ™‚ https://github.com/gradle/gradle/tree/master/subprojects/docs
šŸ™Œ 1
āœ… 2
PRs are very much welcome!
šŸ‘ 1
😁 1
e
How is the Gradle knowledge in chatGPT coming along? šŸ˜‰ Actually, a lot of chatGPT is out of date too, but not as bad as Google search...
e
Well I do know it can write some good poems about Gradle. šŸ™‚ https://gradle-community.slack.com/archives/CRA9GTYBH/p1669800149275429
😁 1
ā¤ļø 1
e
Yup, chatGPT is out-of-date...
c
So considering the work done in https://github.com/gradle/gradle/issues/2531#issuecomment-1354506556, what would be the status of recommending includeBuild over buildSrc? Or would this not change the recommendation.
šŸ‘€ 3
e
Okay, I am trying to follow
Copy code
<https://github.com/jjohannes/idiomatic-gradle>
There is a lot of setup involved... a lot of complexity going on
z
Set up convention plugins, that's the key thing
e
Yep... going slow as I am apt to make typos...
I see similarities in using
buildSrc
but way more intense...
Extreme 'separation of concerns' -- not that that's a bad thing...
z
BuildSrc is literally the same thing minus a few behavior differences
e
Yup...
It makes me a little nervous to overload the _project_/gradle directory as thought that was only used for _project_/gradle/wrapper files... But, this old dog can still learn a few new tricks...
z
Why would you ever do that
e
Learn new tricks? Or overload the _project_/gradle directory -- because that is what the idiomatic gradle GitHub project does...
z
Who cares what directory is used for an included build
e
I am just following the conventions I see before me... and will reflect on deeper philosophy later...