[
https://issues.apache.org/jira/browse/ARTEMIS-2876?focusedWorklogId=549389&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-549389
]
ASF GitHub Bot logged work on ARTEMIS-2876:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Feb/21 04:04
Start Date: 08/Feb/21 04:04
Worklog Time Spent: 10m
Work Description: jbertram commented on pull request #3436:
URL: https://github.com/apache/activemq-artemis/pull/3436#issuecomment-774851296
I think that a better approach might be to create 3 sub-modules under
`artemis-junit`. You could have `artemis-junit-4`, `artemis-junit-5`, and then
`artemis-junit-commons` for all the bits they share. I'm not sure what this
would mean for backwards compatibility since the Maven coordinates would change
for existing users. Perhaps there's some Maven magic we could do to get around
that. Or perhaps we could do this change in a major version.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 549389)
Time Spent: 20m (was: 10m)
> Port artemis-junit @Rule to junit5 extensions
> ---------------------------------------------
>
> Key: ARTEMIS-2876
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2876
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Tests
> Reporter: Luís Alves
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The artemis-junit @Rule is a great feature for integration tests. Would be
> nice to be ported to Junit5 so projects don't need to mix vintage (Junit4)
> and Junit5 tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
