After deploying vra7.4, with vco up and running, maven cannot access the archetype xml file.
I get the following diagnostic:
Caused by: org.apache.maven.wagon.providers.http.httpclient.conn.HttpHostConnectException: Connect to kdvra:8281 [kdvra/10.128.225.40] failed: Connection refused (Connection refused)
How can I go about determining the root cause of this?
Hi,
The first problem is the port number.
The second problem - in case of vRO embedded in vRA appliance, I think there is no hosted Maven repository available. I'm not 100% sure (have to double check this), but in this case you'll have to deploy a standalone vRO appliance.
Another possible problem you can hit is that the newer Maven versions could have issues with the latest Maven archetype plug-in. You can resolve it by forcing Maven to use the slightly older version 2.4 of this plug-in; if you are unsure how to do so you may check eg. https://communities.vmware.com/message/2707795#2707795 or https://www.virtualvcp.com/vmware-vrealize-automation-vcac/229-vro-plugin-development-getting-maven-...
Hi,
The first problem is the port number.
The second problem - in case of vRO embedded in vRA appliance, I think there is no hosted Maven repository available. I'm not 100% sure (have to double check this), but in this case you'll have to deploy a standalone vRO appliance.
Another possible problem you can hit is that the newer Maven versions could have issues with the latest Maven archetype plug-in. You can resolve it by forcing Maven to use the slightly older version 2.4 of this plug-in; if you are unsure how to do so you may check eg. https://communities.vmware.com/message/2707795#2707795 or https://www.virtualvcp.com/vmware-vrealize-automation-vcac/229-vro-plugin-development-getting-maven-...