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

Improve description of build-image and build-image-no-fork #35608

Closed
ThomasKasene opened this issue May 23, 2023 · 7 comments
Closed

Improve description of build-image and build-image-no-fork #35608

ThomasKasene opened this issue May 23, 2023 · 7 comments
Labels
status: superseded An issue that has been superseded by another

Comments

@ThomasKasene
Copy link
Contributor

I feel that the documentation for the spring-boot-maven-plugin's build-image and build-image-no-fork could be more informative. Currently, they only talk about the difference between the two goals in terms of forking, but not what they actually do and in which situations one might want to use them. The descriptions also seem to be more like JavaDoc than anything, as they're mentioning the different *Mojo class names, rather than the goal names.

@snicoll
Copy link
Member

snicoll commented May 23, 2023

Currently, they only talk about the difference between the two goals in terms of forking, but not what they actually do and in which situations one might want to use them.

What do you mean? Perhaps you can contribute a PR and we can take it from there?

@ThomasKasene
Copy link
Contributor Author

ThomasKasene commented May 23, 2023

Done 😃 (Assuming I edited the correct files)

@wilkinsona
Copy link
Member

wilkinsona commented May 23, 2023

The descriptions also seem to be more like JavaDoc than anything, as they're mentioning the different *Mojo class names, rather than the goal names.

Comparing the descriptions of spring-boot:build-image and spring-boot:build-image-no-fork with those of the other goals, they do read very differently. I think we should try to align them.

Currently, they only talk about the difference between the two goals in terms of forking, but not what they actually do and >> in which situations one might want to use them.

What do you mean? Perhaps you can contribute a PR and we can take it from there?

If @ThomasKasene can do it then great, but I'm not sure that we can expect a user to contribute a PR to document something that isn't well documented. It's a chicken and egg problem.

I think this overlaps a bit with the description reading like javadoc. For example:

If you need to configure a mojo execution in your build, use BuildImageNoForkMojo instead.

I don't think "mojo" really belongs here. I think "goal" would be a better term. Similarly, I think BuildImageNoForkMojo could be replaced by spring-boot:build-image.

@wilkinsona
Copy link
Member

It looks like this regressed in 3.0.x. The description of spring-boot:build-image is better in 2.7.x.

@ThomasKasene
Copy link
Contributor Author

I don't think "mojo" really belongs here. I think "goal" would be a better term. Similarly, I think BuildImageNoForkMojo could be replaced by spring-boot:build-image.

In #35609 I've replaced "mojo" with "goal" like you suggested. As for the goal names, I've omitted the spring-boot: prefix as the other goal descriptions don't use it when referring to other goals (for example, the spring-boot:start description mentions the run goal).

@snicoll
Copy link
Member

snicoll commented May 24, 2023

I'm not sure that we can expect a user to contribute a PR to document something that isn't well documented. It's a chicken and egg problem.

I asked for a PR because I didn't understand what the problem was and the OP seems to be positive in what was missing. I can see now what they meant.

@snicoll
Copy link
Member

snicoll commented May 24, 2023

Closing in favor of PR #35609. Thanks a lot for that @ThomasKasene

@snicoll snicoll closed this as not planned Won't fix, can't repro, duplicate, stale May 24, 2023
@snicoll snicoll added status: superseded An issue that has been superseded by another and removed status: waiting-for-triage An issue we've not yet triaged labels May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: superseded An issue that has been superseded by another
Projects
None yet
4 participants