If you want to include the CLI into your own programs, read the following instructions. For more info about developing DiverCLI itself, see the wiki.
With Maven: If you use Maven as build system, put this in the dependencies
section of your pom.xml
:
<dependency>
<groupId>eu.kidf</groupId>
<artifactId>divercli</artifactId>
<version>${project.version}</version>
</dependency>
Note that Wordnet 3.1 dependency will be automatically included.
Without Maven: you can download DiverCLI jar and its dependencies from here, then copy the jars to your project classpath.
In case updates are available, version numbers follow semantic versioning rules.
- See Diversicon Core dependencies.
- Diversicon Wordnet 3.1
- JCommander
Logging is configured with logback.xml
files, which during developing / testing are found in this order:
- whatever is passed by command line:
mvn test -Dlogback.configurationFile=path-to-my-logback.xml
conf/logback-test.xml
as indicated in Maven surefire plugin configurationlogback-test.xml
in test resources.
CAVEAT: stupid Eclipse doesn't pick those surefire properties by design , nor allows to apply run settings to all tests (O_o) so I went to Windows->Preferences->Java->Installed JREs->Default one->Edit
and set default VM arguments to -Dlogback.configurationFile=conf/logback-test.xml
. It's silly but could somewhat make sense for other projects too.