Update BUILDING.txt instructions for Eclipse

[Andrew Wang <an...@cloudera.com>]

Hi all,

I happened to see this on the maven list, looks like the Maven eclipse
plugin (aka "eclipse:eclipse") is being retired.

Our BUILDING.txt still mentions running the "eclipse:eclipse" goal. Has
anyone tried alternative ways of importing Hadoop into Eclipse? Seems like
a good time to update our instructions.

I've switched over to IDEA so this doesn't really affect me, but I'm happy
to test and update the Eclipse instructions if someone provides them.

Best,
Andrew

---------- Forwarded message ----------
From: Robert Scholte <rf...@apache.org>
Date: Wed, Oct 7, 2015 at 11:06 AM
Subject: [RESULT] [VOTE] Retire Maven Eclipse Plugin / Donation to Mojohaus
To: Maven Developers List <de...@maven.apache.org>
Cc: Maven Users List <us...@maven.apache.org>, Maven Project Management
Committee List <pr...@maven.apache.org>


Hi,

The vote has passed with the following result:

+1 (binding): Barrie Treloar, Arnaud Héritier, Tamás Cservenák, Dennis
Lundberg, Hervé BOUTEMY, Olivier Lamy, Karl Heinz Marbaise, Kristian
Rosenvold, Jason van Zyl, Robert Scholte
+1 (non binding): Tibor Digana, Anders Hammar, Michael Osipov, Andreas
Gudian
+0.5 (non binding): Baptiste Mathus

thanks for the huge number of votes!!

I will continue with the steps required to retire this plugin.

Robert

Op Sun, 04 Oct 2015 11:18:55 +0200 schreef Robert Scholte <
rfscholte@apache.org>:

Hi,
>
> during the latest upgrade of the plugin-parent I faced several issues with
> the maven-eclipse-plugin.
> It will take quite some time to fix these issues, but is it worth
> maintaining it here?
> Nowadays the Maven support for Eclipse is good and stable.
> The maven-eclipse-plugin has a lot of integration tests which should be
> rewritten, because it always launches a new Maven fork and it takes ages to
> complete. This simply blocks good continuous integration of the plugins.
> I know there are still some projects with can't use the Maven Integration
> of Eclipse and depend on this plugin, so the sources need to stay available
> for users so the can extend it for their own usage.
>
> I therefor propose that we retire maven-eclipse-plugin for the Apache
> Maven project and donate it to the Mojohaus project
>
> If this vote is successful I will make one final release of the plugin,
> making
> it clear on the plugin site that it has been retired. After that the
> source code
> will be moved into the "retired" area in Subversion.
>
> The process for retiring a plugin is described here:
> http://maven.apache.org/developers/retirement-plan-plugins.html
>
> The vote is open for 72 hours.
>
> [ ] +1 Yes, it's about time
> [ ] -1 No, because...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Update BUILDING.txt instructions for Eclipse

[Sangjin Lee <sj...@apache.org>]

I've used both ways of setting up hadoop for eclipse, and one issue I see
with m2eclipse is that it doesn't seem to set up the code-generated
protobuf classes properly. As a result, the workspace comes out with tons
of errors to begin with. Has anyone solved this issue?

Sangjin

On Thu, Dec 3, 2015 at 5:32 PM, Andrew Wang <an...@cloudera.com>
wrote:

