All notable changes to the "vscode-tomcat" extension will be documented in this file.
- Regression issue: failed to debug a WAR package. #329
- Empty string in META-INF/context.xml was not handled well. #234
- New setting
tomcat.customEnv
to specify custom environment variables. Now it is allowed to launch Tomcat servers with a different Java runtime by specifying aJAVA_HOME
env. #318
- Always ask for confirmation when deleting a Tomcat server. #306
- Fixed #226: Can't add Tomcat server on Linux
- Fixed #239: Can't select different JVM to run Tomcat instance
- Update the
vscode-extension-telemetry-wrapper
to0.8.0
.
- Account for case when looking at context XML #218
- Support to use the context.xml if present
- Support right click on exploded war folder to run it directory Tomcat Server
- Support right click on exploded war folder to debug it directory on Tomcat Server
- Fix issue #177
- Add command "Generate War Package from Current Folder"
- Enable "Open in Browser" command for idle server too
- Support right click on server to select a war package to debug
- Fix issue #168
- Rename extension to "Tomcat for Java" #162
- Update war package icon
- Update demo gif in README
- Support automaticaly run operations aginst the server when there is only one Tomcat Server in work space
- Update the server home page header
- Provide a centralized usage demo in the beginning of README
- Fix issue #138
- Add "Reveal in Explorer" context command to war packages in Tomcat Exploer
- Add "Delete" context command to war packages in Tomcat Explorer
- Add support for users to customize JVM options
- Update context commands names
- Format the server.xml during creating Tomcat Server
- Validate Tomcat install directory when user creating Tomcat Server
- Add "Restart Tomcat Server" command
- Add command palette entry for users to run "Debug on Tomcat Server"
- Support users to config the Tomcat Servers workspace in settings
- Add refresh button in Tomcat Server Explorer
- Support Tomcat Server renaming from Tomcat Server Explorer
- Show war packages deployed to Tomcat Server in sub-tree in Tomcat Server Explorer
- Add context command to browse war package
- Support right-click to Add Tomcat Server in Tomcat Server Explorer
- Support creating multiple Tomcat Servers from same install path
- Construct the Tomcat Server name automatically base on install path
- Add option for users to choose never restarting Tomcat Server even if the http(s) port changed
- Just deploy a war package without restarting a Tomcat Server when users keep runing/debuging new war package on it #59
- Poping up error message with a revert action instead of just restarting Tomcat Server when user change server port of a running server #28
- Add "+" button in Tomcat Server Explorer to add new Tomcat Server
- Add option to add new Tomcat Server to start if there is no server to start
- Add context command "Delete Tomcat Server" for running server in Tomcat Server Explorer
- Browse directly to select Tomcat Directory and add Tomcat Server without clicking "Browse..."
- Prompt information message to confirm continuing operations when user creating same Tomcat Server
- Using command to start a running server throw error and shutdown the running server #60
- Error message shows not clear enough information to user when no server to stop #42
- Using command to delete a running server didn't kill all tomcat process #61
- Command 'Open server.xml' command shows in Tomcat Server Explorer even if there is no Tomcat Server #37
- Support starting Tomcat from Tomcat Server Explorer
- Support restarting if server.xml of a running server is updated
- Support opening root page from Tomcat Server Explorer
- Fix Overview page issue
- Support opening/editoring server.xml of the tomcat instance in workspace from Tomcat Servers Explorer
- Initial release
- Create Tomcat server in workspace
- Debug war package on Tomcat server
- Run war package on Tomcat server
- Delete the Tomcat server in workspace