[
https://issues.apache.org/jira/browse/SUREFIRE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682775#comment-16682775
]
ASF GitHub Bot commented on SUREFIRE-1585:
------------------------------------------
Tibor17 commented on a change in pull request #196: [SUREFIRE-1585] [WIP]
Resolve missing and align "JUnit 5" artifacts
URL: https://github.com/apache/maven-surefire/pull/196#discussion_r232477337
##########
File path:
surefire-providers/surefire-junit-platform/src/main/java/org/apache/maven/surefire/junitplatform/RunListenerAdapter.java
##########
@@ -243,7 +243,7 @@ private StackTraceWriter getStackTraceWriter(
TestIdentifier testIdentifier, Thr
{
String className = getClassName( testIdentifier );
String methodName = getMethodName( testIdentifier ).orElse( "" );
- return new PojoStackTraceWriter( className, methodName, throwable );
+ return new LegacyPojoStackTraceWriter( className, methodName,
throwable );
Review comment:
Yes to restore please. We should use the previous `PojoStackTraceWriter`.
The old `LegacyPojoStackTraceWriter` has bad user experience on the console.
Now it has only one purpose within plugin's process. Maybe it could be moved to
`surefire-common`. We will have a chance to break backwards compatibility in
3.0.0.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Auto-resolve "missing" JUnit 5 artifacts
> ----------------------------------------
>
> Key: SUREFIRE-1585
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1585
> Project: Maven Surefire
> Issue Type: Improvement
> Components: JUnit 5.x support
> Affects Versions: 2.22.1
> Reporter: Christian Stein
> Assignee: Christian Stein
> Priority: Minor
> Labels: features
>
> Providers should be able to enhance the test runtime by injecting "missing"
> artifacts before executing tests.
>
> For example, the JUnit Platform Provider should add "missing" Test Engine
> artifacts for when users only depend on the API of a test framework.
> * User test depends on *`junit-jupiter-api`* only? Provide
> *`junit-jupiter-engine`* at test runtime -- automatically or via plugin deps.
> * User test depends on *`junit-jupiter-params`* only? That pulls in
> *`junit-jupiter-api`* transitively. Provide *`junit-jupiter-engine`* at test
> runtime -- automatically or via plugin deps.
> * User test depends on *`junit:junit:4.12`* only *AND* the JUnit Platform
> Provider is forced? Provide *`junit-vintage-engine`* at test runtime --
> automatically or via plugin deps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
