bld Build Tool

A bld project is defined by extending the rife.bld.Project class. You configure project metadata (package, name, version, main class) and dependencies within the constructor.

Dependencies can be defined using the dependency(group, artifact, version) helper or via a colon-separated string format "group:artifact:version".

package com.example;

import rife.bld.Project;
import java.util.List;
import static rife.bld.dependencies.Repository.*;
import static rife.bld.dependencies.Scope.*;

public class MyAppBuild extends Project {
    public MyAppBuild() {
        pkg = "com.example";
        name = "my-app";
        mainClass = "com.example.MyApp";
        version = version(0,1,0);

        downloadSources = true;
        repositories = List.of(MAVEN_CENTRAL, RIFE2_RELEASES);
        scope(test)
            .include(dependency("org.junit.jupiter", "junit-jupiter", version(6,1,3)))
            .include(dependency("org.junit.platform", "junit-platform-console-standalone", version(6,1,3)));
    }

    public static void main(String[] args) {
        new MyAppBuild().start(args);
    }
}

In bld, extension declarations are managed separately from project dependencies. While project dependencies are declared in the build file's Java code, extension declarations live in the wrapper properties on disk.

ExtensionClasspath is responsible for reading these wrapper properties and resolving the classpath JARs for a specific dependency within the extensions. It uses a BldCache to ensure that if the extension declarations (repositories, extensions, and version overrides) haven't changed, it can quickly retrieve cached JARs instead of re-resolving the entire dependency tree.

Key behaviors:

• Isolation: Extension declarations are read via the Wrapper to ensure consistency between the wrapper and the build process.
• Caching: The resolution process is fingerprinted based on the repositories, extensions, and version overrides. If these change, the cache is considered stale.
• Scope: When resolving dependencies, it considers both Scope.compile and Scope.runtime scopes.

// Note: ExtensionClasspath is an internal class used by the build system to resolve extension JARs.
// It is not intended to be instantiated directly by end-users.

To obtain the list of JAR files required for a specific dependency within the extensions, the system uses the classpathJars method. This method performs the following steps:

1. Checks the BldCache using a hash of the current repositories, extensions, and version overrides.
2. If a valid cache exists for the given coordinate, it returns the cached files.
3. If no cache is valid, it uses a ParallelDependencyResolver to resolve all extension dependencies for Scope.compile and Scope.runtime.
4. It then uses a DependencyResolver to find all transitive dependencies for the specific requested dependency.
5. Finally, it transfers the files to the libBldDirectory and updates the cache.

Parameters:

• dependency: The Dependency object representing the target extension dependency.
• coordinate: A string representation of the dependency's coordinate (used for cache lookups).

Throws:

• IllegalArgumentException: If the requested coordinate is not part of the project's extensions.

// Conceptual usage within the bld build engine:
List<File> jars = extensionClasspath.classpathJars(dependency, "group:artifact:version");