![]() ![]() ![]() ![]() (Apr 12 '21) GradleDistributionManager can detect local Gradle Distributions Request project creation via Gradle init.Īction can be disabled for a configuration.Īdded API to reload Gradle project information. (Sep 23 '21) NetBeans Tooling plugin recognizes "runWorkingDir" and "runEnvironment" properties. (Feb 17 '22) GradleCommandLine Flag, Parameter, and Property implements GradleOptionItem interface (Apr 30 '22) GradleFiles can be obtained from API (Aug 12 '22) Allow to inspect dependency tree (Aug 20 '22) Rich exception reports are exported from Gradle process. (Oct 4 '22) Expose regular Lookup in NbGradleProject. (Oct 4 '22) New APIs that provide access to values of build properties and tasks. (Jan 13 '23) Adding JavaRuntimeManager abstracting the Gradle Runtime from Java Platform (Apr 4 '20) Move Gradle Tooling API to a separate module. (Jan 1 '21) Make ProjectActionMappingProvider available for other modules. Not all deprecations are listed here, assuming that the deprecatedĪPIs continue to essentially work. So it causes a bit of friction of not having a single source of ownership to various features of the IDE.This document lists changes made to the Gradle Project API.įuller descriptions of all changes can be found below (follow links). But now you can't submit a pull request to the "team", you have to go to someone else who may, or may not, deem the request worthwhile. I appreciate how the team doesn't necessarily want to be a domain expert in some specific aspect of the vast Java eco-system. You have NB maintained code designed to work with a specific maven archetype maintained by someone else. Many of those archetypes are NOT "owned" or maintained by the NB project, they're 3rd party. Many of the "New Project" wizards are simply wrappers around maven archetypes. If there's one real power feature to NetBeans is that it's a first class Maven IDE. My singular nit with the project is that they rely a bit on external projects. And, indeed, it doesn't have any formal sponsorship like it did under Oracle. The singular task of just "keeping up with Java" is load enough, much less adding on features. The transition to Apache has been tough, but it's honestly amazing how well it does. I'm a long time NB user, I still use it as my daily driver. IBM did that 20 years ago with Eclipse and it's a feature I miss a lot. There are not many IDEs out there for any language that can do that. It could even tolerate compilation errors and still allow you to run parts of your code. The reason for this was a deeply integrated incremental compiler. Fix the problem, the red goes away immediately. Introduce a problem, the project goes red immidiately. error state of your project would update in real time while you were typing. And with the round trip via Gradle, it just is guaranteed to take multiple seconds to process even a 1 character change in a unit test when you run one.Įclipse used to be awesome for this with Java: I love Kotlin but compiler speed is not one of its strengths. I still miss incremental compilation speeds for Java that were in the order of milliseconds rather than the 5-10 seconds (minimum, if you are lucky). I've only had to go back to it to fix a JavaFX app we got landed with, and I can't say I was too impressed at how well it integrated with maven, having to ditch out and use the command line to get proper bundled builds to work.Įxcept performance. Now I used Netbeans for years, but only because I was exposed to it in the university computer labs. VSCode, immediately shows that it's USP, it's extensions ecosystem, in the screenshot on the landing page and then covers some other minor USPs in brief segments.Įven Sublime Text, updated once every blue moon when Mars is in retrograde, understands that showing off USPs and the developer experience is key. Testimonies, and new features are listed on that page. IntelliJ has me scroll down the page, but I then get a breakdown of what USPs IntelliJ thinks I a developer would be interested to know about, like it's refactoring and code completion, that it has specific integrations for frameworks. > It highlights source code syntactically and semantically, lets you easily refactor code, with a range of handy and powerful tools. All those call to actions are the bare minimum I'd expect of an IDE, nothing gives a unique selling point. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |