Apache NetBeans (Incubating)

Friday July 20, 2018

What's Happened to My Favorite NetBeans Plugins?

So, you start up Apache NetBeans (incubating) 9.0 and... you find that when you go to the New Project wizard, or when you try to open your projects, that there's no support for your JavaScript, PHP, Groovy, enterprise Java (i.e., Java EE or, as it is known now, Jakarta EE), and C/C++ projects.

What's the reason for that and what can be done?

Well, Apache NetBeans (incubating) 9.0 is specifically focused on Java SE only. Why? Because NetBeans is extremely large (it will be by far the largest project in Apache, once everything has been donated), which is because it has existed for over 20 years and provides support for a very wide range of technologies. Since so many files all needed to be audited before they could be donated to Apache, the decision was made to donate NetBeans in pieces, i.e., not everything at the same time because that would have taken much too long.

And since NetBeans is modular, doing an incremental donation was not difficult to architect. The first donation focused specifically on the underlying core, i.e., the NetBeans Platform (e.g., the module system, window system, menubar, etc etc) and, to enable the result of the first donation to be usable for general users and not just NetBeans Platform developers, the various Java SE features were included too, e.g., Java project templates, Java editor, and new Java features such as support for Jigsaw, JLink, and JShell.

The above is what Apache NetBeans (incubating) 9.0 consists of. In the meantime, the second donation has been completed, i.e., Oracle has audited and donated all the modules for features providing support for JavaScript, PHP, Groovy, and enterprise Java (i.e., Java EE or, as it is known now, Jakarta EE). These features are on a separate branch in the Apache NetBeans Git repo. They will be integrated, i.e., relicensed to Apache, after Apache NetBeans (incubating) 9.0 is released. After that, the next set of modules that is being audited prior to donation are related to C/C++.

So, does that mean that all the features that are not integrated into Apache NetBeans (incubating) 9.0 cannot be used? No, it does not. Go to Tools | Plugins in Apache NetBeans (incubating) 9.0 and, in the Settings tab, register the NetBeans IDE 8.2 update center:

http://updates.netbeans.org/netbeans/updates/8.2/uc/final/distribution/catalog.xml.gz

Then go to the Available Plugins tab and you'll see all the plugins for NetBeans IDE 8.2., and search for the word "Kit", which will give you bundles of modules, for higher-level features such as C/C++, JavaScript, Groovy, PHP, and enterprise Java (i.e., Java EE or, as it is known now, Jakarta EE).

Though note that none of these features have been tested with Apache NetBeans (incubating) 9.0, they should work, in most cases. If not, don't panic. Just sign up to the Apache NetBeans mailing lists, as explained at netbeans.apache.org, and start a new thread where you'll highlight some problem you've encountered, after which someone will help you or you'll be advised to create a new issue in Apache NetBeans Issuezilla.

Where is all this documented, how can anyone know what will be donated in which order, etc? Easy, go here, to the end of this page:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition

Comments:

