does not start

[commsor]

does not start

[mikub]

Hi @mfehse,
thanks for pointing this out - I can confirm that I can see this on JDK9 to JDK11.
It seems the namespaces located on classpath under titanoboa/system/ folder do not get automatically loaded during startup (they should).
Basically the auto-loading of these namespaces was supposed to be there just to make starting from scratch easier. Apparently it got broken at some point and is doing quite the opposite...

I am going to fix this, but in the meantime there is an easy workaround:

1. Update ext-dependencies.clj so as it contains [titanoboa.system.local] under the :require section, e.g.:

{:coordinates [[io.titanoboa.tasklet/pdf "0.1.0"][io.titanoboa.tasklet/aws-s3 "0.1.0"]]
 :require [[titanoboa.system.local][io.titanoboa.tasklet.aws.s3][io.titanoboa.tasklet.pdf]]
 :import nil
 :repositories {"central" "https://repo1.maven.org/maven2/"
                "clojars" "https://clojars.org/repo"}}

2. Make sure you point titanoboa to the ext-dependencies.clj (otherwise it will be recreated upon startup). Just update the start.sh script to contain:
   -Dboa.server.dependencies.path=./ext-dependencies.clj
   e.g.:

#!/bin/bash 
java -Dboa.server.dependencies.path=./ext-dependencies.clj -cp "./build/titanoboa.jar:./lib/*" titanoboa.server

Feel free to read more about the server config and dependencies at https://github.com/mikub/titanoboa/wiki/Server-Configuration

Cheers
Miro

[mikub]

This has now been fixed in this commit and the fix will go into the next release.

I also added the workaround into the current release available at https://www.titanoboa.io - so if you download the release again it should work straight away without any need for the workaround described above.

Feel free to reopen this if you still have any issues with it.