vaadin-archetype-application generates a project without WEB-INF folder about archetypes

[vaadin-bot]

Originally by brunojcm

---

The tree got screwed on the description, here is what I first tried to do, sorry.

.
├── pom.xml
├── src
│   └── main
│       ├── java
│       │   └── com
│       │       └── example
│       │           └── vaadin_example
│       │               ├── AppWidgetSet.gwt.xml
│       │               └── MyVaadinUI.java
│       └── webapp
│           ├── META-INF
│           │   ├── context.xml
│           │   └── MANIFEST.MF
│           └── VAADIN
│               └── themes
│                   └── mytheme
│                       ├── addons.scss
│                       ├── favicon.ico
│                       ├── mytheme.scss
│                       └── styles.scss
└── target

[vaadin-bot]

Originally by @Artur-

---

The servlet configuration is specified inside MyVaadinUI.java, there is no need for a web.xml. If you want to use a web.xml instead of annotations, you always have to possibility to add a web.xml and remove the annotations.

[vaadin-bot]

Originally by brunojcm

---

Artur, the main problem with this approach is that some plugins like run-jetty-run don't recognize the project as a web project if this file is missing.

Could you consider having a more classic config in the archetype? Or a hybrid one?

For a lot of people (as happened with me) the first contact with some Vaadin code is using the archetype and this kind problem may upset some of potential users.