Technically NetBeans is both an RCP, first technically, and an IDE, so it is a library, and an application, but no, there is no separate TCK. All the tests are in the build infrastructure you get when you clone the repository. There are some infrastructure things which the community uses to validate release, through community programs/processes such as NetCat, but those are not running tests. They are more for community sign off and manual regression testing; formalized crowd sourced testing.
Wade On Sep 14, 2016 7:41 PM, "Greg Stein" <gst...@gmail.com> wrote: > On Wed, Sep 14, 2016 at 4:14 PM, Shane Curcuru <a...@shanecurcuru.org> > wrote: > >... > > > >> I think the question is more along the lines of what else would be > > >> required to produce a "canonical" > > >> release of Apache Netbeans. If everything that is required is being > > >> donated -- I think we're good. > > > > Indeed - and remember, I'm not a regular NetBeans user. But when I > > google "NetBeans", I see lots of links of bundled JDK downloads and > > various plugins that do all sorts of cool Java stuff. My question is: > > does producing a fully working core NetBeans require running any TCKs? > > > > It's just an application. Not a library. No TCKs involved. >
