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 cad512 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 cad512 2024-09-0
Hi,
How does this prevent running the reports for the parent itself?
Konrad
> On 8. Sep 2024, at 09:12, Michael Osipov 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/re
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.
On
Here's ChatGPT's answer... :-)
To create a common `reportSet` that is applied to all child projects
but not activated in the parent POM itself, you can use a few Maven
techniques, such as creating a profile or leveraging inheritance in a
way that allows the children to inherit the `reportSet` but
