Dusan Balek
Dusan Balek
> @dbalek when (re)targetting delivery, please add your reasoning, thanks! OK - target milestone changed back to NB16.
> Obviously the binaries need distributing via Maven and the binaries-list files updating rather than deleting before this can be merged. > > Is there a reason for the PR...
@neilcsmith-net: Changes requested are IMHO done, do you want to update your review before merge ?
Unfortunatly, tested with the attached [vscode-java-test extension](https://github.com/microsoft/vscode-java-test/files/12712911/vscode-java-test-0.40.2023092502.vsix.zip) and the pre-release (v3.12.2023091801) of the [vscode-gradle extension](https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-gradle) I am still getting the same error as in https://github.com/microsoft/vscode-java-test/issues/1613
Cleaning the workspace cache, still the same result
I have started VSCode with the fresh `--user-data-dir` and `--extensions-dir`, and I have created the new Micronaut 4.1.2 project. So, the `settings.json` is almost empty now: ``` { "workbench.startupEditor": "none"...
The node is named `Referenced Libraries (Read-only)` now, otherwise no change...
Yes, exactly the same error.
> Going back to this - thinking of this more, the actual commit characters sent out from the server should probably be an intersection between the commit characters requested by...