On 1 Jun 07, at 12:02 PM 1 Jun 07, Tamás Cservenák wrote:
Hello,
no, i'm not talking about bringing them under one project.
I think it is too late for that. IMHO, every MRM (MRM as Maven Repo
Manager
and not Archiva predecessor) team achieved a lot, and it would be
irrealistic to expect from them to throw it away or dissect it. And
even if
they do, the result would be very probably a MRM called
"Frankenstein, the
most versatile Maven Repository Manager" that would never work :)
I think this is the best approach and I think that applications based
around maven should be ejected from Maven itself and either go TLP or
somewhere else. As a group we should be focusing on the core apis and
tools which are suffering I believe because of a focus on tools.
I was talking about common MRM API defined by Maven (maven
community, not
MRM developers/community). This common API could be implemented by
various
MRMs fully or partially (depending on their MRM capabilities).
And also, all "maven tools" like maven plugins or 3rd party tools
could use
this API to gain some benefit regardless of actual MRM on the far
end. Like
the mentioned m2eclipse or netbeans plugin, to reach remote repo
indexes for
example, etc.
~t~
On 6/1/07, Tim Moloney <[EMAIL PROTECTED]> wrote:
Since you said that all of the current maven proxies are essentially
repository managers and you are suggesting that we combine them
and all
of their features into one project...
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
