On 18 Dec 07, at 3:27 AM 18 Dec 07, [EMAIL PROTECTED] wrote:

i too think that work effort should be focused on one good product, instead of doing the work twice. this way plugin could be better quality, richer in features and releases would speed up.


q4e was forked from our codebase, it's not our project that created a second faction. It's purely political, all the technical reasons given in the q4e proposal are bogus. It's not like we can't create extensions points, or whatever other nonsense they have in that proposal. The development of q4e was driven by Mergere/Devzuz when I left that company and they no longer had access to this project. The code they submitted just wasn't very good which is why we never accepted it. It's as simple as that.

The fact is people involved in this project are the people actually involved in Maven making the integration possible. We felt that making good support was the most important thing, and moving forward if it was deemed important by our users and industry supporters to submit a proposal to eclipse then we would do so. We're not trying to leverage the Eclipse brand to promote our work prematurely, and use that as a driver to bring people to use our code. We are actually trying to make good code first.

ossi petz schrieb:
indeed.

after moving our builds from ant to maven (which was a real improvement) i have to say that eclipse integration lacks a certain comfort.

i tried q4e but m2eclipse works much better for me. if someone starts a comparison chart in a wiki or so i am glad to help filling the rows :)

the comparison with subversive / sublcipse is frequently used and quite good. but i am not satisfied with the situation there. both plugins are incomplete but in different areas. it is like doing thw work twice with no better solution coming out. so i dont understand why there is q4e at all.

having the same situation with m2eclipse and q4e cant be too good. from my 20 developers i have 2 that actually do releases with maven. the rest sees maven as some eclipse plugin which fails on hot-code-replacement. (different story). ide integration is a critical feature. having to choose on or another plugin does not improve that situation.

but well. lets see :-)
glad m2eclipse will live! thanks a lot!




Donnie McNeal schrieb:
IMO it seems that q4e and m2eclipse has finally lit a fire in the eclipse community to bring quality maven support to the IDE. So, hooray for both!



---------------------------------------------------------------------
To unsubscribe from this list please visit:

  http://xircles.codehaus.org/manage_email



--
manuel aldana
[EMAIL PROTECTED]
homepage: www.aldana-online.de


---------------------------------------------------------------------
To unsubscribe from this list please visit:

  http://xircles.codehaus.org/manage_email


Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.

-- Jakob Burckhardt



---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to