Add Native Image Support in Spring Framework on Google Cloud

[mpeddada1]

While Spring Framework on Google Cloud 4.x adds compatibility for Spring Boot 3.0, we don't currently have support for native image compilation. This issue serves as an umbrella tracker to report on the status of this support in the repository.
Related Issues:

• Native compile failing with spring cloud GCP 4 and spring boot 3 #1559
• Datastore: spring-native support #1279

[filipenfst]

Is there any plans or timelines for you guys to work on this issue?

[Tera]

+1

[rkettelerij]

Would be nice wrt cloud run / cloud functions

[gomezmejiam]

stuck in this issue, we where making a work around using the gcp rest api via feign but it´s a lot of work and future manteniance

[jainsahab]

Hi everyone,

Thanks for showing interest in this feature.

we are planning to take up this work soon and will keep you updated about the progress.

[laurent-grousset]

Native compilation worked fine with Spring Boot 3 and spring-cloud-gcp-dependencies 3.4.0

[jleonar]

Native compilation worked fine with Spring Boot 3 and spring-cloud-gcp-dependencies 3.4.0

It doesn't with the latest version at spring-cloud-gcp-dependencies 4.1.1

[laurent-grousset]

@jainsahab moreover, Native execution is all the more important as it allows us to mitigate the cold start of Cloud Run running Spring Boot (this is my case)

[lutics]

any update on here?

[dangazineu]

Thank you for the interest. We don't have an ETA on this feature yet.

[pkutlunin]

I think I found the reason why in versions 4.x.x it stopped working - it's related to #1287 (upgrade to Spring boot 3.0.0).
As it was mentioned in #1559, the code no longer gets compiled with -parameters argument. If we take a look at the current version of maven-compiler-plugin, we'll see that the configuration is invalid:

spring-cloud-gcp/pom.xml

Line 523 in 4a1d4ec

<artifactId>${maven-compiler-plugin.version}</artifactId>

Because of the wrong artifact id, the configuration cannot be applied.
The fix should be easy:

<artifactId>maven-compiler-plugin</artifactId>
<version>${maven-compiler-plugin.version}</version>

Unfortunately, I couldn't make it work because of errorprone plugin configuration:

Compilation failure
[ERROR] error: invalid flag: -Xep:UnicodeInCode:OFF

If I remove these 2 flags, the project builds fine:

-Xep:UnicodeInCode:OFF \
-Xep:CanIgnoreReturnValue:OFF

Could you try if it works for you with the fix? Maybe it's just my local setup that causes issues with errorprone.

[burkedavison]

#1775 resolves the above compiler profile and ErrorProne configuration issues highlighted by @pkutlunin . These fixes are now available in Spring Cloud GCP 4.3.0.

[zhumin8]

We do not plan to support Native Image in Spring Framework on Google Cloud 4.x. Initial Native Image support is available in Spring Framework on Google Cloud 5.x.