### Launching Federated Catalog as Java Process

Source: https://github.com/eclipse-edc/federatedcatalog/blob/main/README.md

This command starts the Federated Catalog as a native Java application. It configures the web server's main and catalog API paths and ports using system properties, then executes the `fc-mocked.jar` file.

```bash
java -Dweb.http.catalog.path="/api/catalog" \
     -Dweb.http.catalog.port=8181 \
     -Dweb.http.path="/api" \
     -Dweb.http.port=8080 \
     -jar launchers/catalog-mocked/build/libs/fc-mocked.jar
```

--------------------------------

### Starting Test Backend with Docker Compose

Source: https://github.com/eclipse-edc/federatedcatalog/blob/main/system-tests/end2end-test/README.md

This command uses Docker Compose to bring up the test backend services defined in `docker-compose.yml` for the End-to-End tests. The `--build` flag ensures that Docker images are built or rebuilt if necessary. By default, it keeps logs in the foreground, but can be run in the background using `-d` or `--wait` flags.

```Shell
docker-compose -f system-tests/end2end-test/docker-compose.yml up --build
```

--------------------------------

### Building Federated Catalog JAR Files (Gradle)

Source: https://github.com/eclipse-edc/federatedcatalog/blob/main/README.md

This snippet shows how to compile and package the Federated Catalog into executable JAR files using Gradle's `shadowJar` task. The first command builds the entire project, while the second specifically targets the `launchers` subproject.

```bash
./gradlew shadowJar
```

```bash
./gradlew -p launchers shadowJar
```

--------------------------------

### Building EDC Launcher JARs with Gradle

Source: https://github.com/eclipse-edc/federatedcatalog/blob/main/system-tests/end2end-test/README.md

This command builds the executable JAR files for both the `catalog-dcp` and `connector-runtime` submodules using Gradle's `shadowJar` task. These JARs are essential for the Docker containers used in the End-to-End tests, providing the necessary runtime artifacts.

```Shell
./gradlew :launchers:catalog-dcp:shadowJar
./gradlew :system-tests:end2end-test:connector-runtime:shadowJar
```

--------------------------------

### Building Federated Catalog Docker Image

Source: https://github.com/eclipse-edc/federatedcatalog/blob/main/README.md

This command constructs a Docker image for the Federated Catalog from the `catalog-mocked` launcher directory. The image is tagged as `fc`, enabling containerization of the application.

```bash
docker build -t fc ./launchers/catalog-mocked
```

--------------------------------

### Executing End-to-End JUnit Tests with Gradle

Source: https://github.com/eclipse-edc/federatedcatalog/blob/main/system-tests/end2end-test/README.md

This command executes the JUnit test cases located in the `e2e-junit` submodule using Gradle. The `-DincludeTags="EndToEndTest"` flag specifically targets and runs only those tests annotated with the 'EndToEndTest' tag, ensuring focus on the relevant End-to-End scenarios.

```Shell
./gradlew system-tests:end2end-test:e2e-junit:test -DincludeTags="EndToEndTest"
```

--------------------------------

### Running Federated Catalog in Docker Container

Source: https://github.com/eclipse-edc/federatedcatalog/blob/main/README.md

This command executes the Federated Catalog within a Docker container, removing it upon exit (`--rm`). It sets environment variables to configure the web server's API paths and ports, using the `fc:latest` image.

```bash
docker run  --rm --name fc \
    -e "WEB_HTTP_PATH=/api" \
    -e "WEB_HTTP_PORT=8080" \
    -e "WEB_HTTP_CATALOG_PORT=8181" \
    -e "WEB_HTTP_CATALOG_PATH=/api/catalog" \
    fc:latest
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.