Hi, Can you elaborate why you need the codes in 5.4.0? Maybe we can find a way to work it around. If not, I think option 1 and option 2 looks both ok to me. If I have to choose, I choose option 1 because this is a test dependency, it should not have too much impact to the code quality. If choose option 2 and have to wait 2 month, maybe there will be lots of refactoring work like resolving conflicts.
On Thu, Jan 10, 2019 at 4:09 PM Xin Wang <[email protected]> wrote: > > If so , I think there are two methds: > 1. Use jupiter version5.4.0-M1 [1]: but it is a milestone version, not a > release version > 2. Use jupiter version5.4.0: the release date is uncertain （maybe need > two monthes） > > [1] https://github.com/junit-team/junit5/releases/tag/r5.4.0-M1 > > Justin Mclean <[email protected]> 于2019年1月10日周四 下午3:50写道： > > > Hi, > > > > > I have a question :I ues junit-jupiter5.3.2, but for some test cases, I > > > copied some source code from junit 5.4.0.M1 , the files are as follow : > > > org.junit.jupiter.api.support.io.TempDirectory.java > > > > > > > > org.junit.jupiter.api.MethodDescriptororg.junit.jupiter.api.TestMethodOrderorg.junit.jupiter.api.Orderorg.junit.jupiter.api.MethodOrdererorg.junit.jupiter.api.MethodOrdererContextorg.junit.jupiter.api.MethodDescriptor > > > > > > the license is Eclipse Public License - v 2.0 > > > Do I need to mark it in the LICENSE file? > > > > Sorry EPL is considered "Category B” [1] and isn’t fully compatible with > > ALv2 can’t be included in a source release. Is there another way of doing > > this? > > > > if it was the connivance binary then yes you would need to put it in the > > LICENSE. > > > > Thanks, > > Justin > > > > 1. https://www.apache.org/legal/resolved.html#category-b -- Best Regards！ Huxing
