Well, this is the result:
osipovmi@deblndw011x:~/var/Projekte/michael-o/michael-o-parent/target/site 
(main =)
$ ll
total 80
drwxr-xr-x  2 osipovmi  cad    512 2024-09-09 09:34 css/
-rw-r--r--  1 osipovmi  cad   4178 2024-09-09 09:34 dependency-info.html
drwxr-xr-x  2 osipovmi  cad    512 2024-09-09 09:34 fonts/
drwxr-xr-x  4 osipovmi  cad   1024 2024-09-09 09:34 images/
drwxr-xr-x  2 osipovmi  cad    512 2024-09-09 09:34 img/
-rw-r--r--  1 osipovmi  cad   3055 2024-09-09 09:34 index.html
drwxr-xr-x  2 osipovmi  cad    512 2024-09-09 09:34 js/
-rw-r--r--  1 osipovmi  cad  14805 2024-09-09 09:34 licenses.html
-rw-r--r--  1 osipovmi  cad   4294 2024-09-09 09:34 project-info.html
-rw-r--r--  1 osipovmi  cad   4403 2024-09-09 09:34 scm.html
-rw-r--r--  1 osipovmi  cad   4496 2024-09-09 09:34 summary.html
-rw-r--r--  1 osipovmi  cad   4472 2024-09-09 09:34 team.html

It does not prevent unless the plugin detects that it is run from a POM type 
and skips the execution. I can totally live with that because one does not need 
to add those reports to the  site.xml.

On 2024/09/08 16:12:19 Konrad Windszus wrote:
> Hi,
> How does this prevent running the reports for the parent itself?
> 
> Konrad
> 
> > On 8. Sep 2024, at 09:12, Michael Osipov <micha...@apache.org> wrote:
> > 
> > Am 2024-09-06 um 11:06 schrieb Konrad Windszus:
> >> Hi,
> >> Unlike plugin (with plugin management and its configuration) the reportSet 
> >> (https://maven.apache.org/ref/3.9.9/maven-model/maven.html#class_reportSet)
> >>  cannot be configured on a POM level which itself should not have the 
> >> configured reports.
> >> Once a reportSuite is configured it is active both on the current project 
> >> and inheriting ones. What I want to achieve is a common report set for all 
> >> children without being active on the parent itself.
> >> Any idea?
> > 
> > Doesn't this approach work for you: 
> > https://github.com/michael-o/michael-o-parent/blob/7e7b52bcfb04c483af5a89f2b5b25ec3d900f2ec/pom.xml#L288-L368
> > 
> > For me it does in my personal projects...
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to