Bump version to 0.4.0 (#78)

* Bump version to v0.4.0

* Update thirdpartynotice.

* Update changelog for v0.4.0.

* Put test plan docs into repo.

CHANGELOG.md

@@ -1,9 +1,12 @@
 # Change Log
 All notable changes to the "vscode-spring-initializr" extension will be documented in this file.
 
-## Unreleased
-
 ## Released
+### 0.4.0
+- Supported to specify packaging type. [#68](https://github.com/Microsoft/vscode-spring-initializr/issues/68)
+- Created a base directory named after the artifact Id. [#72](https://github.com/Microsoft/vscode-spring-initializr/issues/72)
+- Fixed some bugs.
+
 ### 0.3.0
 - Supported to edit starters of an existing Spring Boot Maven project.
 - Supported to generate Kotlin and Groovy projects. 

TestPlan.md

@@ -0,0 +1,89 @@
+# Generate a Maven Project
+
+**Quickstart with dependency search**
+
+1. Open VS Code without opening any folder.
+1. Open `Command Palette`, execute command `Spring Initializr: Generate a Maven Project`.
+1. Input a invalid `Group Id`, verify:
+    1. It doesn't pass the validation.
+1. Input a valid `Group Id`, e.g. `com.microsoft.example`, press `<Enter>`.
+1. Input a invalid `Artifact Id`, verify:
+    1. It doesn't pass the validation.
+1. Input a valid `Artifact Id`, e.g. `sample-artifact`, press `Enter`.
+1. Select a version, verify:
+    1. It lists compatible dependencies for the specified version you selected.
+1. Select some dependencies, verify:
+    1. Selected dependency is entitled by a check mark, and is placed ahead of the dependency list.
+    1. Can cancel the selection by pressing `<Enter>` on a selected dependency.
+    1. The first entry is `Selected # dependency(ies)`, and `#` is the number of seleted entries.
+1. Press `<Enter>` on `Selected # dependency(ies)`, verify:
+    1. It pops up a directory-selection dialog.
+1. Choose a target folder, verify:
+    1. During generating, it shows process in status bar.
+    1. After the process disappear, it shows a information message box on the top.
+1. Click `Open it`, verify:
+    1. It opens the project in current window.
+1. Open `pom.xml` in root folder, verify:
+    1. `Group Id` and `Artifact Id` are correct.
+    1. Selected dependencies are added under `<dependencies>` tag.
+1. Verify the folder structure is organized as `Group Id`.
+
+**Quickstart with last settings**
+
+1. Open `Command Palette`, execute command `Spring Initializr: Generate a Maven Project`.
+1. Input a valid `Group Id`, e.g. `com.microsoft.example`, press `<Enter>`.
+1. Input a valid `Artifact Id`, e.g. `sample-artifact`, press `Enter`.
+1. Press `<Enter>` on `Use Last Settings`, verify:
+    1. The dialog shows the dependeny(ies) name in last settings.
+1. Choose a target folder, open it and verify the `pom.xml`, using same steps above. 
+
+
+# Generate a Gradle Project
+
+Same steps with above, but using command `Spring Initializr: Generate a Gradle Project`.
+
+After that, verify `build.gradle` instead of `pom.xml`.
+
+# Customized Spring Initializr Service URL
+1. Open `User settings` in VS Code.
+1. Change value of entry `spring.initializr.serviceUrl`, e.g. "http://start.cfapps.io/", or [run the service locally](https://github.com/spring-io/initializr#running-the-app-locally)
+1. Verify:
+    1. Can generate a project from the specified service URL.
+
+# Default value of GroupId and ArtifactId.
+1. Open `User settings` in VS Code.
+1. Change values of entry `spring.initializr.defaultGroupId`, `spring.initializr.defaultArtifactId`.
+1. Open `Command Palette`, execute command `Spring Initializr: Generate a Maven Project`.
+1. Verify:
+    1. `GroupId` and `ArtifactId` are filled by the specified default values.
+
+# Default value of language.
+1. Open `User settings` in VS Code.
+2. Change values of entry `spring.initializr.defaultLanguage` to `""`.
+3. Verify:
+    1. It allows to select language during generating the project.
+    2. Open the generated project, the language matches what you selected.
+4. Change values of entry `spring.initializr.defaultLanguage` to `"Java"`.
+5. Verify:
+    1. It skips the step to select language, and directly uses the value you set.
+
+# Default value of packaging.
+1. Open `User settings` in VS Code.
+2. Change values of entry `spring.initializr.defaultPackaging` to `""`.
+3. Verify:
+    1. It allows to select packaging type during generating the project.
+    2. Open the generated project, the packaging type matches what you selected.
+4. Change values of entry `spring.initializr.defaultPackaging` to `"WAR"`.
+5. Verify:
+    1. It skips the step to select packaging type, and directly uses the value you set.
+
+# Edit Starters for Spring Boot Maven projects.
+1. Generate a maven project as above, select some dependencies.
+2. Open `pom.xml` file, verify current value of `dependencies` node.
+3. Right click on the editing area of the file, choose `Edit starters`.
+4. In the QuickPick box, do some selection and unselection, and proceed following the prompt messages.
+5. Verify:
+    1. The `pom.xml` file is modified, and the project can still be built by `mvn package`.
+    2. Corresponding `<dependency>` nodes are added/removed.
+    3. For dependencies with `bom` information, e.g. `azure`, a `<DependencyManagement>` node is added into the pom file.
+    4. For dependencies with `repository` information, e.g. `Spring Shell`, a `<repository>` node is added into the pom file.

package.json

@@ -2,11 +2,11 @@
   "name": "vscode-spring-initializr",
   "displayName": "Spring Initializr Java Support",
   "description": "A lightweight extension based on Spring Initializr to generate quickstart Spring Boot Java projects.",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "icon": "resources/logo.png",
   "publisher": "vscjava",
   "aiKey": "05fb8871-fbf0-488f-8453-a74cf0ca9b93",
-  "homepage": "https://github.com/Microsoft/vscode-spring-initializr/blob/v0.3.0/README.md",
+  "homepage": "https://github.com/Microsoft/vscode-spring-initializr/blob/v0.4.0/README.md",
   "repository": {
     "type": "git",
     "url": "https://github.com/Microsoft/vscode-spring-initializr.git"

thirdpartynotice.txt

@@ -10,6 +10,7 @@ are grateful to these developers for their contribution to open source.
 3. fs-extra (https://github.com/jprichardson/node-fs-extra)
 4. vscode-extension-telemetry-wrapper (https://github.com/Eskibear/vscode-extension-telemetry-wrapper)
 5. semver (https://github.com/npm/node-semver)
+6. lodash (https://github.com/lodash)
 
 md5 NOTICES BEGIN HERE
 =============================
@@ -112,3 +113,79 @@ ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEAL
 
 END OF vscode-extension-telemetry-wrapper NOTICES AND INFORMATION
 ==========================================================
+
+semver NOTICES BEGIN HERE
+==========================================================
+The ISC License
+
+Copyright (c) Isaac Z. Schlueter and Contributors
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
+IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
+END OF semver NOTICES AND INFORMATION
+==========================================================
+
+lodash NOTICES BEGIN HERE
+==========================================================
+The MIT License
+
+Copyright JS Foundation and other contributors <https://js.foundation/>
+
+Based on Underscore.js, copyright Jeremy Ashkenas,
+DocumentCloud and Investigative Reporters & Editors <http://underscorejs.org/>
+
+This software consists of voluntary contributions made by many
+individuals. For exact contribution history, see the revision history
+available at https://github.com/lodash/lodash
+
+The following license applies to all parts of this software except as
+documented below:
+
+====
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+====
+
+Copyright and related rights for sample code are waived via CC0. Sample
+code is defined as all source code displayed within the prose of the
+documentation.
+
+CC0: http://creativecommons.org/publicdomain/zero/1.0/
+
+====
+
+Files located in the node_modules and vendor directories are externally
+maintained libraries used by this software which have their own
+licenses; we recommend you read them, as their terms may differ from the
+terms above.
+
+END OF lodash NOTICES AND INFORMATION
+==========================================================