Re: Open JIRA issues/retiring plugins

2015-02-03 Thread Dennis Lundberg
Den 4 feb 2015 04:00 skrev "Hervé BOUTEMY" : > > Le lundi 2 février 2015 10:23:00 Michael Osipov a écrit : > > Hi folks, > > > > I have performed another cleanup on JIRA in the last couple of days, most of > > on old issues. Right now, we have more than 2000 open issues. Not manageble > > from my p

Re: Open JIRA issues/retiring plugins

2015-02-03 Thread Hervé BOUTEMY
Le lundi 2 février 2015 10:23:00 Michael Osipov a écrit : > Hi folks, > > I have performed another cleanup on JIRA in the last couple of days, most of > on old issues. Right now, we have more than 2000 open issues. Not manageble > from my point of view. > > I have noticed that several plugins hav

Re: Open JIRA issues/retiring plugins

2015-02-03 Thread Hervé BOUTEMY
notice that I completely understand Andreas explanations about memory requirements of m2e vs m-eclipse-p but > > The developer experience within eclipse is so much better after using the > > maven-eclipse-plugin. this one is more obscure to me this doesn't change the fact that I like Andreas pl

Re: Open JIRA issues/retiring plugins

2015-02-03 Thread Hervé BOUTEMY
Le lundi 2 février 2015 19:49:02 Andreas Gudian a écrit : > I'm pretty sure I might be bashed for writing this, but what the heck... ;-) > > I do still see some need for the maven-eclipse-plugin. > > To be perfectly clear, I agree that m2e is by far superior in many ways, > not only tech-wise, bu

Re: Open JIRA issues/retiring plugins

2015-02-03 Thread Stephen Connolly
On Monday, February 2, 2015, Olivier Lamy wrote: > -1 for both archetype and stage plugin. > Maybe I will have a look to fix issues if enough spare time.. > I don't understand such rush... AFAIK we are not a company with some budget > and who need to justify a ratio between number of bugs and tim

Re: Open JIRA issues/retiring plugins

2015-02-02 Thread Olivier Lamy
-1 for both archetype and stage plugin. Maybe I will have a look to fix issues if enough spare time.. I don't understand such rush... AFAIK we are not a company with some budget and who need to justify a ratio between number of bugs and time spent on projects. On 2 February 2015 at 20:23, Michael

Re: Open JIRA issues/retiring plugins

2015-02-02 Thread Andreas Gudian
Great, Daniel, I thought I'm the only one thinking that way... ;-) 2015-02-02 19:38 GMT+01:00 Daniel Kulp : > > I’m -1 to retiring the maven-eclipse-plugin until the m2e stuff is at a > state where it can be as flexible and useful as the maven-eclipse-plugin. > Trying to bring a large complex pr

Re: Open JIRA issues/retiring plugins

2015-02-02 Thread Andreas Gudian
I'm pretty sure I might be bashed for writing this, but what the heck... ;-) I do still see some need for the maven-eclipse-plugin. To be perfectly clear, I agree that m2e is by far superior in many ways, not only tech-wise, but also conceptionally. Still, at work we had to migrate from m2e to m

Re: Open JIRA issues/retiring plugins

2015-02-02 Thread Daniel Kulp
I’m -1 to retiring the maven-eclipse-plugin until the m2e stuff is at a state where it can be as flexible and useful as the maven-eclipse-plugin. Trying to bring a large complex project like CXF into eclipse with m2e is PAINFUL and doesn’t even result in fully configured and ready workspace.

Re: Open JIRA issues/retiring plugins

2015-02-02 Thread Benson Margulies
Just to be perfectly clear: I am volunteering to include archetype in the herd. I have submitted INFRA-9100 to move it to git. I have assigned http://jira.codehaus.org/browse/ARCHETYPE-471 to myself. So no need to send any email announcing its demise. ---

Re: Open JIRA issues/retiring plugins

2015-02-02 Thread Karl Heinz Marbaise
Hi, the plan was to release from almost all the plugins to make a last releases which has Maven 2.2.1 minimum and JDK 5 min. Furthermore I'm working on several of those plugins: maven-docck-plugin, maven-doap-plugin maven-repository-plugin maven-stage-plugin maven-pdf-plugin maven-archetype-p

Re: Open JIRA issues/retiring plugins

2015-02-02 Thread Benson Margulies
People are making new archetypes every day. I did a round of bugfixing a couple of years ago, I could do one again. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache

Re: Open JIRA issues/retiring plugins

2015-02-02 Thread Baptiste Mathus
Agree with Anders: * +1 to deprecate maven-eclipse-plugin (coming from an happy M2E user from years), the community must acknowledge that this plugin is not the way to go and there's a modern an well-maintained alternative. * -1 to deprecate maven-archetype-plugin IMO it's still one of those plugi

Re: Open JIRA issues/retiring plugins

2015-02-02 Thread Anders Hammar
I strongly second that the maven-eclipse-plugin be retired. For us working in Eclipse, the m2e integration is the way to go. Also, there has not been any active work on that plugin for many years and I think we should clearly indicate to the community that there is very little hope anyone would fix

Open JIRA issues/retiring plugins

2015-02-02 Thread Michael Osipov
Hi folks, I have performed another cleanup on JIRA in the last couple of days, most of on old issues. Right now, we have more than 2000 open issues. Not manageble from my point of view. I have noticed that several plugins haven't been touched in years. What is the status of the following plugi