Alex Boyko

The UI only supports projects with **pom.xml** files. Need to also include **build.gradle** files

STS validates XML although all XML validation is off

5

STS validates XML with WST XML Core plugin which is for some reason still being pulled by STS eclipse plugins. There is another WST plugin: WST SSE Core. It is...

Currently we have java-properties project under commons which defines Properties AST and Parser generated with ANTLR from g4 grammar file. It should not be too much effort to switch to...

Normalize URI

6

The common case of setting URI on lsp4j message object is `URI#toString()` call. For example LSP4E sets uri on the `TextDocumentIdentifier` via `URI#toString()` call rather than `URI#toASCIIString()`. Therefore if the...

test/resources are not the classpath when running unit tests

2

Consider the following project https://github.com/BoykoAlex/buildship-test-resources 1. Clone it and import into eclipse. 2. Run `DemoApplication` as **Java Application** 3. Note `Some port = '2222'` in the output in the Console...

SecurityException during native image compilation

1

I'm trying to native compile a language server app (Boot LS) that depends on lemminx jar. The error is below: ``` Caused by: java.lang.SecurityException: class "com.thaiopensource.relaxng.pattern.MySchemaPatternBuilder"'s signer information does not...

Replacing abandoned `react-scripts` with `vite`. Seems to build, execute tests and run locally without issues. The only grey area is the need for `@pact-foundation/pact` in dev dependencies and json file...

SpEL syntax highlighting via LSP semantic tokens inside: - Java annotations - Inside JPQL queries

Allow for usage of `DefaultProjectParser` outside of Gradle Daemon process

5

## What problem are you trying to solve? Re-use `DefaultProjectParser` outside of Gradle daemon process. There are various markers added throughout the ASTs via the project parser. The recipes rely...

Java `Properties` object serialization produces for `String' value `:` looks like this: ``` my.path=\: ``` Doesn't look like the language tokenizer/parser likes this. I get the following errors: ``` extraneous...