ouch, "disabling" = "associating to an unknown phase": what a hack! nice idea :)
there is no such phase association in reports: this hack for plugins can't be used with reports What can be done is adding some reportExcludes in maven-site-plugin configuration: not so easy to configure and explain, but can be done without adding a parameter to every report plugin Is this requirement worth the effort and complexity? Regards, Hervé Le lundi 20 mars 2017, 09:05:07 CET Karl Heinz Marbaise a écrit : > Hi Hervé, > > On 20/03/17 08:31, Hervé BOUTEMY wrote: > > adding a skip parameter to every plugin is a workaround: better than > > nothing > > > > should that be possible? > > as a user, I want everything: I'd like it to be possible, or I'll be > > frustrated because "Maven is inflexible" :) > > ;-) > > > the big question is more IMHO: is it possible to add this feature in a > > consistent and easy to understand way? > > Thats exactly the question I'm asking myself... > > > When you say it is feasible with plugins, can you precise how, please? > > We'll see if we can adpot the same way of doing with report plugins > > Using an approach like this: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-enforcer-plugin</artifactId> > <executions> > <execution> > <id>enforce-maven</id> > <phase>UNKNOWN</phase> > </execution> > </executions> > </plugin> > > This will just simply turn off maven-enforcer-plugin completely.. > > Only for the id you need to be very carefull...You can do the executions > of this appropriate plugin and bind it to an unknown life cycle phase. > > To be honest this feels like a Hack! The skip would be more convenient > way from a user point of view but I think we need to reconsider this and > a take deeper look and may be we find a better solution... > > Kind regards > Karl Heinz Marbaise > > > Regards, > > > > Hervé > > > > Le lundi 20 mars 2017, 13:54:24 CET Maxim Solodovnik a écrit : > >> Hello Karl, > >> > >> I guess you can "skip" report for subproject? > >> > >> On Mon, Mar 20, 2017 at 1:48 PM, Karl Heinz Marbaise <khmarba...@gmx.de> > > > > wrote: > >>> Hi Hervé, > >>> > >>> On 19/03/17 23:39, Hervé BOUTEMY wrote: > >>>> That's the first time I see this part of the doc: defining an empty > >>>> reportSet > >>>> could remove a report plugin? I'm not convinced it ever worked. > >>> > >>> Me neither and made the experience that this will not work. > >>> > >>> But in the end this means a report can not being turned off in a sub > >>> project...which in contradiction is possible with plugins.. > >>> > >>> So the question is: Should that be possible ? > >>> > >>> Kind regards > >>> Karl Heinz Marbaise > >>> > >>>> to me, it is inconsistent with following documentation, associated to > >>>> an > >>>> IT: > >>>> http://maven.apache.org/plugins/maven-site-plugin/ > >>>> maven-3.html#Inheritance_of_reports_for_Maven_3_before_3.0.4 > >>>> > >>>> Reports are additive: they were not in Maven 3.0 to 3.0.3, and it was > >>>> identified as a bug. > >>>> > >>>> Regards, > >>>> > >>>> Hervé > >>>> > >>>> Le dimanche 19 mars 2017, 11:28:06 CET Karl Heinz Marbaise a écrit : > >>>>> Hi, > >>>>> > >>>>> currently I stumbled over a thing which I don't understand. > >>>>> > >>>>> I have parent pom[1] which defines several parts of a site including > >>>>> some reports for example maven-changes-plugin with github-report.. > >>>>> > >>>>> Now I inherit from that parent pom and of course I can do a mvn site. > >>>>> > >>>>> But now the important part. > >>>>> > >>>>> I would like to deactive maven-changes-plugin in particular > >>>>> github-report...cause this test project does not has a github repo > >>>>> which > >>>>> will fail the mvn site build.. > >>>>> > >>>>> I have taken a look into the documentation[2] to find a way to > >>>>> deactive > >>>>> github-report or maven-changes-plugin at all...I tried to change > >>>>> maven-project-info-reports parts etc. but without any luck.. > >>>>> > >>>>> Does someone has a good hint how to do this ? > >>>>> > >>>>> Kind regards > >>>>> Karl Heinz Marbaise > >>>>> > >>>>> [1]: https://github.com/khmarbaise/smpp/blob/master/pom.xml > >>>>> [2]: http://maven.apache.org/pom.html#Reporting > >>> > >>> --------------------------------------------------------------------- > > --------------------------------------------------------------------- > 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
