Fix description of build-image[-no-fork] Maven plugin goals

See gh-35609
pull/35611/head
Thomas Kåsene 2 years ago committed by Stephane Nicoll
parent 72fd94f2b5
commit e84025b1b8

@ -22,10 +22,10 @@ import org.apache.maven.plugins.annotations.Mojo;
import org.apache.maven.plugins.annotations.ResolutionScope;
/**
* {@link BuildImageMojo implementation} that forks the lifecycle to make sure that
* {@code package} ran. This goal is suitable for command-line invocation. If you need to
* configure a mojo {@code execution} in your build, use {@link BuildImageNoForkMojo}
* instead.
* Package an application into an OCI image using a buildpack, forking the lifecycle to
* make sure that {@code package} ran. This goal is suitable for command-line invocation.
* If you need to configure a goal {@code execution} in your build, use
* {@code build-image-no-fork} instead.
*
* @author Stephane Nicoll
* @since 3.0.0

@ -21,10 +21,10 @@ import org.apache.maven.plugins.annotations.Mojo;
import org.apache.maven.plugins.annotations.ResolutionScope;
/**
* {@link BuildImageMojo implementation} that does not fork the lifecycle to make sure
* that {@code package} ran. This goal should be used when configuring a mojo
* {@code execution} in your build. To invoke the goal on the command-line, use
* {@link BuildImageForkMojo} instead.
* Package an application into an OCI image using a buildpack, but without forking the
* lifecycle to make sure that {@code package} ran. This goal should be used when
* configuring a goal {@code execution} in your build. To invoke the goal on the
* command-line, use {@code build-image} instead.
*
* @author Stephane Nicoll
* @since 3.0.0

Loading…
Cancel
Save