Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use same default lifecycle for Kotlin and Java test classes #1002

Closed
1 task done
marcphilipp opened this issue Aug 4, 2017 · 1 comment
Closed
1 task done

Use same default lifecycle for Kotlin and Java test classes #1002

marcphilipp opened this issue Aug 4, 2017 · 1 comment
Assignees
@marcphilipp
Labels
component: Jupiter component: Kotlin theme: execution
Milestone
5.0 RC3

Comments

@marcphilipp
Copy link
Member

marcphilipp commented Aug 4, 2017 •
edited
Loading

Based on the discussion in #905 we've decided to revert #991.

Deliverables

  • Use same default Lifecycle for Kotlin and Java
@marcphilipp marcphilipp added this to the 5.0 RC3 milestone Aug 4, 2017
@marcphilipp marcphilipp self-assigned this Aug 4, 2017
@marcphilipp marcphilipp mentioned this issue Aug 4, 2017
Closed
9 tasks
@marcphilipp
Copy link
Member Author

in progress

@ghost ghost removed the status: in progress label Aug 4, 2017
sbrannen added a commit that referenced this issue Aug 4, 2017
@sbrannen
Move release note to correct section
440ce27 
Issue: #1002
Andrei94 pushed a commit to Andrei94/junit5 that referenced this issue Jun 23, 2018
@marcphilipp @Andrei94
Use same default lifecycle for Kotlin and Java test classes
366924a 
Fixes junit-team#1002.
Andrei94 pushed a commit to Andrei94/junit5 that referenced this issue Jun 23, 2018
@sbrannen @Andrei94
Move release note to correct section
fe28544 
Issue: junit-team#1002
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marcphilipp marcphilipp

Labels
component: Jupiter component: Kotlin theme: execution
Projects
None yet
Milestone
5.0 RC3
Development

No branches or pull requests
2 participants
@sbrannen @marcphilipp