Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reporting configuration should be done in <reporting> section, not in maven-site-plugin <configuration> as reportPlugins parameter. #3205

Closed
elharo opened this issue Apr 27, 2018 · 0 comments
Closed

Reporting configuration should be done in <reporting> section, not in maven-site-plugin <configuration> as reportPlugins parameter. #3205

elharo opened this issue Apr 27, 2018 · 0 comments
Assignees
@chingor13
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. type: process A process-related concern. May include testing, release, or the like.

Comments

@elharo
Copy link
Contributor

elharo commented Apr 27, 2018

While building google-cloud-bom

[WARNING] 
[WARNING] Some problems were encountered while building the effective model for com.google.cloud:google-cloud-core:jar:1.27.1-SNAPSHOT
[WARNING] Reporting configuration should be done in <reporting> section, not in maven-site-plugin <configuration> as reportPlugins parameter.
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
@andreamlin andreamlin added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. type: process A process-related concern. May include testing, release, or the like. labels May 21, 2018
@chingor13 chingor13 self-assigned this Oct 9, 2018
@andreamlin andreamlin mentioned this issue Oct 9, 2018
Merged
@chingor13 chingor13 added the status: in progress There is an open PR label Oct 9, 2018
@chingor13 chingor13 removed status: in progress There is an open PR labels Oct 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chingor13 chingor13

Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chingor13 @elharo @andreamlin