question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Hot deploy: Theme variant change only applied after full Maven rebuild

See original GitHub issue

Hot deploy issue: happens with IDE (IntelliJ) which is able to reuse something (resources or classes?) from the original project location even though it’s deployed to the web server.

Vaadin 14.0.0.rc4

I have the skeleton starter app, with @Theme(value = Lumo.class, variant = Lumo.LIGHT) added on the MainView class. I recompile the project with mvn clean package and launch the WAR file in Intellij+Tomcat. A white button on white background is properly shown.

Now I change the theme variant to dark as follows: @Theme(value = Lumo.class, variant = Lumo.DARK). The theme has not been changed, only the variant. I restart the Tomcat in Intellij, however the dark variant is not applied: the page still uses light theme, as can be seen on the body element: <body theme="light">. I need to run mvn clean package again, in order to actually activate the dark theme. That doesn’t make any sense since the theme is webpacked in in both variants, as can be seen in a browser: simply change the body element to <body theme="dark"> to have the dark theme applied.

It should not be necessary to do mvn clean package after the variant changes in the annotation - the change should be applied without having to run Maven.

Issue Analytics

  • State:open
  • Created 4 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
denis-anisimovcommented, Jul 15, 2019

Alright, now I got this. So this is kind of hot deploy issue. We have a bunch of issues related to this kind of functionality. I will update the title, thanks.

0reactions
mvysnycommented, Jul 15, 2019

Thanks! Yet I think it’s not necessarily a hot-redeploy: you can kill Tomcat, change the annotation and run Tomcat from scratch from Intellij, and the variant change would still not be applied to the app. A cold redeploy if you will 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

Maven building only changed files - java - Stack Overflow
And all the jars gets assembled in the module deploy. My question is if i change anything in services for example, then is...
Read more >
Server Developer Guide - Keycloak
To see the changes, open the login page for your realm. You will notice that the only styles being applied are those from...
Read more >
Optimize your build speed | Android Developers
Long build times slow down your development process. This page provides some techniques to help resolve build speed bottlenecks.
Read more >
Spring Boot Reference Documentation
Since you used the spring-boot-starter-parent POM, you have a useful run goal that ... and restarts are much quicker than a full rebuild...
Read more >
After modifying development files, the changes are not ... - IBM
If you make changes to the development files in a Maven-based portlet project in IBM Rational Application Developer (RAD), a "hot deployment" ( ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found