NetBeans 3.3 Editions & Modules

1. Editions

   Do you like our current distribution or would you prefer to have more editions?

44/45 (97.77%)

- Empty Edition - contains only OpenIDE, Core and Autoupdate module. This edition is suitable for developers using NetBeans as a Tools Platform



44/45 (97.77%)

- Standard Edition - contains most important modules for Java development - something like current NetBeans build.



21/45 (46.66%)

- NetBeans Developer Edition - similar to Standard Edition, but preconfigured for developers of NetBeans modules.



23/45 (51.11%)

- Full Edition - contains all stable modules available on NetBeans website.
  • Should modules which are not in Standard Edition be 11/23 (47.82%) enabled 12/23 (52.17%) disabled
  • 2. Modules

    There are some modules, which became stable and are not in distribution. On the other side, some modules could be removed from NetBeans distribution and become only available on Autoupdate server. Please vote:

    Module Name Description Current Status
    Standard Edition
    Autoupdate Only (and "Full Edition" if it will be accepted)
    Development-time support for the Open APIs. Using this module you can develop extensions to the NetBeans IDE within itself. Includes a complete copy of the API documentation for offline browsing and Javadoc index searching. Has templates for many differents parts of the APIs, code completion, facilities for testing modules and individual objects, and more.
    Stable with NB3.2, available at Autoupdate. It could make startup longer. Big module (~3MB)



    cpplite Lightweight support for development C/C++ applications. Stable with NB3.2, available at Autoupdate



    innertesters Support for unit-testing classes using static inner test classes. Stable with NB3.2, available at Autoupdate



    jasm View/edit bytecode. Beta, works with NB3.2



    junit Support for unit and integration testing with the JUnit framework. Beta, available at Autoupdate



    logger Trace logger that allows logging of messages to multiple output streams, and a UI for changing logger flags. Beta, available at Autoupdate



    objectbrowser Object Browser presents an alternate view of Java classes (as compared to the Explorer, which comes as part of the IDE's core) The Object Browser is a three-pane window, with different panes for packages, classes, and members, each of which can be filtered. Currently part of build. There was already discussion about removing this module from build (see nbdev archive)



    serialversion A wizard to scan source code for serial version UIDs and prompt to fill them in where they are missing. Also helps manage serialization-related Javadoc fields. Beta, available at Autoupdate



    sysprops Displays system properties set in the Java VM, and lets them be modified as well. Stable with NB3.2, available at Autoupdate



    workspaceswitcher Graphically represents workspaces and the windows on them as a double-height toolbar presenter, and allows windows to be dragged between workspaces.
    Nearly stable with NB3.2



    This module adds basic support for C, C++ and Fortran development: syntax highlighting, indentation engines, recognition of source files, derived files (.o etc.) and executable files. Makefiles are also supported, and native binaries can be executed. Some basic templates are also provided. For more information and download see Tor Norbye's e-mail to nbdev. Just contributed to NetBeans OpenSource (Aug/17)



    external editor support (Vim, XEmacs)
    This module lets you use an external editor with NetBeans, in particular, Vim and XEmacs. For more information and download see Tor Norbye's e-mail to nbdev. Just contributed to NetBeans OpenSource (Aug/17)



    Yours commets:

    I suggest two other editions: 1. Distributed - RMI, JINI, CORBA, EJB, etc. might not be part of the "standard" but of this special one 2. "Web development" (JSPServlets) - special edition for people working on those - again the appropriate modules might not be part of standard edition. And on the contrary this web edition might consider not to contain Form Editor... Maybe this is too many editions but ... David

    I see as very important APISupport module. Of course it is necessary only for specific group of users, but it seems to me that a lot of users might not notice that there exist something like that, what might help them to understand OpenAPIs. With editions I would only afraid that it will be more confusing for new users. Right now they must learn which version they want - 3.2, qbuild, dev-version. And now they will also have to choose from editions. The Empty edition is great idea, but I would name it "Pure Core Edition" or something like that, because "empty" has some negative sound ;-)
    objectbrowser: Depends on how the new freestyle browser looks like. If it is much better than the current one, it should be in the standard edition too. empty edition: Not sure how useful this version is. Developers who want to use NetBeans as a Tools platform have to "tweak" it anyway to suit their needs. I think it is much more important that we provide information about how to do this. Some tutorial maybe?
    1. The empty edition should have longer release cycle and different procedures (stronger focus on quality, performance and clean APIs and architecture are more important then features). So it should be more separated from other editions. The other editions can be developed, tested and release synchronously and just divided into 2 or 3 zip files at the release time (possible for beta builds and Q-builds(?)). It would be overkill to create 3-4 builds every day and expect qa and developers to test them. 2. Releasing modules for the autoupdate server should be managed by the module owners, out of the scope of the release cycle. It would be more lightweight process which can scale for large number of modules much more easilly then synchronous releases.
    Ideal for me distribution may be the current _minus_ these modules: -Image -Recource Bundles -Tools Debugger -New Module Wizard -JNDI -RMI -JSP Syntax Coloring -Recource Bundle Syntax Coloring -JsEE Support -Ant (Apache, sorry ;-) -Internationalization -Internationalization Form Cross Dependency -JAR PAckager -Object Browser -Scripting Supposr -CVS Built-in Client -CVS Command-Line Support -VCS Generic Command-Line Support -Applet -External HTML Browser -HTTP Server -JSPServlet -Tomcat 3.2 Server -VCS Core These modules may be available via autoupdating. And, I think, JDK ParserDB files may be "minused" too. Andrew
    Instead of "different" Editiondistributions, why not make the IDE "mode" aware. If you can download "Modules", why not add the same sort of idea, only a super set of "Modules". (Call that a mode.) IDE Mode 0: (IDE) - Empty Edition - Modules abc def IDE Mode 1: (Java1) - Standard Edition - Modules abc def jik etc... This way you can also alow other to contribute "mode" definitions. Say for tuning for specific languages, setups etc... If you really get fancy and allow multiple modes to be selected at a time you could do some very cool things. but then a mode might also try to require a different mode. Well it could be done.. but you would need to watch for loops. :) Lock the "netbeans" defined modes so that users can add modules but not remove them. And allow users to add new "modes" at will. To me this is "Editor pref." type stuff. Not project specific, higher level than projects. Just a t! hought.
    1) A long time ago there was a discussion of discoverability of modules (i.e. advertising new or disabled modules). If such a system were in place, I would vote for disabling more modules by default as long as I could be notified of what functionality was available without going exploring. 2) I think the second table above should have a radio button for developer edition which I would have chosen instead of full edition in several of the cases. 3) I voted to put external editor in the standard edition, but that's provided it's stable.
    I'd prefer the "Platform" edition name to the "Empty".
    There is an argument that all modules should be available in the download and the update centre should be used for *updates*. After all, most people wouldn't be too bothered about having another couple of MB to download. I suppose the real issue is startup time if all these modules are enabled. I imagine a lot of people ignore the current wizard page allowing you to enabledisable modules after installation. A radical solution would be to have every module *disabled* by default forcing people to go through and enable the ones they want. But maybe not so good for novices.
    API Support module should be part of NetBeans Developer Edition. Maybe it could be useful to add a Laptop Edition, which would contain the same modules as the Standard Edition, but most of the modules should be disabled by default (at least the following modules should be disabled: Image, Resource Bundles, Text, Tools Debugger, New Module Wizard, JNDI, RMI, JSP Syntax Coloring, Resource Bundle Syntax Coloring, General Online Help, Auto Update, J2EE Server Registry, Bean Patterns, Ant, Internationalization, Internationalization Form Cross Dependency, JAR Packager, Object Browser, Scripting Support, CVS Built-in Client, CVS Command-Line Client Support, VCS Generic Command-Line Support, Applet, External HTML Browser, HTML, HTTP Server, JSPServlet, Tomcat 3.2 Server, VCS Core and maybe also Form Editor and Debugger) and the workspace would be better configured to make explorer and editor windows as big as possible (e! .g. by removing toolbars, workspaces, reducing width of main window so it would not be wider than explorer window - editor window can be then placed on the top of the screen next to the main window and explorer)
    An Editor Edition will be super: concatenation of empty Edition + Editor module, Java module, HTML module, XML module, And CVS module. Why? Because that edition can be used for user that want edit some text files JAva files, HTML Files or Bundles.Properties files and also have access to CVS. That Editor version of NetBeans will be the perfect companion to user that are interested in Open Source Projets that are on the Net and use CVS Repository for their source code.

    Not logged in. Log in, Register

    By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2016, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo