Build problems. about fairdatapoint HOT 8 CLOSED

Hi @harryhoch, that's strange and certainly unexpected behaviour. Did you try with a freshly cloned repository? And which version of java are you running?

from fairdatapoint.

Running from a freshly-cloned repository on both master and develop. Java info below - running on OS X.

(base) harry@x86_64-apple-darwin13 FAIRDataPoint % java -version
java version "1.8.0_191"
Java(TM) SE Runtime Environment (build 1.8.0_191-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)

from fairdatapoint.

Are you able to upgrade your java version? The codebase requires a minimum of jdk14. Alternatively, you could try to run the docker images, as describes in the docs here: https://fairdatapoint.readthedocs.io/en/latest/deployment/local-deployment.html#local-deployment

from fairdatapoint.

I upgraded to jdk15 and found the same issues.

after digging around, I found some advice to run repackage, so I tried..
mvn clean package spring-boot:repackage

several tests failed, so I ran with skipping tests:
mvn clean package spring-boot:repackage -DskipTests

this work, and then I went back to

mvn spring-boot:start, which went much further. Unfortunately, this eventually blew up as well:

20-11-18 09:41:54,294 12971 [main] INFO org.mongodb.driver.cluster - Cluster description not yet available. Waiting for 30000 ms before timing out
2020-11-18 09:42:10,968 29645 [cluster-ClusterId{value='5fb532ae586f6b119474b1c6', description='null'}-mongo:27017] INFO org.mongodb.driver.cluster - Exception in monitor thread while connecting to server mongo:27017
com.mongodb.MongoSocketOpenException: Exception opening socket
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:70) ~[mongodb-driver-core-3.11.2.jar:?]
at com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:128) ~[mongodb-driver-core-3.11.2.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:117) [mongodb-driver-core-3.11.2.jar:?]
at java.lang.Thread.run(Thread.java:832) [?:?]
Caused by: java.net.SocketTimeoutException: Connect timed out
at sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:546) ~[?:?]
at sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:597) ~[?:?]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:333) ~[?:?]
at java.net.Socket.connect(Socket.java:648) ~[?:?]
at com.mongodb.internal.connection.SocketStreamHelper.initialize(SocketStreamHelper.java:64) ~[mongodb-driver-core-3.11.2.jar:?]
at com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:79) ~[mongodb-driver-core-3.11.2.jar:?]
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:65) ~[mongodb-driver-core-3.11.2.jar:?]

from fairdatapoint.

I now see that the spring-boot:start goal, as mentioned on the README, doesn't invoke the repackage goal. I'm used to using the spring-boot:run goal, which either includes the repackage goal, or runs from the compiled sources directly.

I also see that the mongo dependency is not mentioned on the readme. The application assumes a mongodb instance running (by default on localhost:27017 but this can be customized in the application.yml configuration) at boot. You can easily start a mongo instance using docker.

I'll make these two points more clear in the readme. Apologies for this inconvenience.

from fairdatapoint.

I just realized that the default configuration if run this way is to assume the values in src/main/resources/application.yml, which assumes the docker setup. To configure the mongodb instance when running locally, you can create an application.yml file in the project root, with the following content (see more here in the docs):

# application.yml

spring:
    data:
        mongodb:
            uri: mongodb://localhost:27017/fdp

from fairdatapoint.

ok. thanks. will try that out and will let you know if there are further problems.

from fairdatapoint.

that works!

from fairdatapoint.