Hi:
Regarding the exception, there were several cases I checked:
Case 1:
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>3.0.1</version>
<configuration>
<pluginManagementExcludes>
<pluginManagementExclude>org.eclipse.m2e</pluginManagementExclude>
</pluginManagementExcludes>
</configuration>
</plugin>
</plugins>
</pluginManagement>
it was not finding the very same plugin I was testing:
"org.apache.maven.project.ProjectBuildingException: Error resolving project
artifact: Failure to find
org.apache.maven.plugins:maven-project-info-reports-plugin:pom:3.0.1 in
https://repo.maven.apache.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has
elapsed or updates are forced for project
org.apache.maven.plugins:maven-project-info-reports-plugin:pom:3.0.1"
The reason for this exception is that it could not find it when declared in
the pluginManagement section, because it tries to get it as an artifact and
it was not found. Adding the same plugin staging repo like this solved the
exception:
<repositories>
<repository>
<id>same-staged-repo</id>
<url>https://repository.apache.org/content/repositories/maven-1528
</url>
</repository>
</repositories>
I think this condition should dissapear as soon as the plugin is deployed
to Central repo?
Case 2:
Executing again with the artifact repo added caused this exception:
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure
to find org.eclipse.m2e:lifecycle-mapping:pom:1.0.0 in http://.... was
cached in the local repository, resolution will not be reattempted until
the update interval of central has elapsed or updates are forced
which is what is expected as the 'mvn site' execution does not set the
parameters in the plugin configuration section of plugins.
Case 3:
Leave the pluginManagement section but configure it in the reporting
section:
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>3.0.1</version>
</plugin>
</plugins>
</pluginManagement>
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<configuration>
<pluginManagementExcludes>
<pluginManagementExclude>org.eclipse.m2e</pluginManagementExclude>
</pluginManagementExcludes>
</configuration>
</plugin>
</plugins>
</reporting>
Works OK as long as the artifact repository is kept.
Case 4:
If I delete the artifact repository, to avoid the exception "...Failure to
find
org.apache.maven.plugins:maven-project-info-reports-plugin:pom:3.0.1..." I
excluded the plugin in the configuration (showing that the added
functionality works for the plugin itself):
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<configuration>
<pluginManagementExcludes>
<pluginManagementExclude>org.eclipse.m2e</pluginManagementExclude>
<pluginManagementExclude>org.apache.maven.plugins:maven-project-info-reports-plugin</pluginManagementExclude>
</pluginManagementExcludes>
</configuration>
</plugin>
</plugins>
</reporting>
HTH
Gabriel
El lun., 26 de ago. de 2019 a la(s) 09:59, Tibor Digana (
tibordig...@apache.org) escribió:
> 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.
> > >
> >
>
