slachiewicz opened a new pull request, #1354:
URL: https://github.com/apache/maven-site-plugin/pull/1354

   `site:stage` deploys to a `file:` URL through Wagon and found the provider 
only because Maven ships `wagon-file` in `lib/`. The plugin now declares 
`wagon-file` itself, so staging keeps working on a distribution without it; on 
a stock distribution the provider is then visible from both the core and the 
plugin realm, which works too. `wagon-http` is not added: `site:deploy` to a 
plain `http:` URL already fails on stock Maven with "Wagon protocol 'http' 
doesn't support directory copying", so HTTP deployments use `dav:` with an 
extension, as before.
   
   Verified: on a Maven 3.9.16 copy without `lib/wagon-file*` and 
`lib/wagon-http*`, `site:stage` on master fails with `Cannot find wagon which 
supports the requested protocol: file`; with this change `mvn -Prun-its verify 
-Dinvoker.test=site-sd,site-sd-2,site-sd-lang,site-deploy 
-Dinvoker.mavenHome=<that copy>` → 4 passed, and on stock 3.9.16 
`-Dinvoker.test='site-sd*,site-deploy'` → 10 passed.
   


-- 
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]

Reply via email to