This commit improves TestImage so that an explicit image can trigger
the creation of the container, with optional additional setup. This
removes the need of creating additional container types for images that
have multiple flavors, and to please the static method that can only
create a container based on a single match.
Closes gh-51082
Added a new image cache option that uses the lifecycle's
`-cache-image` argument for the creator, analyzer, restorer and
exporter phases, so the build cache can be stored in an image and
shared between hosts via an image registry.
Exposed the option in the Maven (`<buildCache><image>`) and Gradle
(`buildCache { image { } }`) plugins.
Reject image caches configured for the launch cache, which the
lifecycle does not support.
See gh-50899
Signed-off-by: Tim Ysewyn <Tim.Ysewyn@me.com>
Previously, Spring Boot's Gradle plugin reacted to the Protobuf
plugin by configuring Protobuf's grpc plugin. This worked well for
projects using gRPC but went too far for those using Protobuf
without gRPC.
This commit dials the support back a little bit. Now, our recommended
gRPC defaults are only applied when Protobuf is configured with the
grpc plugin.
Closes gh-50822
Update `ProtobufPluginAction` to align the protoc version with
`protobuf-java` rather than `protobuf-java-util`. The util
jar is only required for server gRPC code.
See gh-50405
Signed-off-by: Dongliang Xie <dragonfsky@gmail.com>
There are two problems with the current approach:
1. The DSL uses dependsOn to try to inform Gradle of the dependency
relationship between tasks. This isn't recommended and inputs and
outputs should be used instead.
2. The generated build-info.properties file doesn't appear on the
classpath when running an application in an IDE, unless that IDE
delegates the execution to Gradle.
This commit addresses both of these shortcomings by configuring the
bootBuildInfo task's output to be a src dir of the main source set's
resources. This gives Gradle the preferred input- and output-based
view of the tasks' interdependencies. It also causes the generated
build-info.properties to appear on the classpath in IDEs that don't
delegate to Gradle. For example, the Eclipse Buildship plugin
automatically configures build/bootBuildInfo as a source folder on
the project's build path.
Closes gh-49547
Accumulate command line --environment values in a ListProperty and
merge them with the configured environment when building the
effective environment map. Add a test that verifies multiple entries
are accepted and propagated.
See gh-48792
Signed-off-by: HuitaePark <qkrgmlxo3174@gmail.com>
Wan bin yu
Stéphane Nicoll
Andy Wilkinson
Manu Sridharan
Phillip Webb
Tim Ysewyn
Dongliang Xie
Moritz Halbritter
HuitaePark