Skip to content

Upgrading gradle project to Spring boot 3.1.8 from 2.4.8 : When bootJar is disabled, gradle build command generated artifact name has -plain added to it in spring boot 3 #39523

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

Closed
SabeetaBhandari opened this issue Feb 12, 2024 · 1 comment
Labels
status: invalid An issue that we don't feel is valid

Comments

@SabeetaBhandari
Copy link

SabeetaBhandari commented Feb 12, 2024

Compare gradle packaging in springboot 3.1.8 and springboot 2.4.8, when bootJar is disabled

When the spring boot version is '2.4.8' -> The artifact generated is 'artifactname.jar'
When the spring boot version is '3.1.8' -> The artifact generated is 'artifactname-plain.jar'

Notice the '-plain' classifier in artifact name after the upgrade.

It seems when bootJar is disabled, the generated jar doesn't have -plain in the artifact name in spring boot 2.4.8.
But when I upgrade springboot to '3.1.8', the artifact name is changed.

I know we can solve this by adding classifier= '' under jar task. But this extra step was not needed in spring boot 2.4.8 version.
This needs to be documented. I couldn't find any documentation related to it, exactly which version has this change.

Here is the reproducer code for this : https://github.com/SabeetaBhandari/gradle-packaging-test

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 12, 2024
@wilkinsona
Copy link
Member

It has been this way since Spring Boot 2.5 when it was documented in the release notes. It's also documented in the plugin documentation.

@wilkinsona wilkinsona closed this as not planned Won't fix, can't repro, duplicate, stale Feb 12, 2024
@wilkinsona wilkinsona added status: invalid An issue that we don't feel is valid and removed status: waiting-for-triage An issue we've not yet triaged labels Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

3 participants