I was waiting this this issue. Now it is clear for me too. So we are missing this commit, right? It's worth to complete the PR#7 and restart the vote.
Gabriel, why the exception with plugin version 3.0.1 appears on your box? T On Mon, Aug 26, 2019 at 2:49 PM Gabriel Belingueres <belingue...@gmail.com> wrote: > Created https://issues.apache.org/jira/browse/MPIR-384 > > Kind regards, > Gabriel > > El lun., 26 de ago. de 2019 a la(s) 05:21, Michael Osipov ( > micha...@apache.org) escribió: > > > Am 2019-08-26 um 04:14 schrieb Gabriel Belingueres: > > > Hi: > > > > > > In the light of what Michael clarified, and after some doc reading [1], > > > quoting the following about 'mvn site': > > > "It uses *only* the parameters defined in the <configuration> element > of > > > each reporting Plugin specified in the <reporting> element, i.e. site > > > always *ignores* the parameters defined in the <configuration> element > of > > > each plugin specified in <build>." > > > > > > After testing with the plugin configuration in the <reporting> section, > > it > > > worked OK. Why it does not apply the reporting configuration when the > > > plugin is declared and configured in both the pluginManagement and > > > repoorting sections is another matter. > > > > > > I created a gist with the log files as it seems the mailing does not > > allow > > > attachments. Please see [2], but it seems less useful now. > > > > > > Regarding the missing commit, it was an improvement over the first > commit > > > (which already had the IT in place). The feature is already there and > > > working. I have no problem to raise a new issue for the next release. > > > > Please do so. > > > > @Tibor. Do you still insist on -1? > > > > @all if Tibor reverts his one, I still need another binding vote. > > >
