I’ve created https://issues.apache.org/jira/browse/NETBEANS-6
Please comment there if you’re interested in JUnit 5 support for Netbeans. I am going to unsubscribe from this mailing list for now. Feel free to reach out to the JUnit team by creating an issue on GitHub: https://github.com/junit-team/junit5/ Thanks, Marc On 10. Jun 2017, 21:50 +0200, Geertjan Wielenga <[email protected]>, wrote: > https://issues.apache.org/jira/browse/NETBEANS > > File it under component "java - JUnit". > > Gj > > On Sat, Jun 10, 2017 at 9:42 PM, Marc Philipp <[email protected]> wrote: > > > Hi again, > > > > this mailing list has way too much traffic for me to stay on it. Can I > > create a ticket in Bugzilla or JIRA to continue the discussion instead? > > > > Thanks, > > Marc > > > > On 18. May 2017, 13:22 +0200, Geertjan Wielenga < > > [email protected]>, wrote: > > > Great discussion! Maybe this is one of the most promising threads on this > > > mailing list -- i.e., a representative from a technology pops up on the > > > Apache NetBeans mailing list to interact on a new integration of that > > > technology with NetBeans. > > > > > > Maybe we need to have a place on the Wiki where specs can be put > > together? > > > I.e., a long list of specs for higher-level features (as opposed to bug > > > fixes and so on)? There'd be an enhancement request in the bug tracker, > > > with a reference to a location on the Apache NetBeans Wiki where the > > > related spec for that enhancement would be found, e.g., a "support JUnit > > 5" > > > enhancement request, pointing to a Apache NetBeans Wiki page where the > > > JUnit team briefly lists the key features that they'd suggest the JUnit 5 > > > support in NetBeans should consist of, as a starting point for others in > > > Apache NetBeans to work out together further, prior to anyone > > implementing > > > anything? > > > > > > There'll be more of these kinds of mail threads starting up, > > increasingly, > > > especially by representatives of other Apache projects, and it would be > > > great to have a standard process, beyond simply saying 'file an > > enhancement > > > request please'. I.e., some kind of form on the Wiki would be filled in > > so > > > that right from the start we'd have formalized input for the requested > > > feature from the group requesting that feature. > > > > > > Gj > > > > > > On Wed, May 17, 2017 at 8:42 PM, Marc Philipp <[email protected] > > wrote: > > > > > > > Regarding the Gradle plugin: What we currently have works for basic use > > > > cases but we’d rather get official support into Gradle core. Please see > > > > https://github.com/gradle/gradle/issues/1037 for details. > > > > > > > > Thanks, > > > > Marc > > > > > > > > On 17. May 2017, 19:51 +0200, Attila Kelemen < > > [email protected]>, > > > > wrote: > > > > > Hi, > > > > > > > > > > I'm the developer of the Gradle integration of NB, so I can speak for > > > > that > > > > > part. > > > > > > > > > > For running tests, I just execute the appropriate Gradle task. If > > > > Gradle's > > > > > test task (`org.gradle.api.tasks.testing.Test`) were to support it > > > > (though > > > > > as far as I know it does not), it would work without change. If the > > > > task's > > > > > type is different, then I need some adjustments to configure it > > properly > > > > > when only running a particular test class (or method). The only > > possible > > > > > issue (which I don't know if it is an issue) is if NB recognizes the > > > > @Test > > > > > annotation or not (that is not within the scope of the build tool > > > > > integration). > > > > > > > > > > Anyway, if JUnit 5 uses a different task type, I would need the > > following > > > > > for proper support: > > > > > > > > > > - A property to configure the test class to be executed. > > > > > - A property to configure the method to be executed. > > > > > > > > > > It would be a nice bonus if it would work the same way (using the > > --tests > > > > > argument) as it does now but I could make it work even if the > > > > configuration > > > > > was different (it would be considerably more work for me but I would > > do > > > > it). > > > > > > > > > > bye, > > > > > Attila Kelemen > > > > > > > > > > > > > > > 2017-05-17 16:19 GMT+02:00 Marc Philipp <[email protected]>: > > > > > > > > > > > Hi all, > > > > > > > > > > > > I’m a member of the JUnit team. We’re currently working on a major > > new > > > > > > version: JUnit 5. It will require work by IDEs to support test > > > > execution > > > > > > and reporting within the IDE. IntelliJ IDEA and Eclipse (on a > > branch) > > > > > > already support the new JUnit Platform and the new Jupiter API to > > write > > > > > > tests. > > > > > > > > > > > > Are there any plans to add JUnit 5 support to Netbeans? If so, how > > can > > > > we > > > > > > help? > > > > > > > > > > > > Thanks, > > > > > > Marc > > > > > > > > > > > > > > > > > > > > > > > >
