-
Notifications
You must be signed in to change notification settings - Fork 24
Error: Bad repository URI #69
Comments
Can you attach the exact entire ouput of the mvn gcloud:run or mvn gcloud:deploy command? Are you using an EAR maven project? |
Yes, my project is an EAR maven project. It fails on the managed vm module when it gets to it with the same error so I have just started trying to run/deploy just the managed vm module for the time being. The project also contains a module that only includes shared code between some of the modules but isn't deployed. See below for the entire output and version numbers.
Chriss-MBP:svgtopdf chrisvaught$ mvn gcloud:run Beginning interaction for module svgtopdf... |
@ludoch I think this is the same problem I was having. Even though the pom had a with a https URI to the repro, the plugin (and/or SDK) was seeing the origin repo from git directly, which was an ssh style. Once I switched to using https for the git repo, this style of error went away. |
I see! On Thu, Dec 10, 2015 at 3:25 PM, Greg Wilkins [email protected]
|
Switching to https did fix this error for me as well. |
Getting the error when running: mvn gcloud:run
using:
maven:
|
I have a Java Managed VM that when I try to run or deploy it returns the Bad repository URI error. The git repos is correct. That being said this is a multiple module repo where the other modules are normal java app engine modules. I was finally able to get the module deployed by removing the repository setting from the app.yaml file that was created then running:
This is obviously not ideal.
The text was updated successfully, but these errors were encountered: