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
> On 2018-11-10T16:47:59 +0100
> Hervé BOUTEMY wrote:
>
> > ok, I investigated more in details and added a little trick in [1]:
> > child.site.url.inherit.append.path is inherited independantly from
> > id/name/url
> >
> > this will manage your edge case, which I can understand is expected
> >
On 2018-11-10T16:47:59 +0100
Hervé BOUTEMY wrote:
> ok, I investigated more in details and added a little trick in [1]:
> child.site.url.inherit.append.path is inherited independantly from id/name/url
>
> this will manage your edge case, which I can understand is expected
>
> do you think it i
ok, I investigated more in details and added a little trick in [1]:
child.site.url.inherit.append.path is inherited independantly from id/name/url
this will manage your edge case, which I can understand is expected
do you think it is ok?
Regards,
Hervé
[1]
https://gitbox.apache.org/repos/asf
Le mardi 6 novembre 2018, 10:35:25 CET Mark Raynsford a écrit :
> 'Ello.
>
> On 2018-11-06T00:03:53 +0100
>
> Hervé BOUTEMY wrote:
> > Hi Mark,
> >
> > even if this is somewhat a corner case (while overriding everything in b,
> > you can override the attribute also), it is strange...
>
> I'm n
'Ello.
On 2018-11-06T00:03:53 +0100
Hervé BOUTEMY wrote:
> Hi Mark,
>
> even if this is somewhat a corner case (while overriding everything in b, you
> can override the attribute also), it is strange...
I'm not sure it's a corner case, exactly. It reflects the real-life
situation I'm in: Cons
Hi Mark,
even if this is somewhat a corner case (while overriding everything in b, you
can override the attribute also), it is strange...
The more immediate check is to run "mvn help:effective-pom" on b to check that
child.site.url.inherit.append.path is configured: I still don't understand
wh
On 2018-11-04T15:05:19 +
Mark Raynsford wrote:
> On 2018-11-04T15:34:11 +0100
> Hervé BOUTEMY wrote:
>
> > you can build https://github.com/apache/maven/tree/MNG-6059 with quick
> > build
> > instruction at the end of README
> >
>
> Thanks. I've built 523db580468bc2b9d8420470bb24f5f68
On 2018-11-04T15:34:11 +0100
Hervé BOUTEMY wrote:
> you can build https://github.com/apache/maven/tree/MNG-6059 with quick build
> instruction at the end of README
>
Thanks. I've built 523db580468bc2b9d8420470bb24f5f688220701 and it
seems to be working for all but the
project/distributionManag
you can build https://github.com/apache/maven/tree/MNG-6059 with quick build
instruction at the end of README
Regards,
Hervé
Le dimanche 4 novembre 2018, 13:48:51 CET Mark Raynsford a écrit :
> On 2018-11-04T13:34:39 +0100
>
> Hervé BOUTEMY wrote:
> > Hi Mark,
> >
> > Seems you found one mor
On 2018-11-04T13:34:39 +0100
Hervé BOUTEMY wrote:
> Hi Mark,
>
> Seems you found one more thing that I forgot when merging MNG-6059:
> inheritance of these child.inherit.append.path configurations...
>
> I created MNG-6505 [1] and added the fix to MNG-6059 branch.
>
> Can you check that it wo
Hi Mark,
Seems you found one more thing that I forgot when merging MNG-6059:
inheritance of these child.inherit.append.path configurations...
I created MNG-6505 [1] and added the fix to MNG-6059 branch.
Can you check that it works as you expect? (notice: with the new
child.x.y.inherit.append.p
You need to add the group,arifcatId and version to the
dependencyManagement section of a parent.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of David Smiley
Sent: Tuesday, May 09, 2006 4:19 PM
To: m2-dev@maven.apache.org
Subject: inheritance
http://maven.apache.org/
16 matches
Mail list logo
