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

Reply via email to