[
https://issues.apache.org/jira/browse/MPLUGINTESTING-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906705#comment-17906705
]
Harald Aamot commented on MPLUGINTESTING-93:
--------------------------------------------
Hi [~sjaranowski] ,
sorry to bother again..
When adding documentation for maven-plugin-testing..
in the repo we have the master and the maven-plugin-testing-3.x branch.
I guess the documentation only gets published via the master branch pipeline
run?
I plan to make a Docu PR against the master branch which thenb could get merged
after/witjh the 3.4.0 release?
Let me know if this approach fits.
My existing PR [https://github.com/apache/maven-plugin-testing/pull/49] that
marks JUnit4 tests as deprecated in the 3.4.0 release (in the 4.x.x/master
release line JUnit4 support is anyhow removed..) will then be decoupled from
the pure documentation related PR.
> Prepare documentation / examples for JUnit 5 and Maven 3/4
> ----------------------------------------------------------
>
> Key: MPLUGINTESTING-93
> URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-93
> Project: Maven Plugin Testing
> Issue Type: Task
> Reporter: Slawomir Jaranowski
> Priority: Blocker
> Attachments: image-2024-12-13-17-28-51-423.png
>
>
> We have implementation but documentation is lack ...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
