Vaadin 24.4.12 Building on windows takes over an hour, mac m2 les than a minute

Hilla
21

Small update:
So i tried copy pasting a file during debugging from a starter project, which is much smaller.

afbeelding
afbeelding1891×761 207 KB

And this works, most likely the file I have is too big for windows to handle through stdin through the method used by Java.

Which explains why it started happening as I created more hilla browser callables in the project.

23

Could you please share json file? Or, if it cannot be posted online, some additional details about it, like the size, how many endpoints methods are exposed, …?

This would probably help the Hilla team investigating the issue

25

Hi

I was able to create a replication application.

It can be found here: GitHub - DuncanCasteleyn/replicate-buffer-issue: Replication for the buffer isue with openapi file

1 Like
26

Currently I’m working around this issue by running wsl ./gradlew -Philla.productionMode=true bootjar, so essentially running in WSL.

27

Could you please try running ./gradlew -Pvaadin.productionMode=true build instead to see if it makes a difference?
Since 24.4 (when Hilla got integrated into Vaadin Platform) the Vaadin Gradle plugin changed to take the options from vaadin extension object into account and not the hilla one anymore.

28

I already replaced it with what you metioned, on WSL it still works. The documentation is outdated though: Using Gradle in Hilla applications

Made a fix proposal: fix(gradle): replace outdated properties from hilla to vaadin by DuncanCasteleyn · Pull Request #3716 · vaadin/docs · GitHub

Additionally running in windows through cmd as expect causes infinite IDLE:

afbeelding
afbeelding723×113 13.2 KB

1 Like
29

Was a fixed added to the latest version of Vaadin? Since I updated the issue seems to have been resolved.

30

Upgrading to v24.5.0 resolved the issue.

2 Likes