Do we know how often this plugin is used? I've also been a happy IntelliJ user for years, but it might be worth posing the question on a few dev lists.
FWIW, Hadoop's BUILDING.txt still mentions eclipse:eclipse, but that's probably just stale. HBase's book also still mentions eclipse:eclipse, but also m2eclipse, so maybe eclipse:eclipse could be retired since there's an alternative. https://hbase.apache.org/book.html#_ides On Fri, Apr 14, 2017 at 3:02 PM, suraj acharya <[email protected]> wrote: > I will say lets remove it. Disabling it without a plan to remove it will > cause a lot of clutter. > On the other side, I use IntelliJ so I am not very well versed with the > plugins present in Eclipse. > > S > > -Suraj Acharya > > On Fri, Apr 14, 2017 at 3:30 PM, Allen Wittenauer < > [email protected]> > wrote: > > > > > Hey gang. > > > > I think it's been known for a while that the maven eclipse plugin > > that a lot of projects have been using has been EOLed for a while now. It > > looks like Eclipse's Neon release has that functionality now built-in via > > the Import Maven functionality. As that Eclipse release approaches a > year > > old, is it time to disable the mvn eclipse test by default? or even > remove > > it completely? > > > > It *does* cause problems; maven complains about it being a badly > > formatted plugin, etc, etc, which means we can't build a (more) useful > test > > that alerts on maven warnings/errors. > > > > Thoughts? > > > > > > > > >
