Support packaging type of WAR when scaffolding a project

[Matthew-Dong]

[Matthew-Dong]

We'd like to recommend using Spring Initializr extension in VS Code as the entry point for Java developer experience when scaffolding a project. However, it only supports to generate a JAR project, which means large numbers of developers using Tomcat have to bring their own project to VS Code. This also caused an inconsistency in the tutorial.

[Eskibear]

@Matthew-Dong I thought the only difference was the value of <packaging>. So previous design is to let users modify it themselves after scaffolding.

It's feasible to allow users to select packaging type, but we should decide where to insert this step.
Current workflow is:

• Choose Maven/Gradle with different commands
• Select Language
• Input GroupId.
• Input ArtifactId.
• Select dependencies.
• Select a local folder to place extracted files.

[Eskibear]

Or do you prefer similar ways to handle language?

E.g. we can have a configuration instead of letting users to bother an extras step to select packaging type. By default, it can be JAR, if you want to generate WAR, use the settings.

  // Default packaging.
  "spring.initializr.defaultPackaging": "JAR",    // <--- candidates are "JAR", "WAR"

[Eskibear]

implemented.