Release 2.4.0.202610021514

This commit is contained in:
Erhan Keseli
2026-10-02 17:17:09 +02:00
parent 44ed149985
commit d77fc9ea5f
16 changed files with 20 additions and 14 deletions

View File

@@ -11,13 +11,10 @@ AI Client --(HTTP/JSON-RPC)--> Eclipse Plugin --(ADT REST API / SNC)--> SAP
```
## What's new in 2.3.0
## What's new in 2.4.0
- `sap_create_object` creates a function module (FUNC) in an existing function group.
- `sap_create_object` creates a function group (FUGR).
- The MCP Server view has an Activity tab that shows each tool call live, with the client name, the result size, and an estimated token count.
- The MCP Server view changes its layout to fit the view width and has a "Connected only" filter for the project table.
- The security log records the client name and the result size of each tool call.
- `sap_create_object` creates a class with a test classes include.
- `sap_pull_source`, `sap_push_source`, and `sap_push_source_from_file` accept `includeType`. A write to `testclasses` creates the include if it is missing.
See [CHANGELOG.md](CHANGELOG.md) for earlier versions.
@@ -77,7 +74,7 @@ Download the plugin JAR from the latest release and drop it into your Eclipse `d
## Requirements
- Eclipse 2024-03 or later with **SAP ADT** (ABAP Development Tools) installed
- Java 17 or later
- Java 21 or later to run the plugin in ADT 3.63.0. The ADT bundles `com.sap.adt.communication` and `com.sap.adt.tools.core` require JavaSE 21 (`Require-Capability: osgi.ee`, `version=21`), and the ADT launcher sets `-Dosgi.requiredJavaVersion=21`
- One or more ABAP projects in your Eclipse workspace with active SNC/SSO connections to SAP
@@ -192,8 +189,8 @@ The plugin exposes 31 tools covering the full ABAP development workflow:
|------|-------------|
| `sap_pull_source` | Read source code of an ABAP object into the AI context. `element=<member>` returns one `METHOD` block (`part=definition` for the declaration); `includeType` selects a class include — `main` (Global Class, default), `definitions`, `implementations`, `macros`, `testclasses`, `all` |
| `sap_pull_source_to_file` | Fetch source from SAP and write it to a local file (preferred for large objects). Same `element` and `includeType` parameters |
| `sap_push_source` | Write source code from context to an ABAP object in SAP — runs the full lock → write → unlock → activate pipeline in one call |
| `sap_push_source_from_file` | Save a local file back to SAP through the same one-call pipeline |
| `sap_push_source` | Write source code from context to an ABAP object in SAP — runs the full lock → write → unlock → activate pipeline in one call. `includeType` selects a class include; a write to `testclasses` creates the include if it is missing |
| `sap_push_source_from_file` | Save a local file back to SAP through the same one-call pipeline. Same `includeType` parameter as `sap_push_source` |
| `sap_push_element` | Write one member block. The server merges the block into the current full source and pushes it — the model never holds the class. CLAS, INTF, PROG, FUGR |
| `sap_push_message` | Write one message or several messages into an existing message class (MSAG). The server reads the class, merges the messages, and writes the class back in one call. A new number is appended. An existing number is updated |
| `sap_pretty_print` | Format (pretty-print) ABAP source through the ADT pretty-printer service. The tool takes only the source and uses the server's stored settings |