FYI: the JUnit team is working on relicensing their provider code under AL 2.0 so there should not be a problem for us to accept their contribution.
https://github.com/junit-team/junit5/issues/541 BR, Benedikt Benedikt Ritter <brit...@apache.org> schrieb am Di. 4. Okt. 2016 um 19:41: > Hello Tibor, > > Tibor Digana <tibordig...@apache.org> schrieb am Di., 4. Okt. 2016 um > 02:14 Uhr: > > +1 to adopt JUnit 5 provider to Maven Surefire git branch. > You would have to extend AbstractSurefireMojo.java with JUnit 5 provider in > classpath builder. > > > I see, we would have to implement a ProviderInfo for JUnit 5. I think I > can work on thins. > > > Do we have to keep using other license? > > > JUnit is EPL. I talked to Marc and they asked all contributors to > explicitly state that they are donating the code under the terms of EPL. > I'm not sure how we would handle it. If they explicitly contribute the > code, it should be no problem. Or do we have to talk to legal? > > > Can we ask the JUnit team to continuously migrate stable changes to > Surefire? > > > I think there should be only one home for the provider. Either it is > maven-surefire or it's junit but not both. So if we decide to take over the > provider they will probably stop maintaining their own implementation > because it is not their scope. I've volunteered to help maintaining the > code since I'd like to get involved in the maven project and in junit. If > that's not enough, we have to find a different solution. > > Regards, > Benedikt > > > > > On Mon, Oct 3, 2016 at 7:39 PM, Benedikt Ritter [via Maven] < > ml-node+s40175n5882104...@n5.nabble.com> wrote: > > > Hi, > > > > now that we have a separate branch for the JUnit 5 support in the > surefire > > repo, I'm asking myself how to much things forward. I've added some > > additional IT implementations in my GitHub fork, but they all fail > because > > the 5.0.0-M2 release of junit-surefire-provider does not implement the > > desired features. > > > > At this point I'm pretty much blocked: I can not pick up the latest > > changes > > to the JUnit 5 provider, because the JUnit team has not released it. The > > JUnit team does not push the development of the provider further, since > > they don't have integration tests... > > Right now I think it would be best to start implementing a JUnit 5 > > provider > > ourself in the junit5 branch, so we can add the missing features and have > > it ready when JUnit 5 reaches GA. > > > > Thoughts? > > > > Benedikt > > > > > > ------------------------------ > > If you reply to this email, your message will be added to the discussion > > below: > > http://maven.40175.n5.nabble.com/SUREFIRE-JUnit-5-support- > > how-to-move-things-forward-tp5882104.html > > To start a new topic under Maven Developers, email > > ml-node+s40175n142166...@n5.nabble.com > > To unsubscribe from Maven Developers, click here > > < > http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=142166&code=dGlib3JkaWdhbmFAYXBhY2hlLm9yZ3wxNDIxNjZ8LTI4OTQ5MjEwMg== > > > > . > > NAML > > < > http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Re-SUREFIRE-JUnit-5-support-how-to-move-things-forward-tp5882138.html > Sent from the Maven Developers mailing list archive at Nabble.com. > >
