Hi Radu, I never use the site goals "deploy" or "stage" for Sling modules. Instead of the former we have a rather manual process outlined in https://sling.apache.org/documentation/development/release-management.html#appendix-b-deploy-maven-plugin-documentation-if-applicable. The latter is only useful to test links between module sites in a multi module build. I don't think we have that use case in Sling.
The distributionManagement url I removed from parent was invalid and IMHO never used. Any reason why a simple "mvn clean site" does not suffice to test the Maven site? Konrad > On 21. Sep 2021, at 18:35, Radu Cotescu <[email protected]> wrote: > > Hello, > > I noticed that commit [0] removed the site distribution management section. > Without this the site:stage goal fails for our Maven plugins, with the > following error: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.9.1:stage (default-cli) on > project scriptingbundle-maven-plugin: Missing site information in the > distribution management of the project Apache Sling Scripting Bundle Maven > Plugin (org.apache.sling:scriptingbundle-maven-plugin:0.4.1-SNAPSHOT) > > The referenced project uses version 45 of the parent pom. Should we manually > add the distributionManagement section to the Maven plugins? I’ve currently > added something like the following in this project: > > <distributionManagement> > <site> > <id>staging</id> > <url>file:${project.build.directory}/staging</url> > </site> > </distributionManagement> > Thanks, > Radu > > [0] - > https://github.com/apache/sling-parent/commit/a36d73b749732554fc703380e55fbe649219d234
