Hi Martin, Thanks for your feedback. Good to know you’re still using NetBeans. By “Eclipse’s dependency tree tool” what do you mean? Something like [1] or like [2]?
Should we move these kind of emails to the user list? Thanks, Antonio [1] https://books.sonatype.com/m2eclipse-book/reference/figs/web/eclipse_pom-editor-graph-radial.png [2] https://books.sonatype.com/m2eclipse-book/reference/figs/web/eclipse_pom-editor-depend-tree.png > El 13 oct 2017, a las 22:10, Martin Dindoffer <mdindof...@gmail.com> escribió: > > Maven, just like everything else, lacks some of the refinements that can be > found in other IDEs. > > For example, you can't "ctrl+click" through the remote parent references in > the poms. > And that's a pita in large projects where parents are often only in some > remote repos. > > Also, what if you generate sources with a maven plugin into a folder > different from "/target/generated-sources/" ? > As always - other IDEs handle it with no problems, but Netbeans does not > recognize them and you can't do nothing about it. > There was an issue for this way back then. It was closed as won't fix IIRC. > > Also, take a look at Eclipse's dependency tree tool. Compared to that > Netbeans has only the "graph" that > > 1. looks outdated, > 2. has visual glitches on newer systems > 3. quickly becomes a slow mess in large projects > 4. does not show you the actual tree hierarchy (unbelievably useful, again > in big projects with many parents) > > Martin > > 2017-10-13 19:03 GMT+02:00 Ciprian Ciubotariu <cheepe...@gmx.net>: > >> The netbeans-maven integration is waaa...aay better than what I found in >> eclipse and intellij. Maven projects are basically native netbeans >> projects - >> no extra files necessary. Unless you want to do something in your IDE that >> you >> don't want to write in pom.xml, I guess... >> >> On Friday, 13 October 2017 13:41:34 EEST Martin Dindoffer wrote: >>>> What are those small things? Providing a list of those small things, >> for >>>> others to implement, is precisely the very significant role that you >> can >>>> play in this project. >>> >>> Hi there, fellow Java developer here. >>> The thing is, as others have pointed out, Netbeans is quite behind other >>> major IDEs and the list of the small things would be really huge. >>> Also, you already have a list. A bug list. And a big one. Do you think >>> those hundreds of bugs are not relevant anymore because they are old? >>> Absolutely not. >>> If you'd like to know about some specific issues I'm dealing with: >>> * Maven integration is bad. Compared to competition it is slow, the >>> periodic indexing is painful. The dependency graph generator is unusable >> on >>> large projects. >>> * JavaFX support is almost non-existent. >>> * The Java refactorings lack many of the features intellij has. >>> * Some lesser known languages do not have any plugin/support. (Yang >> anyone?) >>> * When an external changes happen to a larger codebase, NB takes up to a >>> minute or two to cope with it and reopen everything or whatever it does. >> * >>> Those little mising features everyone speaks about are everywhere from >>> lacking colors in maven terminal output to javadoc popups not parsing >> html. >>> >>> I use Netbeans at work for regular development. The amount of exceptions >> I >>> receive from the IDE varies from 3 - 12 every day. >>> There's a plethora of visual glitches and errors. Sometimes it even likes >>> to crash. >>> Is the exception reporter tool still being used by the devs? Or should >>> everything be reported via a ticket manually. >>> >>>> Instead, start a new mail thread with a specific missing feature, >>> >>> something >>> >>>> small -- and let's discuss that feature via a mail thread, first. >> Then, at >>>> some point in the discussion, someone will say, let's create an issue >>>> around this feature, now that we've discussed it, and someone else will >>>> say, hey I think I know how to fix that, let me try and then I'll send >> a >>>> pull request for others to review. >>> >>> I really do not think a mail thread for each little change is a good >> idea. >>> Just because of the sheer amount of bugs and features. >>> >>> Martin >> >> >>
