The checkout option "checkpointBeforeBuild: true" is not working on development pathes.

If we make a build on a project's development path and the option checkpointBeforeBuild is true, the plugin returns the error MKS125607: Invalid project syntax

The plugin adds the returned checkpoint revision simply to the specified project and use this for the projectinfo command:
#/repository/projectx becomes #/repository/projectx#forceJump#b=1.78

If the project is on a development path the resulting string is invalid
#/repository/projectx#d=branchname becomes #/repository/projectx#d=branchname#forceJump=#b=1.77.1.3

[Pipeline] {
[Pipeline] tool
[Pipeline] tool
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Checkout)
[Pipeline] checkout
Change Log: http://jenkins.domain.intra/job/projectx/2/changes
Build Log: http://jenkins.domain.intra/job/projectx/2/console
Preparing to execute si projectinfo for #/repository/projectx#d=branchname
Preparing to execute pre-build si checkpoint for #/repository/projectx#d=branchname
Successfully executed pre-build checkpoint for project for #/repository/projectx#d=branchname, new revision is 1.77.1.3
An API Exception was caught!
The project for #/repository/projectx#d=branchname#forceJump=#b=1.77.1.3 could not be located on the server ptc.domain.intra:7001: MKS125607: Invalid project syntax. MKS125617: You cannot specify twice a configuration for (projectx/project.pj).
si projectinfo --user=jenkins-core --port=7001 --hostname=ptc.domain.intra --project=for #/repository/projectx#d=branchname#forceJump=#b=1.77.1.3 – returned exit code 128
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }