Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Note the Kt class name suffix when describing how to configure a Kotlin application's main class name #23418

Closed
wants to merge 1 commit into from

Conversation

fernandezseb
Copy link
Contributor

The purpose of this PR is to make it clearer that when Kotlin is used, the name of the main class is not equal to the name of the Kotlin class. This is unrelated with what language the Gradle build script is written in.

In issue gh-22664 this confusion was brought up.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Sep 20, 2020
@wilkinsona wilkinsona changed the title Add note about Kotlin main class name Add note about Kotlin main class name to the Gradle plugin's documentation Sep 21, 2020
@wilkinsona wilkinsona added type: documentation A documentation update and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 21, 2020
@wilkinsona wilkinsona added this to the 2.2.x milestone Sep 21, 2020
@wilkinsona wilkinsona changed the title Add note about Kotlin main class name to the Gradle plugin's documentation Note the Kt class name suffix when describing how to configure a Kotlin application's main class name Sep 21, 2020
@wilkinsona wilkinsona modified the milestones: 2.2.x, 2.2.11 Sep 21, 2020
wilkinsona pushed a commit that referenced this pull request Sep 21, 2020
wilkinsona added a commit that referenced this pull request Sep 21, 2020
@wilkinsona
Copy link
Member

Thanks very much, @fernandezseb. I've merged this into 2.2.x and then forwards so it'll be part of the next 2.3.x and 2.4.x releases as well.

@fernandezseb
Copy link
Contributor Author

@wilkinsona Thanks for your support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: documentation A documentation update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants