Tibor, If one is ranking correctness of integration with Maven of the various IDEs then IntelliJ is not the "gold standard".
There are two *major* bugs in how IntelliJ handles Maven projects: 1. It does not allow different Java versions for test versus main trees: https://youtrack.jetbrains.com/issue/IDEA-85478 2. It does not consult ArtifactHandler.isAddedToClasspath() and consequently generates incorrect classpaths: https://youtrack.jetbrains.com/issue/IDEA-175538 Both of these force users to contort their Maven projects in strange ways just to make them work in their IDE. >From my understanding, from the PoV of a Maven integration, the *gold standard* IDE is probably NetBeans, largely because it falls back to Maven to do the lifting. (Granted I do not use NetBeans, so I probably haven't found the bugs in its integration :-P) IIUC Eclipse could not have an issue like https://youtrack.jetbrains.com/issue/IDEA-175538 because m2e doesn't suffer from NIH syndrome when it comes to parsing the pom.xml files... however because of architectural history, Eclipse (last time I checked... some years ago) had issues keeping the main and test classpaths separate, which is worse than https://youtrack.jetbrains.com/issue/IDEA-85478 (And to defend IntelliJ, there may actually be some good reasons for their having NIH syndrome with respect to parsing the pom.xml files... but if you're going to have NIH syndrome you had better put in the work to make sure things actually work... and 2 years is a long time for https://youtrack.jetbrains.com/issue/IDEA-175538 to sit there without even a triage comment) Now I personally don't like NetBeans as an IDE, and I hate Eclipse as and IDE, so I continue to use IntelliJ despite its flaws... but I also recognise that these are personal preferences of mine. IDEs are subjective. Please try to remember what Clint Eastwood's character says about opinions in the film Dirty Harry. On Sat, 8 Jun 2019 at 16:01, Tibor Digana <tibordig...@apache.org> wrote: > No, it is not truth. And the price is nothing one cannot survive. IDEA is > also OSS. > User exp of IDEA is ideally joined together with Maven and working > naturally well. > Try Maven + IDEA and you will see. I used both. > > On Sat, Jun 8, 2019 at 4:51 PM Jeff MAURY <jeffma...@gmail.com> wrote: > > > <troll>because it's much better and oss</troll> > > > > Le sam. 8 juin 2019 à 10:29, Tibor Digana <tibordig...@apache.org> a > > écrit : > > > > > Why you use Eclipse. Use InteliJ IDEA. It is professional tool. Every > > > company has money to buy enterprise IDEA, the company wouln'd say no > > > because it is price you pay once and you can upgrade to major version > > > within whole year. You can use it forever without paying more after the > > > support period of one year you paid before. For instance I had IDEA 14 > > > since 2014 - 2019 without any issue in that tool. > > > > > > On Fri, Jun 7, 2019 at 3:32 PM Cristiano <cvgav...@gmail.com> wrote: > > > > > > > Hello, > > > > > > > > Yesterday I did an upgrade on some dependencies and plugins of my > > > > company's master POM. > > > > > > > > I used the versions-plugin and changed many of the suggested ones. > > After > > > > conclude and build on CI without error, I ended up with a strange > error > > > > in Eclipse IDE (ubuntu, 201903, jdk11) on every project that has it > as > > > > its parent POM. > > > > > > > > The error has no description and its title is "Unknown". > > > > > > > > > > > > It took some time to track the culprit down and after I have > downgraded > > > > the maven-jar-plugin to 3.1.1 the error was gone. > > > > > > > > I'm curious about this... > > > > > > > > best regards, > > > > > > > > > > > > Cristiano > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > > >
