[
https://issues.apache.org/jira/browse/MPLUGIN-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498112#comment-17498112
]
ASF GitHub Bot commented on MPLUGIN-395:
----------------------------------------
michael-o commented on pull request #74:
URL:
https://github.com/apache/maven-plugin-tools/pull/74#issuecomment-1050824506
> Maybe we should have separate upgrades of one plugin and independent
upgrade of it tests? To easier detect if plugin updates not affects old it
tests?
I totally agree with you and will explain why I did this in one go:
* Both API/Impl go hand on hand for Doxia 2 preparation
* When you update both reporting components ITs start to fail
Basically spilitting up is posslbe, but will leave commits in broken state
that is why I have them together. In other projects I have upgraded ITs
completely separately.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Upgrade Maven Reporting API/Impl to 3.1.0
> -----------------------------------------
>
> Key: MPLUGIN-395
> URL: https://issues.apache.org/jira/browse/MPLUGIN-395
> Project: Maven Plugin Tools
> Issue Type: Dependency upgrade
> Affects Versions: 3.6.4
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.7.0
>
>
> In alignment with Doxia (Sitetools) 1.11.1 need to bump Reporting components
> as well. Along with them MSITE and MPIR too otherwise we have failures.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
