Less literacy and more work – pure, hard, real one. I think that downloading git repository – i.e. cloning it – is a way to run TDD on QuestDB in general.

Politics is about scope

I think that the most intreaguing part is mvn clean test off the load, meaning that project itself results in an error on this scale.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project questdb: Compilation failure -> [Help 1]
[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] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

You can be brave and run it anyways. java -p core/target/questdb-5.0.5-SNAPSHOT.jar -m io.questdb/io.questdb.ServerMain -d runtime – nothing special:

Error occurred during initialization of boot layer
java.lang.module.FindException: Module io.questdb not found

I also think it’s more beneficial than customizing a package on composer.json repository to publish online; MVC likewise, has its drawbacks and advantages.

%d bloggers like this: