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