> Yea my impression is that it'll basically no longer be maintained. The vote
> mentions the m2eclipse integration, which I know has been used successfully
> in the past for Hadoop. So if someone wants to write that up, it'd be good
> to have in BUILDING.txt.
>
> On Thu, Dec 3, 2015 at 5:24 PM, Chris Douglas <cd...@apache.org> wrote:
>
> > What does it mean for the project to "retire... and donate [the
> > plugin] to the Mojohaus project"? The plugin will still be available,
> > but not maintained by Apache Maven?
> >
> > Unless there is a satisfactory replacement for eclim, I'm stuck with
> > eclipse... -C
> >
> > On Wed, Oct 7, 2015 at 2:31 PM, Andrew Wang <an...@cloudera.com>
> > wrote:
> > > Hi all,
> > >
> > > I happened to see this on the maven list, looks like the Maven eclipse
> > > plugin (aka "eclipse:eclipse") is being retired.
> > >
> > > Our BUILDING.txt still mentions running the "eclipse:eclipse" goal. Has
> > > anyone tried alternative ways of importing Hadoop into Eclipse? Seems
> > like
> > > a good time to update our instructions.
> > >
> > > I've switched over to IDEA so this doesn't really affect me, but I'm
> > happy
> > > to test and update the Eclipse instructions if someone provides them.
> > >
> > > Best,
> > > Andrew
> > >
> > > ---------- Forwarded message ----------
> > > From: Robert Scholte <rf...@apache.org>
> > > Date: Wed, Oct 7, 2015 at 11:06 AM
> > > Subject: [RESULT] [VOTE] Retire Maven Eclipse Plugin / Donation to
> > Mojohaus
> > > To: Maven Developers List <de...@maven.apache.org>
> > > Cc: Maven Users List <us...@maven.apache.org>, Maven Project
> Management
> > > Committee List <pr...@maven.apache.org>
> > >
> > >
> > > Hi,
> > >
> > > The vote has passed with the following result:
> > >
> > > +1 (binding): Barrie Treloar, Arnaud Héritier, Tamás Cservenák, Dennis
> > > Lundberg, Hervé BOUTEMY, Olivier Lamy, Karl Heinz Marbaise, Kristian
> > > Rosenvold, Jason van Zyl, Robert Scholte
> > > +1 (non binding): Tibor Digana, Anders Hammar, Michael Osipov, Andreas
> > > Gudian
> > > +0.5 (non binding): Baptiste Mathus
> > >
> > > thanks for the huge number of votes!!
> > >
> > > I will continue with the steps required to retire this plugin.
> > >
> > > Robert
> > >
> > > Op Sun, 04 Oct 2015 11:18:55 +0200 schreef Robert Scholte <
> > > rfscholte@apache.org>:
> > >
> > > Hi,
> > >>
> > >> during the latest upgrade of the plugin-parent I faced several issues
> > with
> > >> the maven-eclipse-plugin.
> > >> It will take quite some time to fix these issues, but is it worth
> > >> maintaining it here?
> > >> Nowadays the Maven support for Eclipse is good and stable.
> > >> The maven-eclipse-plugin has a lot of integration tests which should
> be
> > >> rewritten, because it always launches a new Maven fork and it takes
> > ages to
> > >> complete. This simply blocks good continuous integration of the
> plugins.
> > >> I know there are still some projects with can't use the Maven
> > Integration
> > >> of Eclipse and depend on this plugin, so the sources need to stay
> > available
> > >> for users so the can extend it for their own usage.
> > >>
> > >> I therefor propose that we retire maven-eclipse-plugin for the Apache
> > >> Maven project and donate it to the Mojohaus project
> > >>
> > >> If this vote is successful I will make one final release of the
> plugin,
> > >> making
> > >> it clear on the plugin site that it has been retired. After that the
> > >> source code
> > >> will be moved into the "retired" area in Subversion.
> > >>
> > >> The process for retiring a plugin is described here:
> > >> http://maven.apache.org/developers/retirement-plan-plugins.html
> > >>
> > >> The vote is open for 72 hours.
> > >>
> > >> [ ] +1 Yes, it's about time
> > >> [ ] -1 No, because...
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: dev-help@maven.apache.org
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> >
>

Re: Update BUILDING.txt instructions for Eclipse

[Andrew Wang <an...@cloudera.com>]

Yea my impression is that it'll basically no longer be maintained. The vote
mentions the m2eclipse integration, which I know has been used successfully
in the past for Hadoop. So if someone wants to write that up, it'd be good
to have in BUILDING.txt.

On Thu, Dec 3, 2015 at 5:24 PM, Chris Douglas <cd...@apache.org> wrote:

> What does it mean for the project to "retire... and donate [the
> plugin] to the Mojohaus project"? The plugin will still be available,
> but not maintained by Apache Maven?
>
> Unless there is a satisfactory replacement for eclim, I'm stuck with
> eclipse... -C
>
> On Wed, Oct 7, 2015 at 2:31 PM, Andrew Wang <an...@cloudera.com>
> wrote:
> > Hi all,
> >
> > I happened to see this on the maven list, looks like the Maven eclipse
> > plugin (aka "eclipse:eclipse") is being retired.
> >
> > Our BUILDING.txt still mentions running the "eclipse:eclipse" goal. Has
> > anyone tried alternative ways of importing Hadoop into Eclipse? Seems
> like
> > a good time to update our instructions.
> >
> > I've switched over to IDEA so this doesn't really affect me, but I'm
> happy
> > to test and update the Eclipse instructions if someone provides them.
> >
> > Best,
> > Andrew
> >
> > ---------- Forwarded message ----------
> > From: Robert Scholte <rf...@apache.org>
> > Date: Wed, Oct 7, 2015 at 11:06 AM
> > Subject: [RESULT] [VOTE] Retire Maven Eclipse Plugin / Donation to
> Mojohaus
> > To: Maven Developers List <de...@maven.apache.org>
> > Cc: Maven Users List <us...@maven.apache.org>, Maven Project Management
> > Committee List <pr...@maven.apache.org>
> >
> >
> > Hi,
> >
> > The vote has passed with the following result:
> >
> > +1 (binding): Barrie Treloar, Arnaud Héritier, Tamás Cservenák, Dennis
> > Lundberg, Hervé BOUTEMY, Olivier Lamy, Karl Heinz Marbaise, Kristian
> > Rosenvold, Jason van Zyl, Robert Scholte
> > +1 (non binding): Tibor Digana, Anders Hammar, Michael Osipov, Andreas
> > Gudian
> > +0.5 (non binding): Baptiste Mathus
> >
> > thanks for the huge number of votes!!
> >
> > I will continue with the steps required to retire this plugin.
> >
> > Robert
> >
> > Op Sun, 04 Oct 2015 11:18:55 +0200 schreef Robert Scholte <
> > rfscholte@apache.org>:
> >
> > Hi,
> >>
> >> during the latest upgrade of the plugin-parent I faced several issues
> with
> >> the maven-eclipse-plugin.
> >> It will take quite some time to fix these issues, but is it worth
> >> maintaining it here?
> >> Nowadays the Maven support for Eclipse is good and stable.
> >> The maven-eclipse-plugin has a lot of integration tests which should be
> >> rewritten, because it always launches a new Maven fork and it takes
> ages to
> >> complete. This simply blocks good continuous integration of the plugins.
> >> I know there are still some projects with can't use the Maven
> Integration
> >> of Eclipse and depend on this plugin, so the sources need to stay
> available
> >> for users so the can extend it for their own usage.
> >>
> >> I therefor propose that we retire maven-eclipse-plugin for the Apache
> >> Maven project and donate it to the Mojohaus project
> >>
> >> If this vote is successful I will make one final release of the plugin,
> >> making
> >> it clear on the plugin site that it has been retired. After that the
> >> source code
> >> will be moved into the "retired" area in Subversion.
> >>
> >> The process for retiring a plugin is described here:
> >> http://maven.apache.org/developers/retirement-plan-plugins.html
> >>
> >> The vote is open for 72 hours.
> >>
> >> [ ] +1 Yes, it's about time
> >> [ ] -1 No, because...
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>

