Re: Deprecate eclipse:eclipse plugin
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 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 defined place where development happens, it's fine with me. > >> 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 is an implicit claim >> to support them. Just letting them sit there hoping people contribute >> patches I don't think is good enough. > > Fair enough. > >> So if you want to give the maven-eclipse-plugin a happy life at Mojo then >> just take it there. > > I am not committer for Mojo, but that should be the least problem. > > - Jörg > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: Deprecate eclipse:eclipse plugin
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 defined place where development happens, it's fine with me. > 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 is an implicit claim > to support them. Just letting them sit there hoping people contribute > patches I don't think is good enough. Fair enough. > So if you want to give the maven-eclipse-plugin a happy life at Mojo then > just take it there. I am not committer for Mojo, but that should be the least problem. - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Deprecate eclipse:eclipse plugin
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 issues as above. > I've got m2eclipse working at home but I've never been able to get it > to work in my corporate environment yet. > (I've never looked at Eclipse/STS) > > m-e-p mostly works. A lot of the problems are around the edge cases. > And there are a lot of missing integration tests for the IBM specific > tools. > +1 But I'm forced to admit that maven eclipse plugin doesn't bring any solution either. > > Maybe giving it a new home would help, I haven't thought about it enough. > I've not looked at git usage at all, and from the little I understand > someone still needs to maintain it so that it can be released and > synced (via forge to central, or however). > I dont think a move will help the maintenance question, but it may > remove the (mis)percpetion that it is more actively maintained. > > I'd be interested to see other peoples opinions > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Deprecate eclipse:eclipse plugin
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 able to get it to work in my corporate environment yet. (I've never looked at Eclipse/STS) m-e-p mostly works. A lot of the problems are around the edge cases. And there are a lot of missing integration tests for the IBM specific tools. Maybe giving it a new home would help, I haven't thought about it enough. I've not looked at git usage at all, and from the little I understand someone still needs to maintain it so that it can be released and synced (via forge to central, or however). I dont think a move will help the maintenance question, but it may remove the (mis)percpetion that it is more actively maintained. I'd be interested to see other peoples opinions - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Deprecate eclipse:eclipse plugin
+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 this > year, so there definitely are people that are "supporting" it. > > Maybe if m2eclipse was actually usable for any of the projects I work on I > might think differently, but it isn't. > > It's used a lot, it's at least somewhat supported here, and no viable > alternative exists. Doesn't sound like deprecation material to me. > > Dan > > > On Monday 01 November 2010 10:04:14 am 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 corporate environments. Thus we cannot just say to our community that >> we just stop to maintain it. We have to propose something else. >> m2eclipse or Q4E are the best choices for now but they don't cover all what >> eclipse:eclipse can do and they have always some performances/stabilities >> issues with large projects. Everybody can fork eclipse:eclipse plugin (and >> many teams already did it) but I think we should provide a solution for >> them to try to share their changes. >> >> How will we communicate around these changes ? >> >> On Nov 1, 2010, at 2:37 PM, Jason van Zyl wrote: >> > I started moving any of the ones discussed here: >> > >> > http://svn.apache.org/repos/asf/maven/retired/ >> > >> > If anyone disagrees we can move them back but I think the ones suggest so >> > far are good candidates. >> > >> > On Nov 1, 2010, at 1:37 PM, Jason van Zyl wrote: >> >> Following up from a discussion on the user list. I think it's time to be >> >> realistic about providing a healthy level of support for plugins here. >> >> I think it makes more sense to reduce the foot print of plugins we say >> >> we support and do those well as opposed to housing many plugin that >> >> just don't get much love. I would ask people to think about the plugins >> >> we're housing that we shouldn't. Probably a thread per plugin would be >> >> fine for discussion. >> >> >> >> To that end the plugins I'll send the first thread. >> >> >> >> Thanks, >> >> >> >> Jason >> >> >> >> -- >> >> Jason van Zyl >> >> Founder, Apache Maven >> >> http://twitter.com/jvanzyl >> >> - >> >> >> >> Our achievements speak for themselves. What we have to keep track >> >> of are our failures, discouragements and doubts. We tend to forget >> >> the past difficulties, the many false starts, and the painful >> >> groping. We see our past achievements as the end result of a >> >> clean forward thrust, and our present difficulties as >> >> signs of decline and decay. >> >> >> >> -- Eric Hoffer, Reflections on the Human Condition >> > >> > Thanks, >> > >> > Jason >> > >> > -- >> > Jason van Zyl >> > Founder, Apache Maven >> > http://twitter.com/jvanzyl >> > - >> > >> > In short, man creates for himself a new religion of a rational >> > and technical order to justify his work and to be justified in it. >> > >> > -- Jacques Ellul, The Technological Society >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org > > -- > Daniel Kulp > dk...@apache.org > http://dankulp.com/blog > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Deprecate eclipse:eclipse plugin
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 work on I might think differently, but it isn't. It's used a lot, it's at least somewhat supported here, and no viable alternative exists. Doesn't sound like deprecation material to me. Dan On Monday 01 November 2010 10:04:14 am 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 corporate environments. Thus we cannot just say to our community that > we just stop to maintain it. We have to propose something else. > m2eclipse or Q4E are the best choices for now but they don't cover all what > eclipse:eclipse can do and they have always some performances/stabilities > issues with large projects. Everybody can fork eclipse:eclipse plugin (and > many teams already did it) but I think we should provide a solution for > them to try to share their changes. > > How will we communicate around these changes ? > > On Nov 1, 2010, at 2:37 PM, Jason van Zyl wrote: > > I started moving any of the ones discussed here: > > > > http://svn.apache.org/repos/asf/maven/retired/ > > > > If anyone disagrees we can move them back but I think the ones suggest so > > far are good candidates. > > > > On Nov 1, 2010, at 1:37 PM, Jason van Zyl wrote: > >> Following up from a discussion on the user list. I think it's time to be > >> realistic about providing a healthy level of support for plugins here. > >> I think it makes more sense to reduce the foot print of plugins we say > >> we support and do those well as opposed to housing many plugin that > >> just don't get much love. I would ask people to think about the plugins > >> we're housing that we shouldn't. Probably a thread per plugin would be > >> fine for discussion. > >> > >> To that end the plugins I'll send the first thread. > >> > >> Thanks, > >> > >> Jason > >> > >> -- > >> Jason van Zyl > >> Founder, Apache Maven > >> http://twitter.com/jvanzyl > >> - > >> > >> Our achievements speak for themselves. What we have to keep track > >> of are our failures, discouragements and doubts. We tend to forget > >> the past difficulties, the many false starts, and the painful > >> groping. We see our past achievements as the end result of a > >> clean forward thrust, and our present difficulties as > >> signs of decline and decay. > >> > >> -- Eric Hoffer, Reflections on the Human Condition > > > > Thanks, > > > > Jason > > > > -- > > Jason van Zyl > > Founder, Apache Maven > > http://twitter.com/jvanzyl > > - > > > > In short, man creates for himself a new religion of a rational > > and technical order to justify his work and to be justified in it. > > > > -- Jacques Ellul, The Technological Society > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org -- Daniel Kulp dk...@apache.org http://dankulp.com/blog - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Deprecate eclipse:eclipse plugin
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 is an implicit claim to support them. Just letting them sit there hoping people contribute patches I don't think is good enough. So if you want to give the maven-eclipse-plugin a happy life at Mojo then just take it there. On Nov 1, 2010, at 6:28 PM, Jörg Schaible wrote: > 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 with >>> eclipse in many corporate environments. >> >> I think once it's retired anyone has the option to pick it up and maintain >> it. I think all we're saying putting it in the retired area is that we >> don't have the resources to support said plugin. Folks can do what they >> like after that. > > Why don't you move it then straight away over to mojo ? > > - Jörg > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - the course of true love never did run smooth ... -- Shakespeare
Re: Deprecate eclipse:eclipse plugin
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 with >> eclipse in many corporate environments. > > I think once it's retired anyone has the option to pick it up and maintain > it. I think all we're saying putting it in the retired area is that we > don't have the resources to support said plugin. Folks can do what they > like after that. Why don't you move it then straight away over to mojo ? - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Deprecate eclipse:eclipse plugin
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 > corporate environments. I think once it's retired anyone has the option to pick it up and maintain it. I think all we're saying putting it in the retired area is that we don't have the resources to support said plugin. Folks can do what they like after that. > Thus we cannot just say to our community that we just stop to maintain it. > We have to propose something else. Go for it. > m2eclipse or Q4E are the best choices for now but they don't cover all what > eclipse:eclipse can do and they have always some performances/stabilities > issues with large projects. M2E specifically block project files created with mvn eclipse:eclipse. We're definitely not interested in maintaining it. > Everybody can fork eclipse:eclipse plugin (and many teams already did it) but > I think we should provide a solution for them to try to share their changes. > > How will we communicate around these changes ? > I think the easiest way for these people to work is to put the plugin in github and then they can more easily collaborate to fix it. I think we can announce these retirements on the user list and I can post a blog entry. > > On Nov 1, 2010, at 2:37 PM, Jason van Zyl wrote: > >> I started moving any of the ones discussed here: >> >> http://svn.apache.org/repos/asf/maven/retired/ >> >> If anyone disagrees we can move them back but I think the ones suggest so >> far are good candidates. >> >> On Nov 1, 2010, at 1:37 PM, Jason van Zyl wrote: >> >>> Following up from a discussion on the user list. I think it's time to be >>> realistic about providing a healthy level of support for plugins here. I >>> think it makes more sense to reduce the foot print of plugins we say we >>> support and do those well as opposed to housing many plugin that just don't >>> get much love. I would ask people to think about the plugins we're housing >>> that we shouldn't. Probably a thread per plugin would be fine for >>> discussion. >>> >>> To that end the plugins I'll send the first thread. >>> >>> Thanks, >>> >>> Jason >>> >>> -- >>> Jason van Zyl >>> Founder, Apache Maven >>> http://twitter.com/jvanzyl >>> - >>> >>> Our achievements speak for themselves. What we have to keep track >>> of are our failures, discouragements and doubts. We tend to forget >>> the past difficulties, the many false starts, and the painful >>> groping. We see our past achievements as the end result of a >>> clean forward thrust, and our present difficulties as >>> signs of decline and decay. >>> >>> -- Eric Hoffer, Reflections on the Human Condition >>> >>> >>> >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> In short, man creates for himself a new religion of a rational >> and technical order to justify his work and to be justified in it. >> >> -- Jacques Ellul, The Technological Society >> >> >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare
Deprecate eclipse:eclipse plugin
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 that we just stop to maintain it. We have to propose something else. m2eclipse or Q4E are the best choices for now but they don't cover all what eclipse:eclipse can do and they have always some performances/stabilities issues with large projects. Everybody can fork eclipse:eclipse plugin (and many teams already did it) but I think we should provide a solution for them to try to share their changes. How will we communicate around these changes ? On Nov 1, 2010, at 2:37 PM, Jason van Zyl wrote: > I started moving any of the ones discussed here: > > http://svn.apache.org/repos/asf/maven/retired/ > > If anyone disagrees we can move them back but I think the ones suggest so far > are good candidates. > > On Nov 1, 2010, at 1:37 PM, Jason van Zyl wrote: > >> Following up from a discussion on the user list. I think it's time to be >> realistic about providing a healthy level of support for plugins here. I >> think it makes more sense to reduce the foot print of plugins we say we >> support and do those well as opposed to housing many plugin that just don't >> get much love. I would ask people to think about the plugins we're housing >> that we shouldn't. Probably a thread per plugin would be fine for >> discussion. >> >> To that end the plugins I'll send the first thread. >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> Our achievements speak for themselves. What we have to keep track >> of are our failures, discouragements and doubts. We tend to forget >> the past difficulties, the many false starts, and the painful >> groping. We see our past achievements as the end result of a >> clean forward thrust, and our present difficulties as >> signs of decline and decay. >> >> -- Eric Hoffer, Reflections on the Human Condition >> >> >> > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
