-
Notifications
You must be signed in to change notification settings - Fork 188
Open
Description
Description of the bug
When a new hilla application is created fron scratch, and we add a new view (via copilot), re-building the app does not show the new view. Not tested whether changing the view and re-building works.
I have tested with maven compiler + spring-boot live-reload.
Note that this was working in beta4
Expected behavior
app works like in beta4
Minimal reproducible example
- Create a new app and bump versions
curl -s \
'https://start.spring.io/starter.zip?type=maven-project&language=java&bootVersion=3.4.3&baseDir=initializer-vaadin-maven-react&groupId=com.vaadin.initializer&artifactId=initializer-vaadin-maven-react&name=initializer-vaadin-maven-react&description=initializer-vaadin-maven-react&packageName=com.vaadin.initializer&packaging=jar&javaVersion=21&dependencies=vaadin,devtools' \
--output initializer-vaadin-maven-react.zip
perl -pi -e 's|(\s*<'vaadin.version'>)[^\s]+(</'vaadin.version'>)|${1}25.0.0-beta4${2}|g' \
pom.xml
perl -0777 -pi -e 's|(\s+)(<parent>\s*<groupId>)(org.springframework.boot)(</groupId>\s*<artifactId>)(spring-boot-starter-parent)(</artifactId>\s*)(?:(<version>)([^<]+)(</version>))?(\s*)(.*?)?(\s*</parent>)|${1}${2}'org.springframework.boot'${4}'spring-boot-starter-parent'${6}${7}4.0.0-RC2${9}${10}${11}${12}|msg' \
pom.xml
perl -0777 -pi -e 's|(\n[ ]*)(</dependencies>\s+<build>)|$1 <dependency>$1 <groupId>com.vaadin</groupId>$1 <artifactId>hilla-spring-boot-starter</artifactId>$1 <scope>compile</scope>$1 </dependency>$1$2|' \
pom.xml
echo 'spring.devtools.livereload.enabled=true' >> src/main/resources/application.properties
- Run the app
./mvnw spring-boot:run
-
Open the Browser and click on the link 'create new hilla view'
-
Recompile in a separated terminal
./mvnw compile
- Reload the browser after a while, new view is not shown
Versions
- Vaadin version: 25.0.0-beta5
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
🔎 Investigation
Status
🪵Product backlog