It's really a matter of who is going to support. Saying it's important and then
not doing much with it I don't believe is acceptable. At least if we put it
somewhere else, more people can work on it.
On Nov 2, 2010, at 9:37 AM, Jörg Schaible wrote:
> Hi Jason,
>
> Jason van Zyl wrote:
>
>> Go
Hi Jason,
Jason van Zyl wrote:
> Go for it. I'm going to help retire them, after that it's fair game. So if
> you, and the folks who might want to work on it, are cool with that then
> take it over there.
I consider the eclipse plugin still one of the more essential ones. As long
there is a def
On Tue, Nov 2, 2010 at 5:18 AM, Barrie Treloar wrote:
> On Tue, Nov 2, 2010 at 1:51 PM, Paul Benedict
> wrote:
> > +1 on keeping the eclipse plugin. I like m2Eclipse but at times is
> > buggy so I fall back to using this often.
>
> As someone who irregularly maintains m-e-p I have the same issue
On Tue, Nov 2, 2010 at 1:51 PM, Paul Benedict wrote:
> +1 on keeping the eclipse plugin. I like m2Eclipse but at times is
> buggy so I fall back to using this often.
As someone who irregularly maintains m-e-p I have the same issues as above.
I've got m2eclipse working at home but I've never been
+1 on keeping the eclipse plugin. I like m2Eclipse but at times is
buggy so I fall back to using this often.
Paul
2010/11/1 Daniel Kulp :
>
> I personally think deprecating/retiring the eclipse plugin is a bit premature.
> Looking at the svn log, there have been a buunch of commits and a release
I personally think deprecating/retiring the eclipse plugin is a bit premature.
Looking at the svn log, there have been a buunch of commits and a release this
year, so there definitely are people that are "supporting" it.
Maybe if m2eclipse was actually usable for any of the projects I wor
Go for it. I'm going to help retire them, after that it's fair game. So if you,
and the folks who might want to work on it, are cool with that then take it
over there.
My only concern is that we don't claim to support plugins that we have no real
intention of supporting. Having them in our SCM
Jason van Zyl wrote:
>
> On Nov 1, 2010, at 3:04 PM, Arnaud Héritier wrote:
>
>> For the eclipse plugin, I think that just moving it to retired isn't a
>> good think because even if we are agree that this one is now really
>> difficult to maintain, this is always the preferred integration way wi
On Nov 1, 2010, at 3:04 PM, Arnaud Héritier wrote:
> For the eclipse plugin, I think that just moving it to retired isn't a good
> think because even if we are agree that this one is now really difficult to
> maintain, this is always the preferred integration way with eclipse in many
> corpora
For the eclipse plugin, I think that just moving it to retired isn't a good
think because even if we are agree that this one is now really difficult to
maintain, this is always the preferred integration way with eclipse in many
corporate environments.
Thus we cannot just say to our community tha
10 matches
Mail list logo