First of all, my kudos to all the volunteers who have accepted the work and responsibility of maintaining a beast that a big corporation is not willing to. You really have my appreciation. Secondly, my two cents and a question. I briefly tried 9.0 when it was out. I successfully got rid of Java stuff (whether it was a good idea is something I'm not qualified to assert) and installed PHP plugins (most of them anyway). Subversion does not work at all. Also, it uses "%APPDATA%\NetBeans\dev" as profile location and broke my 201804200002 set-up so I'm glad I had backup copies. Am I right if I assume that actual bugfixing is not really feasible until second donation completes?

Posted by Álvaro González on July 23, 2018 at 08:24 AM UTC #

“when it was out”? Apache NetBeans has not been released yet. And don’t report issues in blogs please. Use the mailing list or issuezilla.

Posted by Geertjan Wielenga on July 23, 2018 at 08:31 AM UTC #

@Geertjan Wielenga My excuses, I omitted the "Incubating" and "RC1" bit because I thought it was evident given the context. It also wasn't my intention to report bugs, sorry if I gave that impression.

Posted by Álvaro González on July 23, 2018 at 10:55 AM UTC #

Sorry, if you’re not willing to report bugs for problems that you find, then I’m not going to spend time trying to help you. Do note that rc1 is several months old though. We’re very close to the final release, are no longer working with rc1 at all. However, the place for this doscussion is the mailing lists and issue tracker. So, hope to see you there, that’s where all the discussions take place.

Posted by Geertjan Wielenga on July 23, 2018 at 11:15 AM UTC #

Then simply do not release it as 9.0. But as a RC, Alpha, Beta, whatever. We are during a period that most of open-source IDEs (eclipse, netbeans) have fallen behind commercial competition (that is Jetbrains). Do yourselves a favor and think about business-wise. Hold up the release of the product until it is ready and in a good state. Or else the last few of us that insist on using open-source products will also jump ship, just my 2 cents ...

Posted by Anonymous Coward on July 24, 2018 at 09:12 AM UTC #

You can trust that that approach has been considered and, in fact, why not join in via the mailing lists at netbeans.apache.org. The Beta and RC have already been released, FYI. The product is in a ready and good state right now for Java developers and we'll continue to work on the other pieces for other developers as well, while these developers can install those features via plugins. Join in with the discussions on the mailing lists, we look forward to hearing from you there.

Posted by Geertjan Wielenga on July 24, 2018 at 09:20 AM UTC #

First, Kudo's to the Apache crew and thanks for all of your effort. Secondly, please ignore what appears to be Trolling from JetBrains Fanboys, as unlike some, us long term users of Netbeans enjoy the Open Source alternatives that are available. Now, while Eclipse, Netbeans or even Jetbrains and "others" may have interesting features, one size does not fit all and never has. As for the idea that any Open source product "lacks features" because it isn't a copy of a "Commercial Product", that just beggars belief. Many of us are quite happy with what we have and don't really need features we don't use and/or don't find useful. For those that do, it's called modular design, there's probably a plugin for that. Also, many of us appreciate what the Apache Foundation has done and continues to do. As for Netbeans, the last stable version, 8.2 is still available from Netbeans.org and still works as intended. This is not to say that Apache won't improve things, given that I was one of the those who appreciated Apache 1.3 when first released. Just look where we are today. All thanks to the Apache Foundation. Also, I can't help but notice that not only is the sky not falling but that given the previous Track record of the Apache Foundation, eventually, Netbeans will hopefully become the third force in cross platform Developer tools. Love your work folks, keep it up.

Posted by John Harris on July 28, 2018 at 08:31 AM UTC #

As long as Java Enterprise isn't integrated in NB 9 I'll stay with NB 8.2. NB 8.2 works fine so I don't need to do experiments with an unfinished release.

Posted by Hugo on July 30, 2018 at 08:57 AM UTC #

You could consider helping make NetBeans better by experimenting with the newest release. NetBeans is no longer simply here for you to use, in one way or another please consider what you can do to make it even better than it is. You are needed, not simply as someone who waits to use, but as an actual participant in the process.

Posted by Geertjan Wielenga on July 30, 2018 at 09:29 AM UTC #

Congratulations on the first release! I love Netbeans. I really hope the community gets behind this project now that it is part of ASF. One quick tip for people; most developers will want to set the -J-Xmx java option in etc/netbeans.conf because the option is not being set in this version so jvm default is used and 1GB which isn't enough to compile a lot of projects.

Posted by Benjamin P Erridge on August 03, 2018 at 09:01 PM UTC #

After installing the J2EE plugins, you can get back the imported servers by copying ~/.netbeans/8.2/config/J2EE/InstalledServers to ~/.netbeans/9.0/config/J2EE/InstalledServers

Posted by Hrotkó Gábor on August 09, 2018 at 07:09 AM UTC #

The url with final/distribution is a curated list or something like that? Some plugins that I use (Darcula LAF is the most popular), didn't appear. But after adding the "normal" url, were available again. May be useful to someone: http://plugins.netbeans.org/nbpluginportal/updates/8.2/catalog.xml.gz

Posted by Guillermo Gomez on August 14, 2018 at 09:41 PM UTC #

If you need PHP 7.1 support, you can add the Latest Development Build catalog url, and update the plugins: http://bits.netbeans.org/dev/nbms-and-javadoc/lastSuccessfulBuild/artifact/nbbuild/nbms/updates.xml.gz

Posted by Tamas Molnar on August 16, 2018 at 09:50 AM UTC #

I think the problem for me is that none of my servers got transferred in the upgrade ( I have some legacy Glassfish installations)

Posted by Paul . on August 16, 2018 at 02:03 PM UTC #

Apache NetBeans (incubating) 9.0 is focused on Java SE only. Not Java EE, which is focused on Java servers, such as GlassFish. For that reason, install the plugins, as described above in this blog entry.

Posted by Geertjan Wielenga on August 16, 2018 at 02:40 PM UTC #

I have installed the plug-ins, but when i start the program a warning come out: Warning - could not install some modules: JavaScript2 Kit - The module named org.netbeans.modules.javascript2.requirejs was needed and not found... ... 18 further modules could not be installed due to the above problems. If i click on "Exit" or "Disable modules and continue" the program crash and it doesn't open.

Posted by Gabriel on September 18, 2018 at 12:43 PM UTC #

what about Subversion?

Posted by Subversion on September 18, 2018 at 02:43 PM UTC #

Anyone running into problems, please see netbeans.apache.org and join the mailing lists described there and ask questions there.

Posted by Geertjan Wielenga on September 18, 2018 at 03:43 PM UTC #

As long as NB 9.0 does not have enough plugins available in the older versions, I will not use V 9.0. Required are PHP, Javascript / Typescript and Python plugins. It is also overdue to discontinue Swing and AWT and only support JavaFX etx. Furthermore the JavaFX Scene GUI Builder has to be integrated into NB. NB has to get much better. There is still a lot of work to do. NB is not a competitor to Visual Studio.

Posted by TR on October 18, 2018 at 01:43 PM UTC #

Those are great ideas and this is where you can provide your pull requests to fix/add what you need: https://github.com/apache/incubator-netbeans/pulls

Posted by Geertjan Wielenga on October 18, 2018 at 01:46 PM UTC #

Big thanks to all the huge effort by the Apache team to get Netbeans 9.0 released. I have installed the Netbeans 8.2 plugin repos have been successfully working on Javascript and PHP web projects with Netbeans 9.0 without any issues.

Posted by James Wadsworth on October 24, 2018 at 07:09 PM UTC #

Fantastic stuff! Very disillusioned by IntellIiJ after being very disillusioned by Netbeans >4.0 - both engineering efforts were scuppered by feature greed. It's great that there is a focus on SE - many of us would very much appreciate a sharp, smart, hard, stable IDE. Cheers.

Posted by Al on October 25, 2018 at 09:16 PM UTC #

Apache Netbeans works on my whole codestack except for critical sections that depend on Swing. I cannot deprecate them without Swing, so this omission stops development cold for me. My workaround plan is to stay with 8.2, and explore IntelliJ, even though I greatly prefer Netbeans. It has been a great run. Thanks to all who made it possible.

Posted by L. Van Warren on October 30, 2018 at 04:43 AM UTC #

No clue at all what you're talking about, no reference to any issues, so, nothing we can do. Good luck with IntelliJ, I guess. :-)

Posted by Geertjan Wielenga on October 30, 2018 at 06:15 AM UTC #

I do major JavaEE development on NB 8.1 and I found it on first read a bit confusing that NB 9 has focus on SE (not EE/ME). Then next I bumped into a NB 8.2 repository note and thought that this sounds like a backwards-compatibility? Sorry for my weak English (German-native speaker/reader here) but this is a bit confusing what is written here. Do we have "official" (not in basic NB platform, of course) EE/ME support one day or are we doomed with 8.2 (which is getting out-dated and maybe with later updates even incompatible (no longer working, major bummer)? Or can Apache incubate the EE/ME plugins as well? Sure you don't want to miss these developers (and let them stay behind with NB 8.1/8.2) ...

Posted by Roland Häder on November 09, 2018 at 11:06 AM UTC #

Can you read this blog entry a few more times, maybe translate it to your language in Google Translate?

Posted by Geertjan Wielenga on November 09, 2018 at 11:40 AM UTC #

Post a Comment:
  • HTML Syntax: NOT allowed

Calendar

Search

Hot Blogs (today's hits)

Tag Cloud

Categories

Feeds

Links

Navigation