-
Notifications
You must be signed in to change notification settings - Fork 871
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
Build for 2.1.0 failing #4840
Comments
Oh, and I tried maven, because the ant install says it will be deprecated in 3.0 and to use maven. Scott |
which branch/tag are you trying to build? i was able to make a successful build without any issues on 2.1.0 GA. seems to me an environmental issue than anything else. |
I tried with 2.1.0. How can I check my environment? I have Debian Wheezy and this Java. java version "1.6.0_36" Scott |
@smolinari Could you use Oracle JDK 8? |
Ok. Got Oracle Java 8 running and the build finished successfully and It looks like I can now start up OrientDB properly and all is working. (Might need a requirement note in the docs about minimum Java needed). One thing. I can't access Studio. Is it correct that the ports ODB is on only bind to IPv6 (TCP6)? Scott |
Added in readme.txt. |
The port should be IPv4 |
Ok. As it looks, the Oracle Java 8 repo I installed only binds to IPv6 ports. I did some googling and found out I would need to set a Java environment variable.
So I entered that into my Thanks for the help. This issue can be closed. Scott |
Following the installation instructions in the manual. I have tried both maven and ant and both fail.
Here is what ant outputs.
BUILD FAILED
/tmp/orientdb/build.xml:133: The following error occurred while executing this line:
/tmp/orientdb/build.xml:21: The following error occurred while executing this line:
/tmp/orientdb/core/build.xml:38: Compile failed; see the compiler error output for details.
See attached log.jpg file for complete output of compilation. Download it and rename it to log.txt. Github doesn't support .txt files.
Scott
The text was updated successfully, but these errors were encountered: