I've tried to follow the instructions on the getting started page for playn and run into problems when running the first program java showcase. I get the following errors when right clicking and running Maven test. Also I get numerous errors in the problem tab of eclipse related to (failure to transfer xxx from yyy) where xxx is some jar file and yyy is a gwt or playn website
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building PlayN Showcase Java 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://snapshots.repository.codehaus.org/org/apache/maven/plugins/maven-surefire-plugin/2.10/maven-surefire-plugin-2.10.pom
Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.10/maven-surefire-plugin-2.10.pom
Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.10/maven-surefire-plugin-2.10.pom (11 KB at 47.2 KB/sec)
Downloading: http://snapshots.repository.codehaus.org/org/apache/maven/surefire/surefire/2.10/surefire-2.10.pom
Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire/2.10/surefire-2.10.pom
Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire/2.10/surefire-2.10.pom (12 KB at 118.8 KB/sec)
Downloading: http://snapshots.repository.codehaus.org/org/apache/maven/maven-parent/20/maven-parent-20.pom
Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/20/maven-parent-20.pom
Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/20/maven-parent-20.pom (25 KB at 143.9 KB/sec)
Downloading: http://snapshots.repository.codehaus.org/org/apache/maven/plugins/maven-antrun-plugin/1.6/maven-antrun-plugin-1.6.pom
Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-antrun-plugin/1.6/maven-antrun-plugin-1.6.pom
Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-antrun-plugin/1.6/maven-antrun-plugin-1.6.pom (5 KB at 52.2 KB/sec)
Downloading: https://oss.sonatype.org/content/repositories/snapshots/com/googlecode/playn/playn-showcase-core/1.0-SNAPSHOT/maven-metadata.xml
Downloading: http://forplay.googlecode.com/svn/mavenrepo/com/googlecode/playn/playn-showcase-core/1.0-SNAPSHOT/maven-metadata.xml
Downloading: http://forplay.googlecode.com/svn/mavenrepo/com/googlecode/playn/playn-showcase-core/1.0-SNAPSHOT/playn-showcase-core-1.0-SNAPSHOT.pom
Downloading: https://oss.sonatype.org/content/repositories/snapshots/com/googlecode/playn/playn-showcase-core/1.0-SNAPSHOT/playn-showcase-core-1.0-SNAPSHOT.pom
[WARNING] The POM for com.googlecode.playn:playn-showcase-core:jar:1.0-SNAPSHOT is missing, no dependency information available
Downloading: http://forplay.googlecode.com/svn/mavenrepo/jlayer/tritonus_share/1.0/tritonus_share-1.0.pom
[WARNING] Checksum validation failed, no checksums available from the repository for http://forplay.googlecode.com/svn/mavenrepo/jlayer/tritonus_share/1.0/tritonus_share-1.0.pom
Downloaded: http://forplay.googlecode.com/svn/mavenrepo/jlayer/tritonus_share/1.0/tritonus_share-1.0.pom (462 B at 0.7 KB/sec)
Downloading: http://forplay.googlecode.com/svn/mavenrepo/com/googlecode/playn/playn-showcase-core/1.0-SNAPSHOT/playn-showcase-core-1.0-SNAPSHOT.jar
Downloading: http://forplay.googlecode.com/svn/mavenrepo/jlayer/mp3spi/1.9.5/mp3spi-1.9.5.jar
Downloading: http://forplay.googlecode.com/svn/mavenrepo/jlayer/tritonus_share/1.0/tritonus_share-1.0.jar
[WARNING] Checksum validation failed, no checksums available from the repository for http://forplay.googlecode.com/svn/mavenrepo/jlayer/mp3spi/1.9.5/mp3spi-1.9.5.jar
Downloaded: http://forplay.googlecode.com/svn/mavenrepo/jlayer/mp3spi/1.9.5/mp3spi-1.9.5.jar (25 KB at 40.9 KB/sec)
[WARNING] Checksum validation failed, no checksums available from the repository for http://forplay.googlecode.com/svn/mavenrepo/jlayer/tritonus_share/1.0/tritonus_share-1.0.jar
Downloaded: http://forplay.googlecode.com/svn/mavenrepo/jlayer/tritonus_share/1.0/tritonus_share-1.0.jar (101 KB at 102.4 KB/sec)
Downloading: https://oss.sonatype.org/content/repositories/snapshots/com/googlecode/playn/playn-showcase-core/1.0-SNAPSHOT/playn-showcase-core-1.0-SNAPSHOT.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.155s
[INFO] Finished at: Tue Aug 07 08:01:22 EDT 2012
[INFO] Final Memory: 7M/112M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project playn-showcase-java: Could not resolve dependencies for project com.googlecode.playn:playn-showcase-java:jar:1.0-SNAPSHOT: Could not find artifact com.googlecode.playn:playn-showcase-core:jar:1.0-SNAPSHOT in forplay-legacy (http://forplay.googlecode.com/svn/mavenrepo) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
You can try this:
Right click on "playn-showcase" then: Run As -> Maven Install
It should retrieve all dependencies correctly.
Next time you want to launch the sample, you can follow the tutorial procedure:
Right click on "playn-showcase-java" then: Run As -> Maven Test
Related
Setup: Java 17.0.1, Ubuntu 22.04.1 LTS, openjfx installed
$ sudo apt-get install openjfx
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
.....
$ apt list --installed | grep fx
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
grub-gfxpayload-lists/jammy,now 0.7 amd64 [installed]
libmfx1/jammy,now 22.3.0-1 amd64 [installed,automatic]
libopenjfx-java/jammy,jammy,now 11.0.11+0-1 all [installed,automatic]
libopenjfx-jni/jammy,now 11.0.11+0-1 amd64 [installed,automatic]
openjfx-source/jammy,jammy,now 11.0.11+0-1 all [installed,automatic]
openjfx/jammy,now 11.0.11+0-1 amd64 [installed]
Reference: https://github.com/andytill/erlyberly/wiki/Compiling
I have git cloned as specified in the reference. When I try to build using "./mvnw clean compile install assembly:single", I am getting the following error. Please help me in resolving the issue.
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/bhuvan/git/erlyberly/src/main/java/erlyberly/TermTreeView.java:[38,20] package javafx.event does not exist
[ERROR] /home/bhuvan/git/erlyberly/src/main/java/erlyberly/TermTreeView.java:[39,28] package javafx.scene.control does not exist
[ERROR] /home/bhuvan/git/erlyberly/src/main/java/erlyberly/TermTreeView.java:[40,28] package javafx.scene.control does not exist
[ERROR] /home/bhuvan/git/erlyberly/src/main/java/erlyberly/TermTreeView.java:[41,28] package javafx.scene.control does not exist
[ERROR] /home/bhuvan/git/erlyberly/src/main/java/erlyberly/TermTreeView.java:[42,28] package javafx.scene.control does not exist
[ERROR] /home/bhuvan/git/erlyberly/src/main/java/erlyberly/TermTreeView.java:[43,28] package javafx.scene.control does not exist
[ERROR] /home/bhuvan/git/erlyberly/src/main/java/erlyberly/TermTreeView.java:[44,26] package javafx.scene.input does not exist
[ERROR] /home/bhuvan/git/erlyberly/src/main/java/erlyberly/TermTreeView.java:[45,26] package javafx.scene.input does not exist
[ERROR] /home/bhuvan/git/erlyberly/src/main/java/erlyberly/TermTreeView.java:[46,26] package javafx.scene.input does not exist
[ERROR] /home/bhuvan/git/erlyberly/src/main/java/erlyberly/TermTreeView.java:[49,35] cannot find symbol
I'm trying to publish a bookdown book to Netlify. It runs perfect locally, but I cannot deploy it to Netlify.
Github: https://github.com/OmarGonD/doctrina-test
What I've done is to download the bookdown-demo as a Zip and I've modified the contents.
The Deploy log says:
Error: Error building site: No source directory found, expecting to find it at /opt/build/repo/content
And according to this Hugo Forum the content directory must be added to the Github repository.
But in the Bookdown demo repository, I don't see any content folder in there.
What should I do?
Full deploy log:
10:11:22 PM: Build ready to start
10:11:23 PM: build-image version: 9e0f207a27642d0115b1ca97cd5e8cebbe492f63
10:11:23 PM: build-image tag: v3.3.2
10:11:23 PM: buildbot version: f71b4aa1b1ebc2bff806e48691024e0ab383dc02
10:11:23 PM: Fetching cached dependencies
10:11:24 PM: Starting to download cache of 101.9MB
10:11:24 PM: Finished downloading cache in 934.174652ms
10:11:24 PM: Starting to extract cache
10:11:27 PM: Finished extracting cache in 3.007482882s
10:11:27 PM: Finished fetching cache in 3.985523679s
10:11:27 PM: Starting to prepare the repo for build
10:11:28 PM: Preparing Git Reference refs/heads/master
10:11:33 PM: Starting build script
10:11:33 PM: Installing dependencies
10:11:35 PM: Started restoring cached node version
10:11:37 PM: Finished restoring cached node version
10:11:37 PM: v10.16.3 is already installed.
10:11:38 PM: Now using node v10.16.3 (npm v6.9.0)
10:11:38 PM: Attempting ruby version 2.6.2, read from environment
10:11:39 PM: Using ruby version 2.6.2
10:11:40 PM: Using PHP version 5.6
10:11:40 PM: Installing Hugo 0.18
10:11:41 PM: Hugo Static Site Generator v0.18 BuildDate: 2019-08-29T03:11:41Z
10:11:41 PM: Started restoring cached go cache
10:11:41 PM: Finished restoring cached go cache
10:11:41 PM: unset GOOS;
10:11:41 PM: unset GOARCH;
10:11:41 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
10:11:41 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
10:11:41 PM: go version >&2;
10:11:41 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
10:11:41 PM: go version go1.12 linux/amd64
10:11:41 PM: Installing missing commands
10:11:41 PM: Verify run directory
10:11:41 PM: Executing user command: hugo
10:11:41 PM: Started building sites ...
10:11:41 PM: Error: Error building site: No source directory found, expecting to find it at /opt/build/repo/content
10:11:41 PM: Skipping functions preparation step: no functions directory set
10:11:41 PM: Caching artifacts
10:11:41 PM: Started saving pip cache
10:11:41 PM: Finished saving pip cache
10:11:41 PM: failed during stage 'building site': Build script returned non-zero exit code: 255
10:11:41 PM: Started saving emacs cask dependencies
10:11:41 PM: Finished saving emacs cask dependencies
10:11:41 PM: Started saving maven dependencies
10:11:41 PM: Finished saving maven dependencies
10:11:41 PM: Started saving boot dependencies
10:11:41 PM: Finished saving boot dependencies
10:11:41 PM: Started saving go dependencies
10:11:41 PM: Finished saving go dependencies
10:11:41 PM: Error running command: Build script returned non-zero exit code: 255
10:11:41 PM: Failing build: Failed to build site
10:11:41 PM: Finished processing build request in 17.884923232s
In order to go from source to the rendered output you need a R process with the bookdown package. That is not supported by Netlify (at the moment). However, you are already uploading the (locally) rendered book to GitHub in the _book sub-directory. This means you only have to tell Netlify that it should not try to build anything (empty "Build command") and publish the content of _book ("Publish directory" in "Build settings"). BTW, in this case there is not much gain by using Netlify over GitHub pages. If you change your output directory to docs, you can have the book published via that route.
In addition, you can use Travis CI to automatically build the book, so that you do not have to do that locally. See the build.sh and _deploy.sh scripts together with .travis.yml in the bookdown demo repository.
Newbie trying to get going with IJulia on Debian Jessie, and am stuck with an error. Don't know how to interpret the message, and not actually sure on what to do next.
The beginning is all ok :
julia> Pkg.init()
INFO: Initializing package repository /home/sybs/.julia/v0.3
INFO: Cloning METADATA from git://github.com/JuliaLang/METADATA.jl
julia> Pkg.add("IJulia")
INFO: Cloning cache of BinDeps from git://github.com/JuliaLang/BinDeps.jl.git
INFO: Cloning cache of Compat from git://github.com/JuliaLang/Compat.jl.git
INFO: Cloning cache of Conda from git://github.com/Luthaf/Conda.jl.git
INFO: Cloning cache of Dates from git://github.com/quinnj/Dates.jl.git
INFO: Cloning cache of HttpCommon from git://github.com/JuliaWeb/HttpCommon.jl.git
INFO: Cloning cache of IJulia from git://github.com/JuliaLang/IJulia.jl.git
INFO: Cloning cache of JSON from git://github.com/JuliaLang/JSON.jl.git
INFO: Cloning cache of Nettle from git://github.com/staticfloat/Nettle.jl.git
INFO: Cloning cache of SHA from git://github.com/staticfloat/SHA.jl.git
INFO: Cloning cache of URIParser from git://github.com/JuliaWeb/URIParser.jl.git
INFO: Cloning cache of ZMQ from git://github.com/JuliaLang/ZMQ.jl.git
INFO: Installing BinDeps v0.3.21
INFO: Installing Compat v0.7.11
INFO: Installing Conda v0.1.9
INFO: Installing Dates v0.3.2
INFO: Installing HttpCommon v0.1.2
INFO: Installing IJulia v1.1.8
INFO: Installing JSON v0.5.0
INFO: Installing Nettle v0.2.2
INFO: Installing SHA v0.1.2
INFO: Installing URIParser v0.0.7
INFO: Installing ZMQ v0.3.1
INFO: Building Nettle
INFO: Building ZMQ
INFO: Building IJulia
INFO: Installing Jupyter via the Conda package.
INFO: Downloading miniconda installer ...
--2016-02-23 14:43:46-- http://repo.continuum.io/miniconda/Miniconda-3.9.1-Linux-x86_64.sh
Résolution de repo.continuum.io (repo.continuum.io)… 23.21.205.0, 174.129.25.1
Connexion à repo.continuum.io (repo.continuum.io)|23.21.205.0|:80… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 23531867 (22M) [application/octet-stream]
Sauvegarde en : « /home/sybs/.julia/v0.3/Conda/deps/usr/installer.sh »
home/sybs/.julia/v0. 48%[=========> ] 10,86M 16,4KB/s eta 14m 14s/home/sybs/.julia/v 100%[=====================>] 22,44M 13,8KB/s ds 29m 43ss
Then I get a "chmod not defined" error :
INFO: Installing miniconda ...
===============================[ ERROR: IJulia ]================================
chmod not defined
while loading /home/sybs/.julia/v0.3/IJulia/deps/build.jl, in expression starting on line 35
================================================================================
================================[ BUILD ERRORS ]================================
WARNING: IJulia had build errors.
- packages with build errors remain installed in /home/sybs/.julia/v0.3
- build a package and all its dependencies with `Pkg.build(pkg)`
- build a single package by running its `deps/build.jl` script
================================================================================
INFO: Package database updated
I opened up the build.jl file and scroll before and after line35 and got this :
if jupyter_vers < v"3.0" || dirname(jupyter) == abspath(Conda.SCRIPTDIR)
info("Installing Jupyter via the Conda package.")
Conda.add("jupyter")
jupyter = abspath(Conda.SCRIPTDIR,"jupyter")
jupyter_vers = prog_version(jupyter)
jupyter_vers < v"3.0" && error("failed to find $jupyter 3.0 or later")
end
info("Found Jupyter version $jupyter_vers: $jupyter")
#######################################################################
# Warn people upgrading from older IJulia versions:
try
juliaprof = chomp(readall(pipeline(`$ipython locate profile julia`,
stderr=DevNull)))
warn("""You should now run IJulia just via `$jupyter notebook`, without
the `--profile julia` flag. IJulia no longer maintains the profile.
Consider deleting $juliaprof""")
end
#######################################################################
# Install Jupyter kernel-spec file.
So, what shall I do next ? chmod a+x build.jl ? then Pkg.build("IJulia") ?
Conda.jl author here. I do not have enough reputation to comment, so here is an answer.
Conda is tested on the latest julia 0.3, which is 0.3.12, and works there. So a possible fix would be to update your Julia version to either that or 0.4.
You can also try to install it manually, by making it executable and then running ./installer.sh -b -f -p $HOME/.julia/v0.3/Conda/deps/usr/.
I am trying to build Spark 1.2.1 on Windows with the help of sbt, and I'm running into the following issue:
Edit: The command I ran was sbt/sbt assembly
[info] Set current project to spark-parent (in build file:/C:/Programming/spark-1.2.1/)
[error] Expected symbol
[error] Not a valid command: /
[error] /sbt
[error] ^
Any help would be greatly appreciated.
I used the latest sbt Windows installer to install sbt and have Git installed on my machine.
How can I find libraries which have newer versions with sbt.
For Ruby bundler, it can be done with bundle outdated. I want to do similar thing with sbt.
There is sbt-updates which gives you latest stable and snapshot versions. Not sure how reliable it is, though.
Example run:
my-project $ sbt
[info] Set current project to my-project
> dependencyUpdates
[info] Found 14 dependency updates for my-project
[info] com.typesafe.akka:akka-actor : 2.2.1 -> 2.2.3
[info] com.typesafe.akka:akka-agent : 2.2.1 -> 2.2.3
[info] com.typesafe.akka:akka-dataflow : 2.2.1 -> 2.2.3
[info] com.typesafe.akka:akka-slf4j : 2.2.1 -> 2.2.3
[info] com.typesafe.akka:akka-testkit : 2.2.1 -> 2.2.3
[info] com.typesafe.akka:akka-zeromq : 2.2.1 -> 2.2.3
[info] org.scala-lang.plugins:continuations:plugin->default(compile) : 2.10.2 -> 2.10.3
[info] org.scala-lang:scala-library : 2.10.2 -> 2.10.3
[info] org.scalaz:scalaz-concurrent : 7.0.3 -> 7.0.5
[info] org.scalaz:scalaz-core : 7.0.3 -> 7.0.4
[info] org.scalaz:scalaz-effect : 7.0.3 -> 7.0.5
[info] org.scalaz:scalaz-iteratee : 7.0.3 -> 7.0.5
[info] org.scalaz:scalaz-typelevel : 7.0.3 -> 7.0.5
[info] org.scalaz:scalaz-xml : 7.0.3 -> 7.0.5
You can use "SBT > dependencyUpdates" in the command line. Just like described above. That will work. But that is now automated.
You can use VersionEye to monitor your build.sbt file on GitHub/Bitbucket. VersionEye will notify you about out-dated dependencies in your project, automatically via email. In that way it is completely automated and you don't have to remember to execute commands in the shell. It's like a CI Server for versions ;-)
By the way, I'm the dude who started VersionEye. Let me know if you have questions.