You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yetus.apache.org by Allen Wittenauer <aw...@effectivemachines.com> on 2017/04/14 20:30:58 UTC
[DISCUSS] Disable maven's mvneclipse by default?
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?
Re: [DISCUSS] Disable maven's mvneclipse by default?
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
FYI: this just got committed.
Re: [DISCUSS] Disable maven's mvneclipse by default?
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
Awesome thanks.
My hunch is we won’t hear anything at all. But hopefully I’m wrong. :)
> On May 31, 2017, at 1:10 PM, Sean Busbey <bu...@apache.org> wrote:
>
> I forwarded Allen's note over to HBase as well. no responses yet.
>
> On Tue, May 30, 2017 at 10:26 AM, Allen Wittenauer
> <aw...@effectivemachines.com> wrote:
>>
>>
>> Just to bring this back around:
>>
>> I've got a patch sitting on YETUS-509 to remove the support for testing Maven's eclipse plug-in. I'm also going to drop a note over into the Hadoop universe to mention that we're probably going to remove the test for it.
>>
>> Thanks.
Re: [DISCUSS] Disable maven's mvneclipse by default?
Posted by Sean Busbey <bu...@apache.org>.
I forwarded Allen's note over to HBase as well. no responses yet.
On Tue, May 30, 2017 at 10:26 AM, Allen Wittenauer
<aw...@effectivemachines.com> wrote:
>
>
> Just to bring this back around:
>
> I've got a patch sitting on YETUS-509 to remove the support for testing Maven's eclipse plug-in. I'm also going to drop a note over into the Hadoop universe to mention that we're probably going to remove the test for it.
>
> Thanks.
Re: [DISCUSS] Disable maven's mvneclipse by default?
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
Just to bring this back around:
I've got a patch sitting on YETUS-509 to remove the support for testing Maven's eclipse plug-in. I'm also going to drop a note over into the Hadoop universe to mention that we're probably going to remove the test for it.
Thanks.
Re: [DISCUSS] Disable maven's mvneclipse by default?
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
+1.
Just tried with Eclipse Neon.3, the 'Import Existing Maven Projects' works
for HBase.
And for hadoop, 'mvn eclipse:eclipse' never works for me. I need to modify
the build paths manually to fix the build errors...
Thanks.
2017-04-15 8:01 GMT+08:00 Andrew Wang <an...@cloudera.com>:
> 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 <su...@gmail.com>
> 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 <
> > aw@effectivemachines.com>
> > 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?
> > >
> > >
> > >
> > >
> >
>
Re: [DISCUSS] Disable maven's mvneclipse by default?
Posted by Andrew Wang <an...@cloudera.com>.
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 <su...@gmail.com> 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 <
> aw@effectivemachines.com>
> 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?
> >
> >
> >
> >
>
Re: [DISCUSS] Disable maven's mvneclipse by default?
Posted by suraj acharya <su...@gmail.com>.
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 <aw...@effectivemachines.com>
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?
>
>
>
>