On Sun, Sep 27, 2009 at 12:04 AM, Jason van Zyl <jvan...@sonatype.com>wrote:
> > On 2009-09-25, at 10:47 PM, Barrie Treloar wrote: > > On Sat, Sep 26, 2009 at 12:52 AM, Jason van Zyl <jvan...@sonatype.com >> >wrote: >> >> I wouldn't recommend using that. Let the Eclipse folks do it properly. >>> They >>> want to do it so we should help them in whatever capacity we can. >>> >> >> >> Having read through the bug report provided by Jesse ( >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=283745) >> I get the feeling that they are not keen to provide any resources to >> support >> this, because it diverts resources from other "entire" community >> activities. >> >> I know there are enough people in the Maven community that would like to >> see >> this done, so I expect it will fall on us to do the implementation work. >> > > Please don't start making unfounded assumptions, it really doesn't help. > > What we really need is someone from the Eclipse side who is willing to >> spend >> time explaining, guiding and providing advice to get this done. >> >> Does anyone have the necessary contacts at Eclipse to get such a person? >> > > Yes, I talk to folks on the board on a pretty regular basis. I also talk to > Mike Milinkovich and he wants to generally help setup proper Maven > repositories at Eclipse. Folks like Oisin O'Hurley and Jeff McAffer have > also expressed an interest in helping. Sonatype is actually a member, and > Webtide is also at Eclipse with Jetty and they build with Maven so it's all > getting done. > > You have to understand that Eclipse is far more rigorous with releases and > generally the planning of their infrastructure. If artifacts are produced > for a Maven repository it will be done with the knowledge and input of all > the projects at Eclipse. And their infrastructure people know that this > requires proper support, dedicated hardware and interoperability plans > between Maven repositories and P2 repositories. > > Just dumping a bunch of translated artifacts doesn't really help anyone in > the long term. Ok, I dont mean to sound unhelpful. What I mean was that since the pain is felt more keenly by the Maven community it is more likely that we will scratch the itch first. What I would like to do is to get some visibility into who is working on this, what are the issues and what can we do to help. Are you able to provide any more enlightenment?
