Archetype names should be designed to be consistent about archetypes

[vaadin-bot]

Originally by @Artur-

---

"vaadin-archetype"

• Everything in one. What is the use case for this? Isn't it more like you start with "server-ui" and then add an add-on -> you get a widget set. Also this seems to be server side in your list even though the name does not indicate it.

"server-ui-archetype"

• "application" might not be the best choice but "server-ui" is also kind of an internal term and does not tell much to a new user. Who should use it? Pretty much everybody who starts evaluating Vaadin or creating a Vaadin project.

"client-module"

• Shouldn't this then be more symmetrical with "server-ui", e.g. "client-ui" ? Or "server-application" and "client-application". I see no reason why we cannot talk about application even though there is no Application class anymore. With GWT you also create applications but use EntryPoint instead of an Application class.

[vaadin-bot]

Originally by @jojule

---

Agreed to your comments on naming of server-ui and client-module. These could be server-application and client-application.

The purpose of vaadin-archetype was to build an application skeleton that includes both client- and server-side parts. This is then a combination of the "server-application" and "client-application". The naming is chosen to indicate that this is the archetype you should choose if you do not know which one to choose - you can have the both or easily delete the side you are not using later on.

[vaadin-bot]

Originally by @Artur-

---

As we have agreed upon that you should always have the servlet available, there is no need for separate "client" and "server" application archetypes. The current "vaadin-application-archetype" can just aswell be used for client side development as for server side development.

[vaadin-bot]

Originally by @jojule

---

There are two (conflicting) problems with vaadin-application-archetype:

• Hello world it provides should compile without client-side complication cycle (thus empty widgetset should not be included)
• It should give an example / skeleton for client-side development. Preferably client-side widget, connector as well as entrypoint using that widget

[vaadin-bot]

Originally by @Artur-

---

A lot of tickets have been left hanging in the issue tracker through the years. Some of them are still relevant, some of them have been fixed a long time ago and some are no longer valid. To get a better look on what is important and still relevant, we are closing old tickets which have not been touched in a long time.

No further work will be done on this ticket unless someone indicates that it's still relevant.

If this ticket is still relevant to you, please reopen it.