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. With this new information, my vote now is a +1. Kind regards, Gabriel [1] https://maven.apache.org/guides/mini/guide-configuring-plugins.html#Configuring_Reporting_Plugins [2] https://gist.github.com/belingueres/8ceb548e2ef43dca3687d3bd6eaa93ef El dom., 25 de ago. de 2019 a la(s) 13:04, Tibor Digana ( tibordig...@apache.org) escribió: > Michael, this is true but the second problem is a missed commit? Where is > the commit? It is not in the PR. > Gabriel, the log file was not attached. > And the third problem is an exception which we could not see because the > log is not in the attachements. > > On Sun, Aug 25, 2019 at 5:14 PM Michael Osipov <micha...@apache.org> > wrote: > >> Am 2019-08-24 um 21:41 schrieb Gabriel Belingueres: >> > Hi: >> > >> > Regarding MPIR-375, I noted that the merge of the PR into master branch >> was >> > done *before* I made changes using PatternExcludesArtifactFilter based >> on >> > the reviews. >> > >> > See https://github.com/apache/maven-project-info-reports-plugin/pull/7. >> > The commit in master is: >> > >> https://github.com/apache/maven-project-info-reports-plugin/commit/82f4bf23b79fe87d2e414c70ab2058e8f1b4146b >> > >> > The patch should work anyway so I decided to test it with the >> > maven-shared-utils library. >> > I added this to the pom.xml file (in addition to adding the >> staged-releases >> > profile to settings.xml with the staged repo): >> > >> > <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> >> > >> > With version 3.0.1, running 'mvn -V -Pstaged-releases clean site > >> > 3.0.1.log' throws an exception. (see 3.0.1.log attached file) >> > >> > However, when building 3.0.2-SNAPSHOT and installing in the local repo >> > (please see that in git repo there are no new commits after the 3.0.1 >> > release), changing the version to 3.0.2-SNAPSHOT works as expected: >> > >> > mvn -V -Pstaged-releases clean site > 3.0.2-SNAPSHOT.log >> > >> > Does anyone else is having this problem? Or am I doing something wrong? >> >> I cannot confirm: >> > $ mvn -V -Pstaged-releases clean site >> > Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; >> 2018-06-17T20:33:14+02:00) >> > Maven home: D:\Entwicklung\Programme\apache-maven-3.5.4 >> > Java version: 1.8.0_192, vendor: Oracle Corporation, runtime: >> C:\Program Files\Java\jdk1.8.0_192\jre >> > Default locale: de_DE, platform encoding: Cp1252 >> > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" >> > [INFO] Scanning for projects... >> > [INFO] >> > [INFO] -------------< org.apache.maven.shared:maven-shared-utils >> >------------- >> > [INFO] Building Apache Maven Shared Utils 3.2.2-SNAPSHOT >> > [INFO] --------------------------------[ jar >> ]--------------------------------- >> > [INFO] >> > [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ >> maven-shared-utils --- >> > [INFO] Deleting D:\Entwicklung\Projekte\maven-shared-utils\target >> > [INFO] >> > [INFO] --- maven-site-plugin:3.7.1:site (default-site) @ >> maven-shared-utils --- >> > [INFO] configuring report plugin >> org.apache.maven.plugins:maven-project-info-reports-plugin:3.0.1 >> > [INFO] 15 reports configured for >> maven-project-info-reports-plugin:3.0.1: index, summary, dependency-info, >> modules, team, scm, issue-management, mailing-lists, dependency-management, >> dependencies, dependency-convergence, ci-management, plugin-management, >> plugins, distribution-management >> > [INFO] Rendering site with default locale English (en) >> > [INFO] Relativizing decoration links with respect to localized project >> URL: https://maven.apache.org/shared/maven-shared-utils/ >> > [INFO] Rendering content with >> org.apache.maven.skins:maven-fluido-skin:jar:1.7 skin. >> > [INFO] Skipped "About" report >> (maven-project-info-reports-plugin:3.0.1:index), file "index.html" already >> exists. >> > [INFO] Rendering 2 Doxia documents: 1 apt, 1 xdoc >> > [INFO] Generating "Summary" report --- >> maven-project-info-reports-plugin:3.0.1:summary >> > [INFO] Generating "Dependency Information" report --- >> maven-project-info-reports-plugin:3.0.1:dependency-info >> > [INFO] Generating "Team" report --- >> maven-project-info-reports-plugin:3.0.1:team >> > [INFO] Generating "Source Code Management" report --- >> maven-project-info-reports-plugin:3.0.1:scm >> > [INFO] Generating "Issue Management" report --- >> maven-project-info-reports-plugin:3.0.1:issue-management >> > [INFO] Generating "Mailing Lists" report --- >> maven-project-info-reports-plugin:3.0.1:mailing-lists >> > [INFO] Generating "Dependency Management" report --- >> maven-project-info-reports-plugin:3.0.1:dependency-management >> > [INFO] Generating "Dependencies" report --- >> maven-project-info-reports-plugin:3.0.1:dependencies >> > [INFO] Generating "Dependency Convergence" report --- >> maven-project-info-reports-plugin:3.0.1:dependency-convergence >> > [INFO] Generating "CI Management" report --- >> maven-project-info-reports-plugin:3.0.1:ci-management >> > [INFO] Generating "Plugin Management" report --- >> maven-project-info-reports-plugin:3.0.1:plugin-management >> > [INFO] Generating "Plugins" report --- >> maven-project-info-reports-plugin:3.0.1:plugins >> > [INFO] Generating "Distribution Management" report --- >> maven-project-info-reports-plugin:3.0.1:distribution-management >> > [INFO] >> ------------------------------------------------------------------------ >> > [INFO] BUILD SUCCESS >> > [INFO] >> ------------------------------------------------------------------------ >> > [INFO] Total time: 7.428 s >> > [INFO] Finished at: 2019-08-25T17:12:40+02:00 >> > [INFO] >> ------------------------------------------------------------------------ >> > [WARNING] The requested profile "staged-releases" could not be >> activated because it does not exist. >> >> with this patch: >> > $ git diff >> > diff --git a/pom.xml b/pom.xml >> > index 01763d98f..f3b4d7882 100644 >> > --- a/pom.xml >> > +++ b/pom.xml >> > @@ -154,5 +154,21 @@ >> > </plugin> >> > </plugins> >> > </build> >> > + >> > + <reporting> >> > + <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> >> > + </reporting> >> > >> > </project> >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >>
