Not to pass the buck but we in Geronimo are using Maven I think the way it was intended to be used.
Certainly there are issues that are becoming apparent. Aaron put out a good summary of the
problem that we are experiencing.
I think this is certainly important feedback for the Maven team as well. If we can improve our
process then I trust that the Maven team will provide their input.
Matt
Joshua Slive wrote:
On 6/7/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
> On 6/7/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
> >
> > > And in any case, I believe that much of the problem
> > > is not with maven per se, but with how it is being used.
> >
> > How exactly?
> >
> > Cocoon/Geronimo have both hit the same problem. The factor would
seem
> > to be having a lot of components in your build - which I can't see as
> > being a mis-use.
>
> The part about pointing to people.apache.org as a maven repository is
> not a design flaw in maven. The part about maven gobbling up way more
> resources than necessary probably is.
Geronimo/Cocoon and other projects did not set up the maven snapshot
repository at the ASF, they're using what has been in place for a long
time.
Perhaps you are misunderstanding my intentions. I am not trying to
blame anybody for the current situation and ask them to do penance.
I'm trying to get them to change what they do for future releases.
What exists now and in the past and who created it has nothing to do
with that. The fact that a maven repository exists in a particular
location does not mean it must be used.
Joshua.
