Failed to push TS project to vRO 9.0

[unbreakabl3]

Description

I cannot push a TS based project to standalone vRO 9.0 since vRBT version 4.8.0. Getting an error:

ERROR] Failed to execute goal com.vmware.pscoe.maven.plugins:vrealize-package-maven-plugin:4.8.0:push (default-cli) on project test1: Execution default-cli of goal com.vmware.pscoe.maven.plugins:vrealize-package-maven-plugin:4.8.0:push failed: Expected to find an object with property ['versionInfo'] in path $ but found 'java.lang.String'. This is not a json object according to the JsonProvider: 'com.jayway.jsonpath.spi.json.JsonSmartJsonProvider'. -> [Help 1]

When switching to any vRBT version below 4.8.0, the same project is pushed successfully.

Steps to Reproduce

1. Create a new project or use an existing one
2. Set version in pom.xml to any version 4.8.0 and above.
3. Run mvn package vrealize:push ...

Preconditions: [What are the preconditions to reproduce the issue]

Expected behavior: [What you expect to happen]

Actual behavior: [What actually happens]

Reproduces how often: [What percentage of the time does it reproduce]
All the time. I tested all version above 4.8.0 and the result is the same.

Component/s: [What are the Build Tools for VMware Aria components affected by the issue (e.g. "common/artifact-manager", "maven/plugins/vra-ng", "typescript/vrotest", etc)]

Affects Build/s: [Which are the Build Tools for VMware Aria releases / builds affected by the issue]

Environment

Client

• Build Tools for VMware Aria Version: 4.8.0-4.10.0
• Visual Studio Code Version: Version: 1.103.2
• OS Version: macOS 15.7

Dependencies

Run: curl -o- https://raw.githubusercontent.com/vmware/build-tools-for-vmware-aria/main/health.sh | bash and paste the output here:

✔ Node.js version 22.2.0 is within the required range (22 - 22).
✔ Maven version 3.9.11 meets the minimum requirement (>= 3.9).
✔ Java version 21.0.4 is within the required range (17 - 21).
All checks passed successfully.

Server

• vRealize Automation Version:
• vRealize Orchestrator Version: 9.0
• vRealize Operations Version:
• vRealize Log Insight Version:

Failure Logs

Related issues and PRs

Additional Context

[VenelinBakalov]

Hi @unbreakabl3 , were you able to test with 4.10.0 since there were a few more bugfixes introduced?

[unbreakabl3]

Hi @VenelinBakalov ,

yes, as I mentioned, I did test all of them. I am getting the same error for all version 4.8.0-4.10.0.

[VenelinBakalov]

@unbreakabl3 you are right, you listed the version range in the description
Could you rung the clean package -X command and share a more detailed log (no need for the full log but the messages right before the error) - since i am currently not able to test it i want to get a better feeling on where exactly this error is happening so i can potentially analyise the code and hopefully find the error before i get my hands on an environment

[VenelinBakalov]

my guess is that it happens in here, probably on a stand-alone Orchestrator we cannot use that call:

[VenelinBakalov]

Just for the sake of the try, could you remove the first part of the condition (the if vra 9 part) and check if the old authentication still works for the external vro?

[unbreakabl3]

Hi @VenelinBakalov ,
it did work.

[VenelinBakalov]

Ok that's interesting...so a standalone vRO 9 works with the previous authentication...i see. i will need to figure out how to map all of this.