greclipse formatter reformats consecutive bare @Library annotations in Jenkinsfiles

[austek]

We're using Spotless with greclipse() to format Groovy scripts and Jenkinsfiles. We ran into a behaviour where multiple consecutive bare @Library annotations get reformatted unexpectedly.

Original Jenkinsfile:

@Library("pipeline-abc@1.0")
@Library("pipeline-def@2.0")
@Library("pipeline-hij@3.0")

or

@Library("pipeline-abc@1.0")
@Library("pipeline-def@2.0")
@Library("pipeline-hij@3.0")_

formatting works with following but not valid Jenkinsfile syntax

@Library("pipeline-abc@1.0") _
@Library("pipeline-def@2.0") _
@Library("pipeline-hij@3.0") _

After spotlessApply:

The second and third @Library lines get indented as if they are continuations of the previous expression (greclipse appears not to recognise that each annotation is a standalone statement without an immediately following class/method declaration).

Workaround we used:

Merging into a single statement with the array form satisfies greclipse:
@Library(["pipeline-abc@1.0", "pipeline-def@2.0", "pipeline-hij@3.0"]) _

This works, but it changes the meaning of the file structurally (it is the https://www.jenkins.io/doc/book/pipeline/shared-libraries/#using-libraries for multiple libraries, but not everyone uses it).

Questions:

1. Is this a known limitation of how greclipse handles annotation sequences without a following declaration?
2. Is there a greclipse configuration option (e.g., formatter preferences) that prevents it from merging/indenting such annotation sequences?
3. Would it be feasible for Spotless to detect this pattern (bare annotation not followed by a declaration) and leave it untouched, or is this entirely a greclipse concern?

Configuration used:

spotless {
    groovy {
        target '**/*.groovy', 'Jenkinsfile', 'Jenkinsfile.*'
        targetExclude '**/build/**'
        greclipse()
        importOrder()
        removeSemicolons()
    }
}