3 ms·
Still using a old version of NetBeans to develop a Java EE 7 application. I would switch to IntelliJ if possible, but honestly, unlike .NET - Java IDE and the t
by sebazzz 2y ago
Still using a old version of NetBeans to develop a Java EE 7 application. I would switch to IntelliJ if possible, but honestly, unlike .NET - Java IDE and the toolchain are so much tied together (it is not just a bunch of MSBuild) files, chaining the IDE for a project that old and on life support anyway is a journey not worth it.
- jcon321 2y agoI've brought my company's JavaEE 7 web application through NetBeans' upgrade life cycle, starting at NetBeans 8 I think. 10 or so years ago. NetBeans was great, when I first started, around version 8 or 9 - almost every "EE" feature worked. The years during transition to Jakarta were rough, most EE features lost. However during this time I've learned a lot more about java as IDE "magic" was mostly gone. (Converting ant to gradle, better understanding of dependency management, jaxws wsdl generation, better understanding of the deployment and application container, probably more...) I'll probably upgrade to 25 soon. Now-a-days there's never any problems when I upgrade, I guess because I'm no longer reliant on any IDE feature. At this point NetBeans is just a text editor with remote debugging capability. I enjoy it.