[
https://issues.apache.org/jira/browse/MPLUGIN-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616692#comment-17616692
]
ASF GitHub Bot commented on MPLUGIN-423:
----------------------------------------
gnodet commented on PR #147:
URL:
https://github.com/apache/maven-plugin-tools/pull/147#issuecomment-1276741523
> > I would like to have a report in maven-plugin-plugin module which simply
extends reports from new module. We can override `executeReport` methods with
warning and call supper.
> > In such way we need not to duplicate code. What do you thing?
> > We should have a separate java package in separate module.
>
> I suppose it would be a bit cleaner. What I had in mind was to switch to
4.0-SNAPSHOT soon after the 3.7 release. So not sure it's really worth the
extra work, but I'll try it anyway.
I was about to try, but I realized there is problem with this approach. I
think it makes sense to keep the ITs with the report. However, the ITs
actually need the `maven-plugin-plugin` to generate the plugins and then run
the `site` goal. This means a cyclic dependency, which would have to be broken
by moving back the ITs to the `maven-plugin-plugin` or to a new module... so
not really sure the end state would be really better.
> Extract plugin report into its own plugin
> -----------------------------------------
>
> Key: MPLUGIN-423
> URL: https://issues.apache.org/jira/browse/MPLUGIN-423
> Project: Maven Plugin Tools
> Issue Type: Task
> Reporter: Guillaume Nodet
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
