(as of September 2016)
The mixing of Maven and Eclipse Java EE and Java EE (I use CDI) creates lots problem. After suffering a lot I finally get things working right (seems to me at least at this moment).
(1) Stick to Maven
Install Vaadin Eclipse plugin, and create "Vaadin Maven" projects. Stick with Maven.
(2) Do not use Eclipse web tools
Do not rely on Eclipse web tools - that is, do not run / debug with "run as / run on server". I suffered a lot by doing this, all from the fact that the tool does not know things has changed: deleted class still in package, updated class not updated, etc., until restart Eclipse.
(3) Do
- I am using Wildfly to test my application, so far so good
- Configure Wildfly server
- add Wildfly plugin to Maven pom.xml, and remove jetty
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
<version>1.1.0.Alpha11</version>
</plugin>
- start debug by find the server in "servers" tab, right click and "debug", this starts an empty server in debug mode
- use "wildfly:deploy", "wildfly:redeploy", "wildfly:undeploy" to load application onto server to debug