Closed gnnivlek closed 3 years ago
had the same exact same issue...and tried removing it and still it failed
Hi, I had the following issue when I change the sapcc version to latest version in Dockfile: error: open of com.sap.scc-ui-2.13.0.x86_64-4.rpm failed: No such file or directory
All fixed via cab892f465949a88c52212090c4e7835fe9f643c Please confirm.
Error: Unable to access jarfile plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
@skandasoft are you using the latest version of my dockerfile + building it etc? So far I couldn't reproduce the issue on my own...
Thanks for putting this out.
I tried pulling the latest version. And I saw the latest docker file getting pulled. And when I build on it (even with --no-cache) it was giving the same error. Now I re-cloned into another directory and tried it is working. 👍
I now have to figure the difference between the cloud foundry/neo user. the cloud foundry doesn't have the cloud connector link in there but I was able to connect to that subdomain/user successfully.
Now I am trying to connect to local ABAP but it doesn't seem to do a check against it. Should I raise a ticket here or in your youtube. it is in the same network. I guess I have to put the 502 certificate in there.
I consider this to be done/confirmed now.
Just some hints (I had to read you message again and again many many times to understand what you mean, I hope I got it right):
Yes. Confirmed as done. You can close.
Thanks for taking time to answer my question.
Hi, I have followed the instruction and change the version of the cloud connector to the current version (SAPCC 2.13.0), but after successfully running the Dockerfile, the generated image seems to have a problem when accessing the jarfile plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar. Is there any solution for this issue? I noticed that the props.ini on the current version does not have this -jar command and I can't compare it with previous version since there's no way to download it now. Thank you.