Installation on Linux
Hello everyone!
I am a complete beginner, and have worked with processing and p5.js till now, so really excited to get started with the nodebox paradigm.
Currently, while trying to install nodebox3 on my linux machine, I get an error where the ant process is unable to download files from the mvn repo. Plus the build also requires openjdk-7 and since I have ubuntu 20.04, it would be hacky, i think, to try and install that. So I am wondering if the best way to run nodebox 3 on linux is to use the windows build and run using wine.
Has anyone done this before and does it work?
thanks :)
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Frederik De Ble... on 13 Jan, 2021 02:14 PM
NodeBox 3 should be able to run on much more modern JDKs. Can you show the error you're getting?
2 Posted by anushka16798 on 14 Jan, 2021 04:47 AM
Thank you for replying, the error i get is as follows. I saw this over at github as well and tried the solutions mentioned there(like updating certs), but couldn't get it to work.
BUILD FAILED
..../build.xml:86: Unable to resolve artifact: Missing:
----------
1) org.clojure:clojure:jar:1.8.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.clojure -DartifactId=clojure -Dversion=1.8.0 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.clojure -DartifactId=clojure -Dversion=1.8.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) net.nodebox:nodebox:jar:3.0.44
2) org.clojure:clojure:jar:1.8.0
2) com.jayway.jsonpath:json-path:jar:0.8.1
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.jayway.jsonpath -DartifactId=json-path -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=com.jayway.jsonpath -DartifactId=json-path -Dversion=0.8.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) net.nodebox:nodebox:jar:3.0.44
2) com.jayway.jsonpath:json-path:jar:0.8.1
3) org.python:jython-standalone:jar:2.7.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.python -DartifactId=jython-standalone -Dversion=2.7.0 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.python -DartifactId=jython-standalone -Dversion=2.7.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) net.nodebox:nodebox:jar:3.0.44
2) org.python:jython-standalone:jar:2.7.0
Support Staff 3 Posted by Frederik De Ble... on 15 Jan, 2021 09:46 AM
In my testing, this happened because the build process was trying to download dependencies from an unsecure server.
I've now updated the dependencies file (pom.xml). Try doing "git pull" and building again and see if that works.
4 Posted by anushka16798 on 20 Jan, 2021 03:21 AM
Yes, it works now!
I was initially running the command on the download page `ant run`, but that was still giving me the same error. When i checked out the github actions page, I found another mvn command and using that I could build.
This might be a beginner question but how do i run the jar file, cos doing java -jar target/name-of-file says "no main manifest attribute, in target/nodebox-3.0.44.jar"
Support Staff 5 Posted by Frederik De Ble... on 20 Jan, 2021 07:00 AM
That's weird. "ant run" should work.
Support Staff 6 Posted by john on 23 May, 2021 10:02 PM
Does Guilherme's discovery that updating the JDK from 7 to 11 allows the ant command to execute successfully solve this issue?
http://support.nodebox.net/discussions/nodebox-2-3/6390-update-inst...