I have three, semi-related questions:
-
When might the Documentation be updated for Vaadin 7? Much of the site’s examples are for Vaadin 6, and so much has changed in 7, that someone “new” (I used it a long time ago) is easily confused by the documentation saying one thing and it no longer being correct, or in some cases not saying enough. For example…
-
Widgets are explained in some respect, but not enough in my opinion with regards to Maven and/or an automated build process. For example, the mvn vaadin:compile goal must be executed prior to being able to use the simplest of Vaadin 7 app if created with the Maven archetype per the example at https://vaadin.com/download#dependency-management. However, I couldn’t find a good example or explanation as to why, or even if the Widgets are necessary in a simple app. They do not appear to be. I commented the Widget section from the web.xml file and the app (a simple click button to show text) worked fine. So when and why are widgets necessary and what is the proper way to integrate their compilation into the build process?
-
Which leads me to my final question. It seems that the widgets get compiled into a part of the source structure that would normally be committed to a SCM. Now, I can easily ignore that folder so it’s not checked in, but that raises the question, if that folder is necessary for deployment, can it be generated at runtime? In the case of Maven is there an easy way to redirect the VAADIN directory into Maven’s target directory so generated code isn’t placed into the /src structure?
Thank you!