Hi :slightly_smiling_face:
I had some troubles du...
# package-authoringt
thankful-match-46035
06/03/2025, 11:31 AMHi 🙂
I had some troubles during build Java SDK that I resolved. Indeed we are using Java version 21 and gradle 8.8 (and not java 11 and gradle 7.x).
After having fixed the prblems, I am having another problem, during publishing Java SDK.
Indeed, the pulumi-package-publisher uses a old gradle version.
Is it possible to pass in parameter to the action the wanted gradle and java version?
thank you 🙂
thankful-match-46035
06/04/2025, 12:52 PM@adorable-house-61348 do you have an idea? thank you
a
adorable-house-61348
06/04/2025, 12:56 PMWe generally produce the SDKs with old java versions so that they are backwards compatible
adorable-house-61348
06/04/2025, 12:56 PMI suspect that's why the package-publisher uses that version
t
thankful-match-46035
06/04/2025, 1:14 PMOn our side we are using java 21 and gradle 8.8.
As we migrated to use pulumi-package-publisher and the GH workflows for upgrading provider, we are blocked because we can’t use gradle 7.7.
So, in the same way that we can specify node, java(...) versions, it should be logic to be allowed to specify gradle version.
a
adorable-house-61348
06/04/2025, 1:20 PMpulumi-package-publisher is an internal library but it's also open-source
adorable-house-61348
06/04/2025, 1:21 PMOn our side we are using java 21 and gradle 8.8.Using these forces your users to upgrade to java 21 and gradle 8.8
t
thankful-match-46035
06/04/2025, 2:20 PMno we launched Java SDK several monthes ago with gradle 8.8 and Java 21 so they don’t have to upgrade anything 🙂
a
adorable-house-61348
06/04/2025, 2:40 PMok, great to hear. Feel free to fork the publisher library and make any necessary changes - there's a 100 lines of code there or so