[ 
https://issues.apache.org/jira/browse/MENFORCER-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762062#comment-17762062
 ] 

Michael Osipov edited comment on MENFORCER-491 at 9/5/23 12:03 PM:
-------------------------------------------------------------------

[~sjaranowski], no explicit report sets have been configured. But I guess you 
are right, there should be warning, if the plugin does not contain any report 
mojos or the one you have configured aren't present in the plugin. Please raise 
an issue. This is like a {{maven-reporting-exec}} issue.


was (Author: michael-o):
[~sjaranowski], no explicit report sets have been configured. But I guess you 
are right, there should be warning, if the plugin does not contain any report 
mojos or the one you have configured aren't present in the plugin. Please raise 
an issue.

> ENFORCER: plugin-info and mojo pages not found
> ----------------------------------------------
>
>                 Key: MENFORCER-491
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-491
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>    Affects Versions: 3.4.0
>            Reporter: Jörg Hohwiller
>            Priority: Critical
>             Fix For: next-release
>
>
> I get "page not found" for these pages that should actually be there:
> https://maven.apache.org/enforcer/maven-enforcer-plugin/plugin-info.html
> https://maven.apache.org/enforcer/maven-enforcer-plugin/help-mojo.html
> ... (all other mojos) ...
> The usage page is present:
> https://maven.apache.org/enforcer/maven-enforcer-plugin/usage.html
> From there you can click "Goals" from the menu to get to the first listed 
> missing page.
> Other plugins still seem to have the generated goals overview and their 
> details pages:
> https://maven.apache.org/plugins/maven-resources-plugin/plugin-info.html
> Is enforcer using a broken version of project-info-reports or is it using a 
> custom process to publish the maven site that is buggy?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to