Re: Update BUILDING.txt instructions for Eclipse

[Chris Douglas <cd...@apache.org>]

What does it mean for the project to "retire... and donate [the
plugin] to the Mojohaus project"? The plugin will still be available,
but not maintained by Apache Maven?

Unless there is a satisfactory replacement for eclim, I'm stuck with
eclipse... -C

On Wed, Oct 7, 2015 at 2:31 PM, Andrew Wang <an...@cloudera.com> wrote:
> Hi all,
>
> I happened to see this on the maven list, looks like the Maven eclipse
> plugin (aka "eclipse:eclipse") is being retired.
>
> Our BUILDING.txt still mentions running the "eclipse:eclipse" goal. Has
> anyone tried alternative ways of importing Hadoop into Eclipse? Seems like
> a good time to update our instructions.
>
> I've switched over to IDEA so this doesn't really affect me, but I'm happy
> to test and update the Eclipse instructions if someone provides them.
>
> Best,
> Andrew
>
> ---------- Forwarded message ----------
> From: Robert Scholte <rf...@apache.org>
> Date: Wed, Oct 7, 2015 at 11:06 AM
> Subject: [RESULT] [VOTE] Retire Maven Eclipse Plugin / Donation to Mojohaus
> To: Maven Developers List <de...@maven.apache.org>
> Cc: Maven Users List <us...@maven.apache.org>, Maven Project Management
> Committee List <pr...@maven.apache.org>
>
>
> Hi,
>
> The vote has passed with the following result:
>
> +1 (binding): Barrie Treloar, Arnaud Héritier, Tamás Cservenák, Dennis
> Lundberg, Hervé BOUTEMY, Olivier Lamy, Karl Heinz Marbaise, Kristian
> Rosenvold, Jason van Zyl, Robert Scholte
> +1 (non binding): Tibor Digana, Anders Hammar, Michael Osipov, Andreas
> Gudian
> +0.5 (non binding): Baptiste Mathus
>
> thanks for the huge number of votes!!
>
> I will continue with the steps required to retire this plugin.
>
> Robert
>
> Op Sun, 04 Oct 2015 11:18:55 +0200 schreef Robert Scholte <
> rfscholte@apache.org>:
>
> Hi,
>>
>> during the latest upgrade of the plugin-parent I faced several issues with
>> the maven-eclipse-plugin.
>> It will take quite some time to fix these issues, but is it worth
>> maintaining it here?
>> Nowadays the Maven support for Eclipse is good and stable.
>> The maven-eclipse-plugin has a lot of integration tests which should be
>> rewritten, because it always launches a new Maven fork and it takes ages to
>> complete. This simply blocks good continuous integration of the plugins.
>> I know there are still some projects with can't use the Maven Integration
>> of Eclipse and depend on this plugin, so the sources need to stay available
>> for users so the can extend it for their own usage.
>>
>> I therefor propose that we retire maven-eclipse-plugin for the Apache
>> Maven project and donate it to the Mojohaus project
>>
>> If this vote is successful I will make one final release of the plugin,
>> making
>> it clear on the plugin site that it has been retired. After that the
>> source code
>> will be moved into the "retired" area in Subversion.
>>
>> The process for retiring a plugin is described here:
>> http://maven.apache.org/developers/retirement-plan-plugins.html
>>
>> The vote is open for 72 hours.
>>
>> [ ] +1 Yes, it's about time
>> [ ] -1 No, because...
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org