-
Notifications
You must be signed in to change notification settings - Fork 40.9k
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
Comments
What do you mean? Perhaps you can contribute a PR and we can take it from there? |
Done 😃 (Assuming I edited the correct files) |
Comparing the descriptions of
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:
I don't think "mojo" really belongs here. I think "goal" would be a better term. Similarly, I think |
It looks like this regressed in 3.0.x. The description of |
In #35609 I've replaced "mojo" with "goal" like you suggested. As for the goal names, I've omitted the |
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. |
Closing in favor of PR #35609. Thanks a lot for that @ThomasKasene |
I feel that the documentation for the
spring-boot-maven-plugin
'sbuild-image
andbuild-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.The text was updated successfully, but these errors were encountered: