Jeka has predefined methods that comes either from
JkClass or built-in plugins.
jeka help: Displays methods and options invokable from command line, along with plugins available in the classpath.
jeka [kbean-name]#help: Displays methods and options invokable for the specified plugin (e.g.
jeka intellij#iml: Generates iml file for Intellij. This is generated according to the dependencies declared for Jeka project.
jeka intellij#iml -JKC=: If the
jeka intellij#imlfails due to the non-compile def classes,
-JKC=will avoid def compilation phase.
jeka eclipse#files: Same purpose as above to generate metadata files for Eclipse.
jeka scaffold#run: Generates files to create a basic Jeka project from scratch.
jeka scaffold#wrapper: Generates wrapper files (jekaw/jekaw.bat and bootstrap jar).
jeka scaffold#run java#: Generates files to create a Jeka project to build a JVM language project.
Useful standard options¶
You can add the below options to the command line.
-kb=[KBeanName]: By default, Jeka instantiates the first KBean found under def directory to execute methods. It can be forced to instantiate a specific class by passing its long or short name. If the class is already in classpath, then no def compilation occurs.
-JKC=is simply equivalent to
-JKC=JkClasswhich is the base class bundled in Jeka.
-lri: Displays runtime info which will be displayed meaningfully on the console about current Jeka version, Java version, base directory, download repository, classpath, ...
-lsu: Shows logs about Jeka setup (compilation of def classes, plugin loading, ...). This information is not logged by default.
-ls=BRACE: Alters console output by delimiting tasks with braces and mentioning the processing time for each task.
-ls=DEBUG: Alters console output by showing the class name and line number where the log has been emitted.
-lv: Alters console output by displaying trace logs (emitted by
-cw: Clean .work directory, forcing compilation of def classes, even if it is marked as being up-to-date.
Change the JDK that Runs Jeka¶
To determine the JDK to run upon, Jeka looks at, in order of priority :
- JEKA_JDK environment variable ([JEKA_JDK]/bin/java must point on java executable)
- JAVA_HOME environment variable
If none of the above variables are present, Jeka will run on the java executable accessible from the PATH environment.
Change the Repository Jeka uses to Fetch Dependencies¶
By default, Jeka fetch dependencies from Maven central (https://repo.maven.apache.org/maven2).
Another default repository can be selected by setting the
It has been recommended to store this value in your [USER DIR]/.jeka/options.properties file to be reused across projects.
For more details, please see