Use npx for Playwright browser installation in CI workflow

[Copilot]

CI workflow fails at Playwright browser installation step. This PR fixes the issue by using npx to install Playwright browsers, aligning with the devcontainer approach.

Changes

• .github/workflows/ci.yml: Updated Playwright browser installation command (line 36)
  • Changed from Maven-based approach to npx playwright install --with-deps chromium
  • Matches devcontainer setup at .devcontainer/devcontainer.json:15
  • Leverages existing Node.js setup (lines 24-27 in CI workflow)

npx playwright install --with-deps chromium

Why This Approach

• Consistency: Aligns with devcontainer's Playwright installation method
• Simplicity: Uses existing Node.js setup already configured in CI
• Reliability: Avoids Maven classloading issues entirely
• Maintainability: No additional Maven plugin configuration needed

This unblocks the CI step at .github/workflows/ci.yml:36 that installs Chromium for frontend E2E tests.

Original prompt

Problem

The CI workflow is failing when trying to install Playwright browsers with the following error:

Failed to execute goal org.codehaus.mojo:exec-maven-plugin:3.6.2:java (default-cli) on project my-app: 
An exception occurred while executing the Java class. com.microsoft.playwright.CLI

The workflow step at .github/workflows/ci.yml:36 runs:

mvn exec:java -e -D exec.mainClass=com.microsoft.playwright.CLI -D exec.args="install --with-deps chromium"

However, the pom.xml is missing the exec-maven-plugin configuration needed to execute the Playwright CLI.

Solution

Add the exec-maven-plugin to the pom.xml in the <build><plugins> section with proper configuration to allow running the Playwright CLI for browser installation.

Add this plugin configuration after the maven-compiler-plugin (around line 154):

<plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>exec-maven-plugin</artifactId>
    <version>3.1.0</version>
    <configuration>
        <mainClass>com.microsoft.playwright.CLI</mainClass>
    </configuration>
</plugin>

Validation

After making this change:

1. The CI workflow should successfully run the Playwright browser installation step
2. The command mvn exec:java -e -D exec.mainClass=com.microsoft.playwright.CLI -D exec.args="install --with-deps chromium" should work correctly
3. All existing tests should continue to pass

Files to Modify

• pom.xml - Add the exec-maven-plugin configuration in the build plugins section

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[macintorsten]

The better solution would be to change the CI workflow to use npx playwright install --with-deps chromium instead of the Maven approach, since:

Your devcontainer already uses npx (line 15 of .devcontainer/devcontainer. json)
Your CI workflow already has Node.js set up (lines 24-27 of .github/workflows/ci.yml)
This avoids the Maven classloading issues entirely

[macintorsten]

@copilot Can you adjust and use npx and is done in .devcontainer

[Copilot]

@copilot Can you adjust and use npx and is done in .devcontainer

Done! Changed to use npx playwright install --with-deps chromium in the CI workflow (commit ea90014). The exec-maven-plugin has been removed from pom.xml. This now matches the devcontainer approach and leverages the existing Node.js setup.