Hi Jaroslav, You have my full support for this. Getting rid of Maven indexer and searching on the fly is exactly what I'd like to do too - in fact I always set indexing to "never" and run manually from time to time because the indexer freezes the IDE.
A partial workaround would be to add pauses during unpacking and indexing artifacts to avoid freezing the IDE. But still, it doesn't make sense to index whole maven repo and store a couple of GB on disk. I run Netbeans under 2 different user accounts and I had to point Netbeasn to the same directory to store the index to save a couple of GB by a redundant index. Ondro 2018-04-23 8:14 GMT+02:00 Jaroslav Tulach <[email protected]>: > > I just spent the past 2 weeks using IntelliJ IDEA exclusively (having > used > > it sporatically before). I'm going to share some brief thoughts in the > > hopes that it helps. > > > > As far as I can tell, IntelliJ's killer feature is their debugger (more > > broadly, their UI). Our killer feature is our profiler, and Maven > > integration (more broadly, bundling more functionality standard). > > > > * Netbeans drives development of Maven projects through Maven. This > > results in better integration than IntelliJ provides (e.g. good luck > > trying to start a debugging session through Maven) > > > > Yeah, I can confirm setting up debugging (for Maven) in IntelliJ is so > complicated... > > Once I called NetBeans the [IDE for devops and admins]( > http://wiki.apidesign.org/wiki/DevOps) and this is what I meant. If you > care about your overall project structure, there shall be benefits of using > NetBeans+Maven. If you just care about the code, the IntelliJ's editor > focus may give you better experience. > > Moreover the NetBeans approach is more fragile. Structures of pom.xml files > differ wildly and when they get out of expectations, things may get broken > or slow... > > > indexing and performance levels can be done with the > > code currently in Apache NetBeans Git. Jaroslav Tulach will have insights > > as well as gratitude for help in this area > > My thought is simple: there should be no Maven index processing on the > client (by default). There should be a webservice the IDE would query > instead. However my idea was rejected by last Oracle NetBeans performance > team last time I proposed it. It was found too complicated. Anybody wants > to pick that challenge up now? > > -jt >
