You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if I create a project with vaadin-archetype-widget it is too difficult to run superdevmode.
What I'd expect to work is:
Run mvn clean install on root project
Run mvn jetty:run on widget-demo project
Run mvn vaadin:run-codeserver on widget-demo project
This does start up the superdevmode and it appears to be working but actually it does not notice client-side code changes in the widget project. I guess this is because it's using sources from the artifact in the local repo.
You can create an additional maven profile and include the sources from the widget project but this should happen automatically. Or at the very least document at vaadin.com/maven how to do this.
The text was updated successfully, but these errors were encountered:
There is a way to do this in the eclipse by running the SDM as a custom maven launch. You need to select "Resolve workspace artifacts". This thought depends on the jetty running with a compiled widgetset. After this the changes made in the widget module are seen upon reload in the UI.
Originally by @tepi
Currently if I create a project with vaadin-archetype-widget it is too difficult to run superdevmode.
What I'd expect to work is:
This does start up the superdevmode and it appears to be working but actually it does not notice client-side code changes in the widget project. I guess this is because it's using sources from the artifact in the local repo.
You can create an additional maven profile and include the sources from the widget project but this should happen automatically. Or at the very least document at vaadin.com/maven how to do this.
The text was updated successfully, but these errors were encountered: