-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hardcoded /usr/bin path #38
Comments
It will be difficult to have a development SlipStream working like this. You will have to create a lot of symbolic links and to install a lot of dependencies. |
The hardcoding of /usr/bin is also a problem for real installations, if someone wants to put SS in ~/ss, for example... Packages should be relocatable, some sysadmins will require that. IMHO, the in-code default values should be relative paths that just work when checking the code with SlipStreamBootstrap. Does the fact that it does not take my CliConnectorBase.java modification, has something to do with the use of downloaded "-SNAPSHOT"s by maven ? |
Your modifications should have been taken into account. mvn clean install in the |
I'm trying to run SS from a development environment (i.e. not installed) and there are hardcoded pathes:
WARNING: Failed contacting cloud [SlipStreamRuntimeException]: [toto/myos] with 'sh: 1: /usr/bin/openstack-describe-instances: not found
I tried to change CLI_LOCATION from line 51 in:
SlipStreamServer/jar-connector/src/main/java/com/sixsq/slipstream/connector/CliConnectorBase.java
but that is not working, I think my modification is not taken...
The text was updated successfully, but these errors were encountered: