ascheman opened a new pull request, #310: URL: https://github.com/apache/maven-source-plugin/pull/310
## Problem The master `Verify` build has been red since late June: every run fails at the site step with ``` Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.22.0:site (default-site): skin cannot be null ``` The site 2.0.0 descriptor (`SITE/2.0.0`) no longer supplies a default skin, so maven-site-plugin 3.22.0 requires an explicit `<skin>` element, and `src/site/site.xml` doesn't declare one. (The parent's skin is declared only in maven-parent's own `site.xml`; it is not published as an inheritable site-descriptor artifact — `-X` shows `No parent level 1/2/3 site descriptor` — so it never reaches this project.) This single failure blocks the whole repo: since master is red, every open PR inherits a red CI and nothing can be merged. ## Fix Declare `maven-fluido-skin` explicitly in `site.xml` — five lines, no source or dependency changes. ## Why this is the minimal change The `-P run-its verify` build itself (including the `reproducible` IT that deploys via `file://`) is already **green** on `4.0.0-beta-3` — the site skin is the *only* thing failing. I verified the skin-only change on a fork: the full `Verify` matrix passes **8/8** (ubuntu/macos/windows x JDK 17/21/25) against `4.0.0-beta-3` — https://github.com/aschemaven/maven-source-plugin/actions/runs/29831325551. This is intentionally the minimal subset needed to unblock CI. It overlaps with the site-skin part of #309, but without that PR's IT-plumbing/transport changes, which aren't needed to make the build green on beta-3. ## Testing `mvn clean site` and the full `-P run-its verify` matrix pass on 4.0.0-beta-3 (fork run linked above). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
