maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1585) Auto-resolve "missing" JUnit 5 artifacts
Date Sun, 25 Nov 2018 21:42:00 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698323#comment-16698323
] 

ASF GitHub Bot commented on SUREFIRE-1585:
------------------------------------------

Tibor17 commented on issue #196: [SUREFIRE-1585] Resolve missing and align "JUnit 5" artifacts
URL: https://github.com/apache/maven-surefire/pull/196#issuecomment-441476195
 
 
   Not sure what we would do with this in version 3.0.0-M2. I would appreciate to make frequent
releases. One way or another, thinking about mapping api and engines, maybe the api module
could somehow declare Maven coordinates of default engine (groupId:artifactId:version) in
some way. Maybe in a factory or `MANIFEST.MF`.

----------------------------------------------------------------
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:
users@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
>             Fix For: 3.0.0-M2
>
>
> 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)

Mime
View raw message