maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Stein (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SUREFIRE-1585) Auto-resolve "missing" JUnit 5 artifacts
Date Wed, 07 Nov 2018 07:41:00 GMT

     [ https://issues.apache.org/jira/browse/SUREFIRE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christian Stein updated SUREFIRE-1585:
--------------------------------------
    Summary: Auto-resolve "missing" JUnit 5 artifacts  (was: Auto-resolve "missing" artifacts)

> 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)

Mime
View raw message