Spring/spring-tools
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
2,065 Commits 69 Branches 0 Tags
b20ef8ca750104310c8fd16b2eacf528c65aba75
Commit Graph

9 Commits

Author SHA1 Message Date
Kris De Volder
efe8049bba Bump version to 0.1.6 2018-03-09 22:11:06 +00:00
Kris De Volder
3c92ce60cc Update vscode ls client to version 4.0.0 2018-03-05 11:38:19 -08:00
Kris De Volder
8c3af141cd Small change that allows running vscode-spring-boot npm install from git bash on Windows. 2018-03-02 11:28:34 -08:00
Kris De Volder
9f383a9b45 Switch vscode-spring-boot to properties launcher 2018-03-01 22:24:26 -08:00
Paul Verest
d8e7ce177b Name wording: Tools instead of Support 
Of course, it is for authors to name their creation.

Nevertheless, there are now 2 VSCode extension with name "Spring Boot Support".  
And also current published version is the same version number as previous obsolete: 0.1.4  
That make confusion.

Also Tools is used in https://spring.io/tools4
and has been unique word on Eclipse marketplace.
 2018-02-27 00:38:22 +08:00
Kris De Volder
6fd38e61a5 Bump version to 0.1.5 2018-02-22 23:24:47 +00:00
Kris De Volder
6e4141af64 Revert "Attempt to avoid https://github.com/Microsoft/vscode-vsce/issues/238" 
It should be fine to revert the workaround. The problem in vsce should be fixed
already.

This reverts commit dcb08077f5.
 2018-02-19 08:37:35 -08:00
Kris De Volder
dcb08077f5 Attempt to avoid https://github.com/Microsoft/vscode-vsce/issues/238 
Pinning vso-node-api version to 6.1.2-preview seems to work.
 2018-02-16 14:18:41 -08:00
Kris De Volder
a6e86d4cf7 Rename vscode-boot to vscode-spring-boot 
To avoid confusing prefix matching between patterns like
vscode-boot-* and vscode-boot-properties-*, vscide-boot-java-*

This would pontially cause weird version strings in concourse resources.
 2018-02-13 11:31:20 -08:00