Skip to content

Converts the build to Gradle Kotlin DSL#14155

Open
tresat wants to merge 2 commits intotriplea-game:mainfrom
tresat:tt/build/convert-build-to-kotlin-dsl
Open

Converts the build to Gradle Kotlin DSL#14155
tresat wants to merge 2 commits intotriplea-game:mainfrom
tresat:tt/build/convert-build-to-kotlin-dsl

Conversation

@tresat
Copy link
Contributor

@tresat tresat commented Feb 16, 2026

There should be zero behavior changes from this.

@tresat tresat force-pushed the tt/build/convert-build-to-kotlin-dsl branch from d4b5521 to 3c016ed Compare March 12, 2026 23:04
@tresat tresat marked this pull request as ready for review March 12, 2026 23:04
Copy link
Member

@frigoref frigoref left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some one typo and an idea to improve transparency about TripleA configurations by introducting constants.

Gradle plugins used by the build are located in `/gradle/build-logic`.

The build uses the Gradle Kotlin DSL.
This make the build easier to maintain by increasing the completion and refactoring assistance the IDE is able to provide.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"makes"

maven(MavenPublication) {
artifact(tasks.named(sourceSets.main.jarTaskName)) {
extension 'jar'
create<MavenPublication>("maven") {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we work with constants here for which their names can help to understand better what this is?

extension 'jar'
create<MavenPublication>("maven") {
artifact(tasks.named(sourceSets.main.get().jarTaskName)) {
extension = "jar"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't we have a constant for that already?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is just a copy of the previous build.gradle, right?
Should we try to declare constants there as well with another commit or another PR?
I'd suggest to have at least constants for what is "TripleA configuration" like paths even though we keep strings for what is "Kotlin configuration" like plugins. What do you think?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also here, maybe some constants would help.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also here, maybe some constants would help.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also here, maybe some constants would help.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also here, maybe some constants would help.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also here, maybe some constants would help.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also here, maybe some constants would help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants