Yeah, I can confirm setting up debugging (for Maven) in IntelliJ is so complicated...
The one thing I think they have right is having multiple configurations. I'd love the ability to save a configuration, either with a name, or hell even as simple as the host, and port number fields remembering previously used entries - Working on a system with multiple Spring boot services means each one of them has different debug ports, and remembering them is getting tougher the more we add... (off to search JIRA for an existing ticket, or to create a new one before I start work ;) ) Regards John On 23 April 2018 at 07:40, Laszlo Kishalmi <[email protected]> wrote: > Dear all, > > I just experimented some stuff for that yesterday using bintray API for > their repositories. I was able to retrieve a list of packages by > group/artifact ID-s and even query artifacts by package/class names, though > the later one might need to use the "I feel lucky!" heuristics, as I > searched for the new JUnit5 package and that gave me 14000+ matches and > returned the first 50. > > > > On 04/22/2018 11:28 PM, Christian Lenz wrote: > >> Hey Jaroslav, >> >> I think now it is the best time to do the Approach again under Apache 😊 >> >> >> Cheers >> >> Chris >> >> Von: Jaroslav Tulach >> Gesendet: Montag, 23. April 2018 08:14 >> An: Apache NetBeans >> Betreff: The IDE for DevOps was: IntelliJ IDEA vs Netbeans >> >> 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 >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
