Install jar files from JAR-DIRECTORY to the default target directory. This is used in case the build.xml does not include an install target.

Generates the plugin.xml file that is required by Maven so it can recognize the package as a plugin, and find the entry points in the plugin.

Generates the pom.xml for a project. It is required by Maven to find a package, and by the java build system to know where to install a package, when a pom.xml doesn't already exist and installing to the maven repository.

Install a .pom file to a maven repository structure in lib/m2 that respects the file's artifact ID and group ID. This requires the parent pom, if any, to be present in the inputs so some of this information can be fetched.

Install the APIDOC-DIRECTORY to the target directory. This is used to install javadocs when this is not done by the install target.

Install a jar archive and its pom-file to a maven repository structure in lib/m2. This requires the parent pom file, if any, to be present in the inputs of the package being built. This phase looks either for a properly named jar file (artifactID-version.jar) or the single jar in the build directory. If there are more than one jar, and none is named appropriately, the phase fails.

Build the given Julia package, applying all of PHASES in order.

This function can modify a given DEFCONFIG (or .config) file by adding, changing or removing the list of strings in CONFIGS. This allows customization of Kconfig based projects like the kernel Linux or the bootloader 'Das U-Boot'.

These are examples for CONFIGS to add, change or remove configurations to/from DEFCONFIG:

'("CONFIG_A=\"a\"" "CONFIG_B=0" "CONFIG_C=y" "CONFIG_D=m" "CONFIG_E=" "# CONFIG_G is not set" ;; For convenience this abbreviation can be used for not set configurations. "CONFIG_F")

Instead of a list, CONFIGS can be a string with one configuration per line.

Verify that the CONFIG file contains all configurations from the DEFCONFIG file. When the verification fails, raise an error with the mismatching keys and their values.

Build the given package, applying all of PHASES in order, with a Linux kernel in attendance.

Generates a system which can be used by asdf to produce an image or program inside the current directory. The image or program will contain DEPENDENCIES.

Use a lisp implementation to test the TEST-SYSTEMS using asdf.

Replace invalid characters in STR with a hyphen.

If a `lib' output exists, build things there. Otherwise use `out'.

Generate an executable program containing all DEPENDENCIES, and which will execute ENTRY-PROGRAM. The result is placed in PROGRAM. When executed, it will run ENTRY-PROGRAM, a list of Common Lisp expressions in which `arguments' has been bound to the command-line arguments which were passed. Link in any asd files from DEPENDENCY-PREFIXES to ensure references to those libraries are retained.

Generate an image, possibly standalone, which contains all DEPENDENCIES, placing the result in IMAGE.image. Link in any asd files from DEPENDENCY-PREFIXES to ensure references to those libraries are retained.