Releases: ApamaCommunity/apama-vscode-extensions
Releases · ApamaCommunity/apama-vscode-extensions
v2.3.0
v2.2.3
v2.2.2
Fixed a bug where adding bundles to a project did not work.
Full Changelog: v2.2.1...v2.2.2
v2.2.1
Fixed an issue with the extension not locating the Apama installation when executed in a Docker development container, and on Windows.
Full Changelog: v2.2.0...v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
The update provides several important fixes, and a better workflow for setting the Apama installation directory, dynamically changing workspace folders, and adding bundles.
It is designed to work with a modern version of Apama such as 10.15.6.2 or later.
- Added new Command Palette option
Create in Project New Folderfor easily creating a new project directory. - Added support for automatically reloading the extension when the "Apama Home" configuration option is changed.
- Added support for adding custom/non-product bundles such as the Analytics Builder Block SDK (by specifying a
bndfile in a path relative to the project directory). - Added commands to the Command Palette for adding/removing different kinds of bundles.
- Added
Force Rebuildto the Command Palette, which restarts the Apama language servers in case something went wrong. - Added the ability to add multiple product bundles at once.
- Fix the EPL syntax highlighting to use the correct set of keywords.
Full Changelog: v2.0.0...v2.1.0
v2.0.0
The update fixes several bugs and usability issues with the extension, and provides a foundation for future improvements.
It is best enjoyed with a modern version of Apama such as 10.15.6.1 or later.
- All extension settings names are changed; you will need to manually copy any config you need such as the location where Apama is installed
- Apama 10.15.6.0 is the minimum version required for Language Server support, i.e. semantic checking.
- The "Create Project" command requires a minimum of 10.15.6.2.
- Fixed automatic Language Server start up - if Apama is installed in a default location, or the
apamaHomepreference set to a valid location, the Language Server will automatically start up. - A single workspace folder is now considered to hold just one Apama project, and the Apama project files (
.projectand.dependencies) must be at the top level. - Added basic support for multi-root workspaces (each folder added to a workspace is build as an independent Apama project). Change detection is not yet done, so currently requires reloading the Window after changing the open folders.
- Removed support for creating deployment directories. This can be manually done using the
engine_deploycommand line tool. - Fixed some missing keyword highlights
- Now works with WSL
- Stop the extension startup from stealing application focus