GitHub user Mise opened an issue:
https://github.com/apache/incubator-predictionio/issues/341
Install.sh fails
Hi,
I'm trying to evaluate PredictionIO and the "User recommendations" template
for an internal project. I've tried different Docker builds and Vagrant builds
but they all fail due to different reasons at different points in time. Most
often due to some Java/Scala dependency not being met in the *pio train* stage.
I have therefore taken a step back to try to just get a plain PIO install
from the master branch to work. While I believe I had something working the
other day I no longer seem to be able to repeat the installation. The setup is
simple:
1) A Virtualbox ubuntu/trusty64 box instantiated using Vagrant
2) Cloned master branch from apache/incubator-predictionio
3) Installed Oracle Java 8 + JDK
I run the *install.sh* script from the bin folder. Once the script finishes
running the destination path has been created but it is empty apart from the
*vendors* folder that seemingly contains the dependencies: ES, Spark etc. This
is the only folder content and there is no *pio-start-all.sh* etc.
Looking into the *install.sh, make-distribution.sh* and *build.sbt* files
it seems the declared version to be built is 0.10.0-incubating. However, when
running install I can see it is trying to build 0.11.0-SNAPSHOT:
Deciphering this a bit more leads me to believe this is because of this
line in *install.sh*: `curl -L
https://codeload.github.com/apache/incubator-predictionio/tar.gz/develop >
incubator-predictionio-develop.tar.gz`. Looking at what it is actually
downloading, the version downloaded is 0.11.0-SNAPSHOT.
At the end of the script, although not clearly indicating an error I can
see this in the log:
Is it a version mismatch between the tar being pulled and the PIO_FILE in
install.sh? Am I totally missing something? Any pointers greatly appreciated!
----
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
