No one is going out of their way to break anything. No one is willing to maintain it. So, consistent with Apache policy, it should be 'attic-ed'. If then, some people want to take advantage of the Apache license and fork it into mojohaus, that's their privilege under the license. There's no such thing as a 'donation'. The license is already sufficient.
And yes, IDEs should be able to have a way to memoize in the POM; why not? I'd like, personally, to legitimize the use of namespaces to allow _anything_ to have extensions in the pom. On Thu, Oct 8, 2015 at 9:37 AM, Arnaud Héritier <[email protected]> wrote: > Because it is impossible to maintain it nowadays. Too much features (support > for many eclipse distress with many extensions like WTP…), not enough tests > and the impossibility to validate anything at the end because configuration > files used by eclipse are evolving, not documented and there is no known > solution to manage them nicely (as far it was impossible several years ago > when I was maintaining it). > > Also I suppose that now a large part of maven committers aren’t using eclipse > or are using m2e which doesn’t give them the required experience to > improve/maintain this plugin. > > That’s why moving it to MojoHaus will be a good thing because it will allow > more people to contribute to it. > > About the fact that you need to add some settings in your POM because of m2e > …. yes that’s not cool. But I’m using IDEA thus I don’t have useful feedback > about it. It reminds that for all IDEs it is always a nightmare to correctly > share IDE settings inside a team/project. Having some configuration about it > in the pom doesn’t seem the worst idea... > > > >> On 08 Oct 2015, at 15:22, Gary Gregory <[email protected]> wrote: >> >> Sorry for the top post, phone. >> So are you saying that the way forward is to have junk in POM files for the >> way each kind of IDE does its business? Tall about mixing model and view! >> There is nothing wrong with eclipse:eclipse IMO but I have no spare cycles >> to maintain it. I'm not sure why Maven wants to go out of its way to break >> it though... >> Gary >> >> -------- Original message -------- >> From: Jochen Wiedmann <[email protected]> >> Date: 10/07/2015 23:34 (GMT-08:00) >> To: Maven Developers List <[email protected]> >> Subject: Re: [VOTE] Retire Maven Eclipse Plugin / Donation to Mojohaus >> >> On Wed, Oct 7, 2015 at 8:04 PM, Gary Gregory <[email protected]> wrote: >> >>> Does m2e still want to pollute POMs withcryptic entries? >> >> There are alternative storage possibilities, but that >> doesn't fix the inherited difficulties. Just mákes the >> SCM purists happy (and forces other users to live with the same >> trouble that you already fixed for yourself.) >> >> Jochen >> >> -- >> The next time you hear: "Don't reinvent the wheel!" >> >> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
